From: Mark Lord <lkml@rtr.ca>
To: Joshua Hudson <joshudson@gmail.com>
Cc: Ramakanth Gunuganti <rgunugan@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: GPL issues
Date: Tue, 11 Apr 2006 23:18:04 -0400 [thread overview]
Message-ID: <443C716C.1060103@rtr.ca> (raw)
In-Reply-To: <bda6d13a0604111938j5ece401cid364582fe9d6cf76@mail.gmail.com>
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.
Cheers
next prev parent reply other threads:[~2006-04-12 3:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 6:31 GPL issues Ramakanth Gunuganti
2006-04-11 8:42 ` Jesper Juhl
2006-04-11 10:51 ` Martin Mares
2006-04-11 17:46 ` Horst von Brand
2006-04-11 13:49 ` Kyle Moffett
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 16:07 ` linux-os (Dick Johnson)
2006-04-11 16:29 ` Stefan Smietanowski
2006-04-11 16:13 ` Adrian Bunk
2006-04-11 16:15 ` Kyle Moffett
2006-04-11 16:23 ` Dave Neuer
2006-04-11 18:58 ` Jan Engelhardt
2006-04-14 11:39 ` David Schwartz
2006-04-14 14:54 ` linux-os (Dick Johnson)
2006-04-14 17:50 ` David Weinehall
2006-04-14 18:56 ` David Schwartz
2006-04-15 11:55 ` Alan Cox
2006-04-15 13:04 ` Steven Rostedt
2006-04-15 18:49 ` David Schwartz
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 23:06 ` David Weinehall
2006-04-12 2:38 ` Joshua Hudson
2006-04-12 3:18 ` Mark Lord [this message]
2006-04-12 5:00 ` Kyle Moffett
2006-04-12 5:31 ` Arjan van de Ven
2006-04-12 5:45 ` jdow
2006-04-12 6:01 ` David Weinehall
2006-04-12 6:26 ` jdow
2006-04-12 9:13 ` Stefan Smietanowski
2006-04-12 11:33 ` Olivier Galibert
2006-04-12 14:51 ` Arjan van de Ven
2006-04-13 22:07 ` Mark Lord
2006-04-15 11:14 ` Arjan van de Ven
2006-04-13 22:17 ` Mark Lord
2006-04-15 11:15 ` Arjan van de Ven
2006-04-11 23:12 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2006-04-12 7:01 Pramod Srinivasan
2006-04-12 8:16 ` David Weinehall
2006-04-12 9:06 ` Jan Engelhardt
2006-04-12 9:22 ` Stefan Smietanowski
2006-04-12 9:40 ` Martin Mares
2006-04-12 9:28 ` Alan Cox
2006-04-14 11:39 ` David Schwartz
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=443C716C.1060103@rtr.ca \
--to=lkml@rtr.ca \
--cc=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgunugan@yahoo.com \
/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