From: David Woodhouse <dwmw2@infradead.org>
To: davids@webmaster.com
Cc: "Jp@Enix. Org" <jp@enix.org>, linux-kernel@vger.kernel.org
Subject: RE: Possible GPL infringement in Broadcom-based routers
Date: Sun, 07 Nov 2004 17:05:06 +0000 [thread overview]
Message-ID: <1099847106.4938.10.camel@localhost.localdomain> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKGEIEPJAA.davids@webmaster.com>
On Sat, 2004-11-06 at 12:09 -0800, David Schwartz wrote:
> This is exactly the argument I hoped would *not* arise on the LKML. I'll
> try not to reply further unelss someone posts something fundmanetally new.
>
> > Anyone copying and distributing the Linux kernel must comply with the
> > copyright licence which _conditionally_ grants them permission to do so.
>
> *sigh* We're not talking about anyone copying or distributing *the* Linux
> kernel. We're talking about someone copying or distributing another work
> that is derivative of the Linux kernel (which is also *a* Linux kernel, just
> not *the* Linux kernel). This is true whether they distribute the module
> separately or linked with the Linux kernel. In either case, they are not
> distributing the actual work placed under the GPL but a distinct, yet
> derivative, work.
Ah, OK. So as long as they change one line of code in the kernel, it's a
derivative work and they're no longer required to comply with the GPL?
They don't even need to use binary-only modules; they can put their own
proprietary code into their kernel, and distribute it how they like?
An interesting opinion.
--
dwmw2
next prev parent reply other threads:[~2004-11-07 17:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 18:43 Adam J. Richter
2004-11-05 19:59 ` David Schwartz
2004-11-06 3:23 ` David Woodhouse
2004-11-06 20:09 ` David Schwartz
2004-11-06 21:40 ` Stephen Pollei
2004-11-07 17:05 ` David Woodhouse [this message]
2004-11-06 13:38 ` Horst von Brand
2004-11-06 15:49 ` Arjan van de Ven
2004-11-07 21:08 ` Ryan Anderson
-- strict thread matches above, loose matches on Subject: below --
2004-11-06 10:40 Adam J. Richter
2004-11-05 18:51 ` Michael Poole
2004-11-05 18:58 ` Disconnect
2004-11-05 19:03 ` David Schwartz
2004-11-05 19:38 ` linux-os
2004-11-05 19:06 ` Horst von Brand
2004-11-05 19:39 ` Arjan van de Ven
2004-11-06 3:21 ` Kyle Moffett
2004-11-05 18:31 Adam J. Richter
2004-11-05 18:20 Adam J. Richter
2004-11-05 20:00 ` Michael Poole
2004-11-04 23:33 Jérôme Petazzoni
2004-11-04 23:57 ` David Schwartz
2004-11-05 0:23 ` Kyle Moffett
2004-11-05 15:27 ` David Woodhouse
2004-11-05 4:05 ` Scott Lockwood
2004-11-05 20:28 ` Tonnerre
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=1099847106.4938.10.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=davids@webmaster.com \
--cc=jp@enix.org \
--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
Powered by JetHome