From: "David Schwartz" <davids@webmaster.com>
To: "Jp@Enix. Org" <jp@enix.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Possible GPL infringement in Broadcom-based routers
Date: Fri, 5 Nov 2004 11:59:23 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKOECKPJAA.davids@webmaster.com> (raw)
In-Reply-To: <200411051843.iA5Ih4q28451@adam.yggdrasil.com>
> The GPL is a grant of permission. So, if you have an activity
> that is restricted by copyright, you have to find something in the GPL
> that gives you permission. It's not just me saying that. A
> representative
> from the FSF explained that to room of ~50 lawyers and ~50 lay people
> at a seminar that I went to on it.
If that were true, I could poem up on a billboard and sue anyone who read
it. 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.
DS
next prev parent reply other threads:[~2004-11-05 20:03 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 [this message]
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
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=MDEHLPKNGKAHNMBLJOLKOECKPJAA.davids@webmaster.com \
--to=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
all inboxes | Powered by JetHome®