public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Harrison <erikharrison@gmail.com>
To: davids@webmaster.com
Cc: eric@cisu.net, Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org
Subject: Re: more files with licenses that aren't GPL-compatible
Date: Wed, 16 Jun 2004 16:34:25 -0400	[thread overview]
Message-ID: <5b18a542040616133415bf54d1@mail.gmail.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKEEFGMKAA.davids@webmaster.com>

On Tue, 15 Jun 2004 21:11:00 -0700, David Schwartz <davids@webmaster.com> wrote:
> 
> 
> > >     Permission is hereby granted for the distribution of this firmware
> > >     image as part of a Linux or other Open Source operating
> > >   system kernel
> > >     in text or binary form as required.
> 
>        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).

-Erik
> 
> > >     This firmware may not be modified and may only be used with
> > >     Keyspan hardware.
> 
>        That's more restrictive than the GPL. So if you link this with a GPL'd
> work, the entirety must be distributed under the GPL, which you can't do
> since you can't authorize the unrestricted use of the firmware
> 
> > > which makes the kernel as whole unredistributable.  A similar license
> 
>        Bingo.
> 
> > Unredistributable? Am I mistaken? It says permission is given to
> > redistribute
> > this piece as part of the linux kernel. You just can't modify it.
> > Although it
> > is unquestionably not a very permissive license, it's inclusion is not
> > detrimental to the kernel.
> 
>        He didn't say this made the firmware unredistributable, he said it made the
> *kernel* unredistributable. Since you can't GPL the firmware, the kernel as
> a whole is not GPL. You cannot distribute a non-GPL Linux kernel because the
> GPL prohibits it as the GPL applies to everything else in the kernel
> 
> > Please correct me if I am wrong.
> 
>        You *definitely* are wrong. The entirety of the GPL would be negated if you
> were correct.
> 
>        DS
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2004-06-16 20:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 20:57 more files with licenses that aren't GPL-compatible 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 [this message]
2004-06-16 20:37       ` Christoph Hellwig
2004-06-16 21:21       ` David Schwartz
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
  -- strict thread matches above, loose matches on Subject: below --
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=5b18a542040616133415bf54d1@mail.gmail.com \
    --to=erikharrison@gmail.com \
    --cc=davids@webmaster.com \
    --cc=eric@cisu.net \
    --cc=hch@lst.de \
    --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