Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <joel.soete@tiscali.be>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] adding a second nic to B1000
Date: Fri, 08 Aug 2003 19:32:21 +0000	[thread overview]
Message-ID: <3F33FAC5.40509@tiscali.be> (raw)
In-Reply-To: <20030808150256.GX1873@lug-owl.de>

Jan-Benedict Glaw wrote:

>On Fri, 2003-08-08 07:46:24 +0000, Joel Soete <joel.soete@tiscali.be>
>wrote in message <3F335550.3030804@tiscali.be>:
>  
>
>>geos@canada.com wrote:
>>    
>>
>
>  
>
>>But to load modules, they have to be build for the kernel you are 
>>running (I think that will change in 2.6). So the only  think to do now 
>>    
>>
>
>I'm quite sure that won't change, ever. Linux, if it's compatible to
>itself at all, has got "only" a source compatible API. You're somewhat
>on a more save side if you're using symbol versioning, but if you force
>a module to load (into a kernel of different version or even of
>different configuration), you may loose. Right now or sometime later:)
>
>That's what "tainting" was ment for:)
>
>MfG, JBG
>
>  
>
Sorry for this confuion I do have missunderstood some discussion on the 
subject, my bad :(

Thanks for those clarification,
    Joel

  reply	other threads:[~2003-08-08 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 18:01 [parisc-linux] adding a second nic to B1000 geos
2003-08-08  7:46 ` Joel Soete
2003-08-08 15:02   ` Jan-Benedict Glaw
2003-08-08 19:32     ` Joel Soete [this message]
     [not found] <20030807091916.8745.h006.c009.wm@mail.canada.com.criticalpath.net>
2003-08-07 16:59 ` Randolph Chung
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07 15:36 geos
2003-08-07 15:54 ` Randolph Chung
2003-08-07 16:04 ` Joel Soete
2003-08-07 18:42 ` Jesse Dougherty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F33FAC5.40509@tiscali.be \
    --to=joel.soete@tiscali.be \
    --cc=jbglaw@lug-owl.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox