public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 06 Nov 2004 03:23:24 +0000	[thread overview]
Message-ID: <1099711404.27598.44.camel@localhost.localdomain> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOECKPJAA.davids@webmaster.com>

On Fri, 2004-11-05 at 11:59 -0800, David Schwartz wrote:
> If that were true, I could poem up on a billboard and sue anyone who read it.

Your analogy is flawed. Consider instead the case where you want to sue
not someone who _read_ it, but someone who copied it down into their
notebook, went home and then published an anthology of poems including
yours. 

>  The FSF is, of course, free to take any position it wants to. As I
> understand the law, if you want to restrict use, you must restrict access.
> Give free access, you give free use.

Adam said 'an activity that is restricted by copyright', and in the
context it's blindingly obvious that he means _copying_ and
_distribution_, not just use. Yet you persist in your misdirection.

Anyone copying and distributing the Linux kernel must comply with the
copyright licence which _conditionally_ grants them permission to do so.

In particular, the permissions granted by the GPL on the Linux kernel
are conditional on your agreement that when you distribute a collective
work which is based in part on the Linux kernel, you also release all
other parts of that whole, EVEN THOSE WHICH ARE NOT DERIVED WORKS OF THE
KERNEL, under the terms of the GPL.

The GPL does not claim any fundamental 'rights' to those parts which are
your own work, just as commercial copyright licences don't claim any
fundamental 'right' to your money. It's just a trade you are offered;
that is what is asked of you, in return for permission to distribute the
GPL'd work.

You have the right to refrain from entering that agreement; to refrain
from distributing the GPL'd work. You do not have the right to
distribute the GPL'd work _without_ complying with the terms of its
licence. That would be a criminal offence.

Anyone distributing a work which is a whole based on the Linux kernel
and other non-GPL'd works, other than 'mere aggregation on a volume of a
storage or distribution medium', is quite clearly violating the terms of
the GPL. (Bearing in mind the specific exception for userspace).

It's very clear, given that the firmware for these routers is completely
useless without either the kernel or the network driver modules, that
it's more than 'mere aggregation' -- the parts form a coherent whole.

Thus, even when the modules are NOT a 'derived work', they _MUST_ be
distributed under the terms of the GPL in order for permission to
distribute the _kernel_ to be granted.

-- 
dwmw2


  reply	other threads:[~2004-11-06  3:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 18:43 Possible GPL infringement in Broadcom-based routers Adam J. Richter
2004-11-05 19:59 ` David Schwartz
2004-11-06  3:23   ` David Woodhouse [this message]
2004-11-06 20:09     ` David Schwartz
2004-11-06 21:40       ` Stephen Pollei
2004-11-07 17:05       ` David Woodhouse
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=1099711404.27598.44.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