Messages in this thread | | | From | "jdow" <> | Subject | Re: GPL issues | Date | Tue, 11 Apr 2006 22:45:55 -0700 |
| |
> On Tue, 2006-04-11 at 23:18 -0400, Mark Lord wrote: >> Joshua Hudson wrote: >> > On 4/11/06, David Weinehall <tao@acc.umu.se> wrote: >> >> OK, simplified rules; if you follow them you should generally be OK: >> .. >> >> 3. Userspace code that uses interfaces that was not exposed to userspace >> >> before you change the kernel --> GPL (but don't do it; there's almost >> >> always a reason why an interface is not exported to userspace) >> >> >> >> 4. Userspace code that only uses existing interfaces --> choose >> >> license yourself (but of course, GPL would be nice...) >> >> Err.. there is ZERO difference between situations 3 and 4. >> Userspace code can be any license one wants, regardless of where >> or when or how the syscalls are added to the kernel. > > that is not so clear if the syscalls were added exclusively for this > application by the authors of the application....
Consider a book. The book is GPLed. I do not have to GPL my brain when I read the book.
I add some margin notes to the GPLed book. I still do not have to GPL my brain when I read the book.
{^_^} Joanne Dow - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |