public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Schwartz <davids@webmaster.com>
To: <dfawcus@cisco.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Tue, 11 Feb 2003 20:13:14 -0800	[thread overview]
Message-ID: <20030212041315.AAA26639@shell.webmaster.com@whenever> (raw)
In-Reply-To: <20030212032530.G5553@edinburgh.cisco.com>

On Wed, 12 Feb 2003 03:25:30 +0000, Derek Fawcus wrote:
>On Mon, Feb 10, 2003 at 01:33:20PM -0800, David Schwartz wrote:

>>However, without the GPL, you already had the right to possess 
>>and
>>use the original work. Without the GPL, the distributor already had
>>the right to possess and use the original work and to create
>>derived
>>works. There is no issue of distribution rights to the original
>>work
>>because everyone involved started with the right to use and possess
>>the original work.

>I don't know which legal system you're baing the above on (USA?),
>but
>from my understanding of UK law (CDPA 1988,  as ammended),  it's
>different.

	Primarily USA, but I don't agree with your analysis of UK law.

>The acts of redistributing a work [ 16 (1)(b) ],  or adapting a work
>(i.e. derived work) [ 16 (1)(e)] are reserved,  and as such lacking
>some form of licence would constitute infringement.

>So given the above,  your argument would seem to fail wrt UK law.

	This neither says nor implies that the right to distribute the 
original work and the right to distribute derived works are unique 
rights to the original work. I claim they are not.

	I would go further and argue that with source code, there is no 
distinction between use and the the creation of derived works. The 
primary way you would use a header file is to include it in a project 
(thus creating a derived work). The primary way would use the GCC 
source code is to compile it (this creating a derived work).

	We *use* source code to create derived works and for no other 
primary purpose. So I would argue that for source code, there isn't a 
distinction between being able to use the work and being able to 
create derived works.

	I believe this is part of the reason the GPL talks about modifying 
rather than creating derived works. However, the term "modifying" is, 
as far as I know, not a legally precise one. Does compiling a program 
"modify" it? Does linking to a library "modify" it? I don't think 
anyone really knows. Section 2 tries to equate modification with 
creating derived works, but then you'd have to figure out how you 
could use the source code to the Linux kernel in the intended way 
without compiling it.

	The puzzling thing is the GPL refers to things like "the act of 
running the program", though it's not clear how you could run most 
programs without compiling them first. If compiling them is 
unrestricted, then so is creating derived works.

	IANAL, but I know that nobody knows the answer to these questions.

	DS



  reply	other threads:[~2003-02-12  4:03 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 11:58 Monta Vista software license terms 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 [this message]
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
  -- 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-11 22:27 Larry McVoy
     [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
     [not found] <20030212213022.AAA17490%shell.webmaster.com@whenever>
2003-02-12 21:43 ` Valdis.Kletnieks
2003-02-12 22:31   ` David Schwartz
2003-02-12 23:04     ` Daniel Forrest
2003-02-12 23:28       ` 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=20030212041315.AAA26639@shell.webmaster.com@whenever \
    --to=davids@webmaster.com \
    --cc=dfawcus@cisco.com \
    --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