From: "Adam J. Richter" <adam@yggdrasil.com>
To: alan@lxorguk.ukuu.org.uk
Cc: aaronl@vitelus.com, acahalan@cs.uml.edu, adam@yggdrasil.com,
dledford@redhat.com, jas88@cam.ac.uk,
linux-kernel@vger.kernel.org, lk@tantalophile.demon.co.uk,
lm@bitmover.com
Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Mon, 28 May 2001 18:38:46 -0700 [thread overview]
Message-ID: <200105290138.SAA01532@baldur.yggdrasil.com> (raw)
> = Alan Cox
>> = lk@tantalophile.demon.co.uk?
>>> = ??
>>> AFAICS, the firmware is just a file served up to the device as needed
>>> - no more a derivative work from the kernel than my homepage is a
>>> derivative work of Apache.
>>
>> Indeed. But if you compiled your home page, linked it into Emacs to
>> display on startup, and distributed the binary, the _combination_
>> "Emacs+homepage" binary would be a derived work, and you'd be required
>> to offer source for both parts.
>In which case GNU Emacs violates the GPL by containing a copy of COPYING which
>is more restricted than the GPL. After all it displays copying on a hotkey
>combination
"M-x describe-copying" just displays the file
/usr/share/emacs/<version>/etc/COPYING. The emacs binaries do not
contain the text of GPL.
By the way, if one wanted to #include the text of the GPL,
then, in the specific case of the GPL, one could argue that the
restrictions on modifying the GPL are part of the GPL and, therefore
not further restrictions. (Even though those restrictions occur before
the "preamble", they're just as binding and removing them would be a
change to the GPL, so they are an existing restriction of the GPL rather
than a further restriction.)
That said, I have long advocated that authors use
GPL-compatible copying conditions for everything, including plain text,
to facilitate free software effects on platforms that comingle code
and documentation, such as many web pages and some other interactive
media.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
A
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
next reply other threads:[~2001-05-29 1:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 1:38 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-26 11:09 Adam J. Richter
2001-05-26 3:10 Adam J. Richter
2001-05-26 11:00 ` James Sutherland
2001-05-29 0:03 ` Jamie Lokier
2001-05-29 0:24 ` Alan Cox
2001-05-29 0:55 ` Jamie Lokier
2001-05-26 2:34 Adam J. Richter
2001-05-26 2:38 ` Larry McVoy
2001-05-26 4:52 ` Jeff V. Merkey
2001-05-25 17:02 Adam J. Richter
2001-05-25 17:23 ` Jacob Luna Lundberg
2001-05-25 18:30 ` Larry McVoy
2001-05-25 22:30 ` Aaron Lehmann
2001-05-26 1:43 ` Larry McVoy
2001-05-25 19:14 ` Doug Ledford
2001-05-25 10:36 Adam J. Richter
2001-05-25 9:34 Adam J. Richter
2001-05-25 16:06 ` Doug Ledford
[not found] <200105250559.f4P5x80365151@saturn.cs.uml.edu>
2001-05-25 6:03 ` Aaron Lehmann
2001-05-25 6:34 ` Alexander Viro
2001-05-25 6:42 ` Aaron Lehmann
2001-05-25 6:58 ` Alexander Viro
2001-05-25 7:02 ` Andreas Jaeger
2001-05-25 7:05 ` Alexander Viro
2001-05-25 10:56 ` Erik Mouw
2001-05-25 11:56 ` Alexander Viro
2001-05-25 12:44 ` Pavel Machek
[not found] <mailman.990765360.7016.linux-kernel2news@redhat.com>
2001-05-25 6:02 ` Pete Zaitcev
[not found] <Pine.BSF.4.21.0105242155540.4849-100000@beppo.feral.com>
2001-05-25 5:57 ` Aaron Lehmann
2001-05-25 6:26 ` Matthew Jacob
2001-05-25 6:31 ` Aaron Lehmann
2001-05-25 4:34 Aaron Lehmann
2001-05-25 5:07 ` Greg KH
2001-05-25 10:00 ` John Cavan
2001-05-25 11:10 ` Alan Cox
2001-05-25 16:17 ` Alan Cox
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=200105290138.SAA01532@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=aaronl@vitelus.com \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dledford@redhat.com \
--cc=jas88@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=lm@bitmover.com \
/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®