mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: jdow <jdow@earthlink.net>
Cc: Arjan van de Ven <arjan@infradead.org>, Mark Lord <lkml@rtr.ca>,
	Joshua Hudson <joshudson@gmail.com>,
	Ramakanth Gunuganti <rgunugan@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: GPL issues
Date: Wed, 12 Apr 2006 08:01:22 +0200	[thread overview]
Message-ID: <20060412060122.GW23222@vasa.acc.umu.se> (raw)
In-Reply-To: <004101c65df4$5eb71ce0$0225a8c0@Wednesday>

On Tue, Apr 11, 2006 at 10:45:55PM -0700, jdow wrote:
> >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.

This is possibly the worst comparison I've read in a long long time...

It's rather a case of:

Consider a book.  The book is GPLed.  You take add one chapter to the
book.  The resulting book needs to be GPLed.

Now, instead of adding to that book, you "export" parts of the book by
copying them into your book.  Your new book wouldn't work without the
copied parts.  Your resulting book needs to be GPLed.

Your "read the book"-case is only comparable to the case of building
a userspace binary for local use that only uses existing interfaces,
vs building one that uses exported private interfaces.  In both cases,
since you're not distributing your modified version, you're free to
do whatever you like.


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           (/

  reply	other threads:[~2006-04-12  6:01 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
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=20060412060122.GW23222@vasa.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=arjan@infradead.org \
    --cc=jdow@earthlink.net \
    --cc=joshudson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --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

all inboxes | Powered by JetHome®