public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Golds <jgolds@resilience.com>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Controversy over dynamic linking -- how to end the panic
Date: Thu, 21 Jun 2001 11:39:13 -0700	[thread overview]
Message-ID: <3B323F51.BEDC7712@resilience.com> (raw)
In-Reply-To: <200106211814.f5LIEgK04880@snark.thyrsus.com>

"Eric S. Raymond" wrote:
> ------------------------------------------------------------------------
> The GPL license reproduced below is copyrighted by the Free Software
> Foundation, but the Linux kernel is copyrighted by me and others who
> actually wrote it.
> 
> The GPL license requires that derivative works of the Linux kernel
> also fall under GPL terms, including the requirement to disclose
> source.  The meaning of "derivative work" has been well established
> for traditional media, and those precedents can be applied to
> inclusion of source code in a straightforward way.  But as of
> mid-2001, neither case nor statute law has yet settled under what
> circumstances *binary* linkage of code to a kernel makes that code a
> derivative work of the kernel.
> 
> To calm down the lawyers, I as the principal kernel maintainer and
> anthology copyright holder on the code am therefore adding the
> following interpretations to the kernel license:
> 
> 1. Userland programs which request kernel services via normal system
>    calls *are not* to be considered derivative works of the kernel.
> 
> 2. A driver or other kernel component which is statically linked to
>    the kernel *is* to be considered a derivative work.
> 
> 3. A kernel module loaded at runtime, after kernel build, *is not*
>    to be considered a derivative work.
> 
> These terms are to be considered part of the kernel license, applying
> to all code included in the kernel distribution.  They define your
> rights to use the code in *this* distribution, however any future court
> may rule on the underlying legal question and regardless of how the
> license or interpretations attached to future distributions may change.

I disagree with 2.  Consider the following:

- GPL library foo is used by application bar.  bar must be GPL because
foo is.  I agree with this.
- Non-GPL library foo is used by GPL application bar.  foo does NOT
become GPL just because bar is, even if bar statically linked foo in.

The kernel is the equivalent of an application.  If someone needs to
statically link in a driver, which is the equivalent of a library, I
don't see how that should make the driver GPL.


-Jeff

P.S.  I don't claim to be a lawyer, this is just my opinion.

-- 
Jeff Golds
Sr. Software Engineer
jgolds@resilience.com

  parent reply	other threads:[~2001-06-21 18:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 18:14 Controversy over dynamic linking -- how to end the panic Eric S. Raymond
2001-06-21 18:30 ` Alan Cox
2001-06-21 19:17   ` Eric S. Raymond
2001-06-21 19:51     ` Andrew Pimlott
2001-06-21 20:13       ` Eric S. Raymond
2001-06-21 20:17         ` David S. Miller
2001-06-21 20:46         ` Andrew Pimlott
2001-06-21 21:02         ` Timur Tabi
2001-06-21 21:05           ` Andrew Pimlott
2001-06-21 21:17           ` Timur Tabi
2001-06-21 20:29       ` Timur Tabi
2001-06-21 18:39 ` Jeff Golds [this message]
2001-06-21 18:51   ` Jeff Mahoney
2001-06-21 20:02   ` Steve Brueggeman
2001-06-21 18:46 ` Timur Tabi
2001-06-21 19:03   ` Timur Tabi
2001-06-21 19:53     ` Erik Mouw
2001-06-21 19:04   ` Mike Harrold
2001-06-21 19:14     ` Alan Cox
2001-06-21 20:12       ` Marco Colombo
2001-06-21 21:14         ` Alan Cox
2001-06-21 20:31       ` Timur Tabi
2001-06-21 19:08   ` Timur Tabi
2001-06-21 19:17     ` Alexander Viro
2001-06-21 20:01   ` Wei Weng
2001-06-21 19:06     ` Alan Cox
2001-06-21 19:34       ` Jonathan Lundell
2001-06-21 20:17         ` D. Stimits
2001-06-22 11:32   ` Rob Landley
2001-06-21 20:34 ` Craig Milo Rogers
2001-06-21 21:35   ` Controversy over dynamic linking -- how to end the panic (long) Alex Bligh - linux-kernel
2001-06-22 12:32   ` Fair Use (Was Re: Controversy over dynamic linking -- how to end the panic) Rob Landley
2001-06-22  1:29 ` Controversy over dynamic linking -- how to end the panic Andrea Arcangeli
2001-06-22 10:44 ` David Woodhouse
2001-06-23 20:11 ` Fabrice Gautier
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 19:22 Disconnect
2001-06-21 19:24 ` Alan Cox
2001-06-21 19:25 Jesse Pollard
2001-06-21 21:43 Timur Tabi
2001-06-22  3:05 Rick Hohensee
2001-06-22  4:05 ` kumon
2001-06-23 22:29 ` Scott Wood

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=3B323F51.BEDC7712@resilience.com \
    --to=jgolds@resilience.com \
    --cc=esr@snark.thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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