In this section I'm a bit hazy - but as I see it, modules are "linked" againt the kernel , as linking means that you can communicate by function calls in the same memory space, whatever you wish to call it, and whatever API you use to accomplish such a deal.
Oded -- Beware of low-flying butterflies. ----- Original Message ----- From: "Oleg Goldshmidt" <[EMAIL PROTECTED]> To: "Gilad Ben-Yossef" <[EMAIL PROTECTED]> Cc: "Amnon Shiloh" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, November 28, 2001 3:16 PM Subject: Re: making a non-GPLed module > Gilad Ben-Yossef <[EMAIL PROTECTED]> writes: > > > Again, I am no lawyer, but the "official" GNU/FSF standpoint as I > > understand is that the fact that module links against a GPLed work > > (the Linux kernel) means in is considered a "derived work" of the > > Linux kernel and therefor can only be published under the GPL. > > Let me get the technical terminology correct. Are the modules > considered "linked" against the kernel? Or are they "loaded" at > runtime and constitute - as Linus put it - "normal usage of the > kernel"? I must admit never delved into the details of this (though > I did build kernels numerous times). Is "linkage" defined as "running > ld(1) or equivalent (e.g. via a compiler front-end) on the module > and the kernel"? Then I's say they are not linked... However the > insmod(8) man page does say "link". I suppose this means that modules > are linked, indeed. > > -- > Oleg Goldshmidt | [EMAIL PROTECTED] > "If it ain't broken, it has not got enough features yet." > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
