public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Schwartz <davids@webmaster.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Wed, 12 Feb 2003 14:31:13 -0800	[thread overview]
Message-ID: <20030212223115.AAA18900@shell.webmaster.com@whenever> (raw)
In-Reply-To: <200302122143.h1CLhApk010133@turing-police.cc.vt.edu>

On Wed, 12 Feb 2003 16:43:10 -0500, Valdis.Kletnieks@vt.edu wrote:
>On Wed, 12 Feb 2003 13:30:21 PST, David Schwartz said:

>>You already have the right to produce derivative works.

>No. At least in the US, 17 USC 106 says producing a derivative right
>is reserved to the
>copyright holder, except for the cases enumerated in 17 USC 107-121.

>So if you're producing a derivative work without having gotten the
>rights to do so, you're screwed in the legal sense.

	You have been given that right. The GPL, without clause 2, gives you 
the right to use the work (see citation below). For source code, the 
only way to use it is to produce derivative works.

>Clause 2 of the GPL gives you the right to produce derivative works 
>*IF*
>you accept the conditions.  Having accepted that clause, you're
>bound by
>it - that's what makes the GPL work.
>
>Please enumerate what *OTHER* way you are getting the right to
>produce a
>derivative work, rather than via the GPL clause 2.  (Note that this 
>*could*
>happen, if for instance code is dual-licensed and you are getting
>the right via the other license).

	The GPL says:

"Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the 
Program is covered only if its contents constitute a work based on 
the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does."

	Please explain to me, say for the case of the Linux kernel source 
code, how you can run it without first producing a derivative work. 
Granting a person the right to *use* source code means granting them 
the right to produce derivative works of that source code because 
that is how source code is used.

	How can I use the Linux kernel, say on an FTP site or a CD that I 
ordered, without copying it onto my computer? How can I compile it 
without copying it into memory?

	You cannot use a C source file without modifying it. In order to 
compile it, you must pass it through a preprocessor. This produces a 
modified copy of the original.

	Source code is like a recipe. The right to use it implicitly 
includes the right to follow the recipe and eat the results because 
that is how one uses a recipe. Along the way, one makes copies and 
derived works. It's simply unavoidable.

	This doesn't mean that all copying and modifying is automatically 
allowed for all cases where you have the right to use source code. 
However, it does mean that absent a restrictive agreement to the 
contrary that limits your *usage* rights, you can create derived 
works and you can make copies because that's how you use source code. 

	You can't give the derived works or copies to those who have no 
right to the original work (because you can't give others rights to 
code that is not yours). However, no special right to the original 
work is needed to distribute derived works among those who already 
have the right to use and possess the original work and make the 
derived works.

	In the case of the GPL, you even have the additional right to 
distribute the original work. I would argue that you can distribute 
derived works even without the right to distribute the original 
provided all recipients have the right to use and possess the 
original. But this argument isn't even needed.

>Note again that two of these rights (distribute the original,
>distribute
>the modifications) are *NOT* ones you inherently have - you are
>getting them
>*WITH RESTRICTIONS* on what you can and can't do (see clause 2
>again).

	No, that is not true. The GPL says:

"1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any 
warranty; and give any other recipients of the Program a copy of this 
License along with the Program."

	There are no significant restrictions placed upon the distribution 
of the original work. Even if there were, it's not clear that it 
would be enforceable considering that you are only distributing the 
work to people who already have the right to possess and use it. 
There are only a small number of cases on this point and they're 
split both ways. In all the cases where the copyright holder 
prevailed (such as the lawsuit against mp3.com), it was based on a 
showing that such distribution foreclosed on their sales, an argument 
that could not be made in the case of the GPL. So this could be 
argued either way even without clause 1.

	As for distributing modifications, as I have already argued at least 
four times now, this is not a special right to the *original* work so 
there is no need to invoke clause 2 to get that right. It is subsumed 
under the right to make derivative works and the right to distribute 
the original work. It is the simple sum of those two rights (except 
the additional rights you need to the modifications themselves).

	To make and distribute a derived work, you need certain rights to 
the original work. Specifically, you need the right to make the 
derived work in the first place and you need the right to distribute 
the original work. I am saying that you have both of these rights 
without clause 2. It is even arguable that you have them without 
clause 1.

	This will be the last time I repeat myself. I promise. I will not 
