From: David Schwartz <davids@webmaster.com>
To: <oxymoron@waste.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Mon, 10 Feb 2003 13:33:20 -0800 [thread overview]
Message-ID: <20030210213349.AAA18154@shell.webmaster.com@whenever> (raw)
In-Reply-To: <20030210174245.GI28107@waste.org>
On Mon, 10 Feb 2003 11:42:45 -0600, Oliver Xymoron wrote:
>I certainly agree, but the problem is the NDA puts the shoe on the
>other foot and now it's the customer that has to consult a lawyer or
>risk a nuisance suit before proceeding. So while it may not forbid,
>it
>certainly discourages and impedes. Let me point out that I never saw
>the NDA in question but said coworker was sufficiently intimidated
>by
>it that he was unwilling to give me a copy of the kernel and gcc
>sources because of it.
I believe such a provision would, unfortunately, by considered
legally enforceable. The rationale would be that the rights you (the
recipient of the derived work) have under the GPL would only apply if
the distributor were bound by the GPL. The only way the distributor
could be bound by the GPL was if he or she did something that he
didn't have the right to do without the GPL to give him or her such a
right.
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.
You don't need to assent to the GPL to receive GPL'd works. You
don't need to assent to the GPL to modify GPL'd works. So the only
question would be, do you need to assent to the GPL to distribute a
modified work even if both you and the recipient of the work already
have the right to the unmodified work and the right to create such
modifications and you own the difference between the two works.
I've researched this question, and the evidence seems to suggest
that, no, it is not an additional right. Creating a derived work is a
right. Distributing the rights to the original work is a right. But
distributing a derived work when you can already create the derived
work, do not need to distribute any rights to the original work, and
own the rights to the difference between the two, does not seem to be
an additional right to the original work. It is the simple sum of the
rights both parties already have.
Or, to put it more simply, if you can use the linux kernel and
modify the linux kernel, you have pretty much all the rights to the
linux kernel that there are, and so does everyone else. Being able to
distribute a derived work you had the right to make to someone who
already had the right to possess the original work is not an
additional right to the original work.
IANAL, but I'm fairly familiar with copyright law. I'd be quite
interested in legal citations or court precedent to the contrary.
--
David Schwartz
<davids@webmaster.com>
next prev parent reply other threads:[~2003-02-10 21:24 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 [this message]
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
-- 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=20030210213349.AAA18154@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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