> Tzafrir Cohen <[EMAIL PROTECTED]> writes:
>
> > The linux kernel is licensed under a license that is not exactly the GPL.
> > It is the GPL with an extra clause that allows binary modules (to allow
> > support of certain kinds of hardware, and with certain limitations, but
> > this is really *not* the place to discuss them).
>
> I am assuming you mean this:
>
> http://www.gnu.org/licenses/gpl-faq.html#LinkingOverControlledInterface
>
> AFAIK, the Linux kernel does not include this stipulation, albeit
> Linus's note at the top of /usr/src/linux/COPYING is arguably similar
> in spirit. Thus, linking binary modules is a bit shaky (you may trust
> Linus who seems to be quite liberal, but parts of kernel code are
> copyrighted by others, who may adhere to stricter interpretations).
>
> A cautious solution would involve a GPLed (with the additional clause
> like in the URL above) interface module, and a proprietary module that
> will only use the facilities provided by the interface module.
>
> In addition, if you make sure that whatever your module does makes
> sense out of the context of the Linux kernel, you are probably covered
> (this last condition is difficult to satisfy in the case of hardware
> drivers and such).
>
> --
> Oleg Goldshmidt | [EMAIL PROTECTED]
> "A sense of the fundamental decencies is parceled out unequally at birth."
>
What do you mean by `make sure that whatever your module does makes
sense out of the context of the Linux kernel'?
I guess that once I will get that sentence I will be able to understand
why it is difficult to satisfy in the case of hardware drivers.
--
Shaul Karl, [EMAIL PROTECTED] e t
=================================================================
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]