respond to this thread unless something genuinely new comes up.

	DS



  reply	other threads:[~2003-02-12 22:21 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030212213022.AAA17490%shell.webmaster.com@whenever>
2003-02-12 21:43 ` Monta Vista software license terms Valdis.Kletnieks
2003-02-12 22:31   ` David Schwartz [this message]
2003-02-12 23:04     ` Daniel Forrest
2003-02-12 23:28       ` David Schwartz
     [not found] <20030212201840.AAA15967%shell.webmaster.com@whenever>
2003-02-12 20:46 ` Valdis.Kletnieks
2003-02-12 21:30   ` David Schwartz
2003-02-12 21:41     ` Derek Fawcus
2003-02-11 22:27 Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2003-02-06 19:11 Dan Kegel
2003-02-06 20:38 ` Andre Hedrick
2003-02-07 17:28   ` Dan Kegel
2003-02-05 11:58 Nilmoni Deb
2003-02-05 17:04 ` Disconnect
2003-02-05 17:25   ` Christoph Hellwig
2003-02-05 17:10 ` Robert Love
2003-02-05 17:18   ` Nilmoni Deb
2003-02-05 17:23     ` Robert Love
2003-02-05 17:36       ` andrea.glorioso
2003-02-05 17:57         ` Nicolas Pitre
2003-02-05 18:13           ` andrea.glorioso
2003-02-05 18:15           ` Christoph Hellwig
2003-02-05 18:24             ` Steven Dake
2003-02-05 18:28               ` Christoph Hellwig
2003-02-05 19:41               ` Alan Cox
2003-02-05 18:47                 ` Christoph Hellwig
2003-02-05 18:52                   ` Steven Dake
2003-02-05 18:31             ` Nicolas Pitre
2003-02-05 18:34               ` Christoph Hellwig
2003-02-05 18:41                 ` Nicolas Pitre
2003-02-05 18:42                   ` Christoph Hellwig
2003-02-05 19:00                     ` Nicolas Pitre
2003-02-05 18:51                 ` Ben Greear
2003-02-05 18:54             ` Dana Lacoste
2003-02-05 18:56               ` Christoph Hellwig
2003-02-05 19:25                 ` Hugo Mills
2003-02-06  8:08             ` Andre Hedrick
2003-02-05 18:44       ` Nilmoni Deb
2003-02-05 17:16 ` Daniel Jacobowitz
2003-02-05 17:38   ` andrea.glorioso
2003-02-05 17:54     ` Christoph Hellwig
2003-02-05 18:04       ` andrea.glorioso
2003-02-06  1:11       ` jeff millar
2003-02-06  2:19         ` James Buchanan
2003-02-06  9:12         ` Andre Hedrick
2003-02-06 14:37           ` Alan Cox
2003-02-06 18:41             ` Valdis.Kletnieks
2003-02-06 19:14               ` Charles Cazabon
2003-02-06 20:36               ` Andre Hedrick
2003-02-10  7:18         ` Oliver Xymoron
2003-02-10  7:24           ` Christoph Hellwig
2003-02-10 13:24           ` Alan Cox
2003-02-10 17:42             ` Oliver Xymoron
2003-02-10 21:33               ` David Schwartz
2003-02-11  7:42                 ` Horst von Brand
2003-02-11 19:39                   ` David Schwartz
2003-02-11 20:42                     ` Horst von Brand
2003-02-11 22:11                       ` David Schwartz
2003-02-12  8:00                         ` Horst von Brand
2003-02-12 13:26                         ` Mark Hounschell
2003-02-12 15:32                         ` Chris Friesen
2003-02-12 20:18                           ` David Schwartz
2003-02-13  2:21                             ` Jamie Lokier
2003-02-13  2:41                               ` David Schwartz
2003-02-13  3:01                                 ` Jamie Lokier
2003-02-12  3:25                 ` Derek Fawcus
2003-02-12  4:13                   ` David Schwartz
2003-02-05 18:47   ` Nilmoni Deb
2003-02-05 17:17 ` Christoph Hellwig
2003-02-05 18:17   ` Nicolas Pitre
2003-02-05 18:20     ` Christoph Hellwig
2003-02-05 18:33       ` Nicolas Pitre
2003-02-05 18:40       ` Russell King
2003-02-06 11:31       ` Alex Bennee
2003-02-05 17:28 ` Chris Friesen
2003-02-05 17:31 ` Russell King
2003-02-05 19:15 ` Alan Cox
2003-02-05 19:02   ` Nilmoni Deb
2003-02-05 19:12     ` Daniel Jacobowitz
2003-02-05 21:11       ` Nilmoni Deb
2003-02-06 23:06         ` Bill Davidsen
2003-02-06 23:59           ` Nilmoni Deb
2003-02-09 14:52             ` Bill Davidsen
2003-02-09 16:50               ` Nilmoni Deb

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=20030212223115.AAA18900@shell.webmaster.com@whenever \
    --to=davids@webmaster.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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