From: David Weinehall <tao@acc.umu.se>
To: Pramod Srinivasan <pramods@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GPL issues
Date: Wed, 12 Apr 2006 10:16:13 +0200 [thread overview]
Message-ID: <20060412081613.GX23222@vasa.acc.umu.se> (raw)
In-Reply-To: <fcff6ec10604120001o18ca9edxf11ed055b5601e2a@mail.gmail.com>
On Wed, Apr 12, 2006 at 12:01:02AM -0700, Pramod Srinivasan wrote:
> > 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...)
>
> > 5. Userspace code that depends on interfaces you added to the kernel
> > --> consult a lawyer (if this interface is something completely new,
> > you can *probably* use your own license for the userland part; if the
> > interface is more or less a wrapper of existing functionality, GPL)
>
> An example could be helpful in clarifying the GPL license.
>
> Suppose I use the linux-vrf patch for the kernel that is freely
> available and use the extended setsocket options such as SO_VRF in an
> application, do I have to release my application under GPL since I am
> using a facility in the kernel that a standard linux kernel does not
> provide?
>
> Suppose my LKM driver adds a extra header to all outgoing packets and
> removes the extra header from the incoming packets, should this driver
> be released under GPL.? In a way it extends the functionality of
> linux, if I do release the driver code under GPL because this was
> built with linux in mind, Should I release the application which
> adds intelligence to interpret the extra header under GPL?
As I said above, you need to consult a lawyer in unclear cases.
The examples you list above seems innocent enough, but again, I am not a
lawyer. A lot has to do with intent. Are you exporting things to
userland just to workaround the GPL? If so, you're likely violating
the GPL... =)
Regards: david
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2006-04-12 8:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 7:01 Pramod Srinivasan
2006-04-12 8:16 ` David Weinehall [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 6:31 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
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
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=20060412081613.GX23222@vasa.acc.umu.se \
--to=tao@acc.umu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=pramods@gmail.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
all inboxes | Powered by JetHome®