public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Thu, 31 Dec 2009 07:02:19 +0100	[thread overview]
Message-ID: <20091231060219.GA31304@boostbox> (raw)
In-Reply-To: <20091231045142.GC28130@kroah.com>

On Wed, Dec 30, 2009 at 08:51:18PM -0800, Greg KH wrote:
> On Wed, Dec 30, 2009 at 06:43:47AM -0500, Richard Freeman wrote:
> > On 12/29/2009 07:52 PM, Greg KH wrote:
> >> No, the readme/copying is correct, it covers all of the code that runs
> >> on the processor as one body of work.  Firmware blobs are different in
> >> that they do not run in the same processor, and can be of a different
> >> license.
> >>
> >
> > Yes, but they don't cover everything in the tarball.  If I want to copy the 
> > tarball, then I need to comply with the distribution license of the 
> > tarball.  That license isn't clearly advertised.  It is a mix of a number 
> > of licenses from GPL v2 to allowed-to-copy-without-modifications.
> 
> No, you can copy that tarball just fine, and when you _distribute_ it,
> the GPLv2 applies to it.

Then I can distribute modified versions of the tarball, with altered
firmware, in direct violation of the license granted for that firmware,
just because it's allowed by the GPL? Seriously, you're saying the
license of the firmware doesn't matter.

> > The processor that the software runs on is fairly irrelevant.
> 
> Not true at all, why would you think that?  Since when does a license
> cross a processor boundry?

When I copy the Linux kernel sources, all files are copied by a single
processor. This isn't about running the kernel.

> > In any case, I'm sure the kernel team will update the ebuild license string 
> > appropriately - this is more of a debate for the LKML.  I just don't think 
> > that they've done a good job with it.  Others are welcome to hold differing 
> > opinions.  :)
> 
> You don't think the gentoo kernel team (of which I think I'm the
> longest-term member), or the Linux kernel developers (of which I am the
> actual person who put those images in the kernel back in the late
> 1990's after consulting many lawers, and Linus, on the issue) are doing
> a good job with this?

Please stop avoiding the issue. No one is saying the firmware is in
conflict with the GPL, or that distribution of the kernel is illegal.
The way it's distributed is fine. It's just not reflected properly in
Gentoo.



  reply	other threads:[~2009-12-31  6:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  5:36 [gentoo-dev] Non-free software in Gentoo Vincent Launchbury
2009-12-28  8:10 ` Rémi Cardona
2009-12-28 13:11   ` Nirbheek Chauhan
2009-12-29  8:59     ` Peter Volkov
2009-12-29  5:24   ` Vincent Launchbury
2009-12-29  9:02     ` Peter Volkov
2009-12-29 18:32       ` Robin H. Johnson
2009-12-29 23:17         ` Brian Harring
2009-12-28 11:21 ` Jeroen Roovers
2009-12-28 14:37 ` Jeremy Olexa
2009-12-28 18:56 ` Robin H. Johnson
2009-12-28 22:15   ` Richard Freeman
2009-12-28 22:53     ` Robin H. Johnson
2009-12-29  1:16       ` Richard Freeman
2009-12-30  0:52         ` Greg KH
2009-12-30 11:43           ` Richard Freeman
2009-12-31  4:51             ` Greg KH
2009-12-31  6:02               ` Harald van Dijk [this message]
2009-12-30  0:50 ` Greg KH
2009-12-30  2:42   ` Vincent Launchbury
2009-12-31  4:48     ` Greg KH
2009-12-31 12:30       ` Richard Freeman
2010-01-06  4:55       ` Vincent Launchbury
2010-01-06 18:57         ` Greg KH
2010-01-06 21:55           ` Harald van Dijk
2010-01-07  6:19             ` Vincent Launchbury
2010-01-07 14:37               ` Richard Freeman
2010-01-08  5:26               ` Greg KH
2010-01-08 15:48                 ` Richard Freeman

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=20091231060219.GA31304@boostbox \
    --to=truedfx@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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