From: "David Schwartz" <davids@webmaster.com>
To: <erikharrison@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: more files with licenses that aren't GPL-compatible
Date: Wed, 16 Jun 2004 14:21:56 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKIEKKMKAA.davids@webmaster.com> (raw)
In-Reply-To: <5b18a542040616133415bf54d1@mail.gmail.com>
> On Tue, 15 Jun 2004 21:11:00 -0700, David Schwartz
> <davids@webmaster.com> wrote:
> > They can't grant that permission. Every single person
> > who had contributed
> > to the Linux kernel would have to agree. The GPL prohibits including
> > software that isn't itself GPL'd from being combined with GPL'd
> > software.
> > The issue is not permission to distribute this driver, the issue is
> > permission to distribute the *kernel*. The kernel's license prohibits
> > distrubiting it in combination with works that have licenses more
> > restrictive than the GPL.
>
> That better be bogus, or else vendors are going to be very upset that
> they can't ship the kernel with, say, trademarked images. For example,
> Mozilla's trademark on their artwork is fairly restrictive, or the
> Mandrake Firewall product (if that's even still around - I don't keep
> up).
I can't speak to the trademark issue. I don't know enough about how the GPL
deals with possible trademark issues. I believe you could not embed
trademarked images into the kernel and distribute the result either.
However, this is a pure copyright issue. You cannot combine GPL'd code with
code that has a more restrictive license and distribute the resulting
binaries. Read GPL section 2b:
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet *all* of these conditions:
...
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
How can you cause the Linux kernel combined with this firmware to be
licensed under the terms of the GPL? (And, by the way, I think this
prohibits trademark as well, which is very interesting.)
DS
next prev parent reply other threads:[~2004-06-16 21:22 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:57 Christoph Hellwig
2004-06-16 0:38 ` Eric
2004-06-16 1:27 ` Kyle Moffett
2004-06-16 4:11 ` David Schwartz
2004-06-16 20:34 ` Erik Harrison
2004-06-16 20:37 ` Christoph Hellwig
2004-06-16 21:21 ` David Schwartz [this message]
2004-06-16 22:45 ` Oliver Neukum
2004-06-16 23:45 ` David Schwartz
2004-06-17 14:09 ` Timothy Miller
2004-06-17 18:35 ` David Schwartz
2004-06-17 19:22 ` Timothy Miller
2004-06-17 7:59 ` Christoph Hellwig
2004-06-17 8:43 ` Oliver Neukum
2004-06-17 8:47 ` Christoph Hellwig
2004-06-17 10:09 ` Martin Diehl
2004-06-17 10:14 ` Christoph Hellwig
2004-06-19 18:29 ` David Woodhouse
2004-06-17 14:04 ` Timothy Miller
2004-06-16 22:49 ` Helge Hafting
2004-06-18 9:08 ` Adrian Cox
2004-06-18 11:21 ` Kyle Moffett
2004-06-16 23:47 Wichmann, Mats D
2004-06-17 1:18 ` Kyle Moffett
2004-06-18 6:29 Adam J. Richter
2004-06-17 15:44 ` Michael Poole
2004-06-17 17:09 ` Adam J. Richter
2004-06-17 19:14 ` Kyle Moffett
2004-06-17 20:51 ` Flavio Stanchina
2004-06-17 20:53 ` Kyle Moffett
2004-06-17 21:05 ` mdpoole
2004-06-17 21:10 ` Christoph Hellwig
2004-06-17 21:45 ` Flavio Stanchina
2004-06-17 20:22 ` mdpoole
2004-06-17 18:05 ` Greg KH
2004-06-17 19:54 ` Christoph Hellwig
2004-06-17 20:22 ` Greg KH
2004-06-17 20:30 ` Christoph Hellwig
2004-06-17 20:52 ` Greg KH
2004-06-18 6:56 Adam J. Richter
2004-06-18 11:09 ` mdpoole
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=MDEHLPKNGKAHNMBLJOLKIEKKMKAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=erikharrison@gmail.com \
--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®