[lkml]   [2001]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Module Licensing?
Rik van Riel wrote:

> Since your program, which happens to consist of one open
> source part and one proprietary part, is partly a derived
> work from the kernel source (by using kernel header files
> and the inline functions in it) your whole work must be
> distributed under the GPL.

I contest your meaning of the word "work". The open source portion of my
module is one "work", and the closed source portion is another "work". I
could deliver these two works as separate tarballs, if I wanted.

Not only that, but the closed-source portion of my driver is not derived from
any GPL program, so the phrase "contains or is derived from the Program" does
not apply to it, because it:

1. Does not contain any part of any GPL Program
2. Is not derived from any GPL Program

>>Our open source bits are GPL because they are "derived" from the kernel
>>source, which is also GPL.
> "open source bits" ... from "the work as a whole" ?

The point I'm trying to make is that I can play the semantics game very
easily, and still not be forced to open-source the closed-source portions of
my driver. Because of the way Linux loads modules, I could take all the
open-source portions and link them into one .o file, and then insmod that .o
file without any problems. Then the closed-source portion would also be
insmod'ed. The only issue is that closed-source portion would fail to load if
the open-source portion is not already loaded.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.101 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site