From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Thu, 31 Dec 2009 07:30:45 -0500 [thread overview]
Message-ID: <4B3C9975.80104@gentoo.org> (raw)
In-Reply-To: <20091231044831.GB28130@kroah.com>
On 12/30/2009 11:48 PM, Greg KH wrote:
>
> Heh, no, it does not, unless your BIOS, and your keyboard firmware, and
> your mouse firmware are all under a "free" license. The only thing
> close to this type of machine is the OLPC, and even then, I don't think
> all the microcode for the box was ever released.
>
> So it's a pointless effort.
Actually, you describe the futility of the effort, not the pointlessness
of the effort. The fact that an effort is difficult or even futile does
not make it pointless. Some might disagree about it being impossible as
well (there are open-source BIOS implementations, for example).
I'm sure the people who have such philosophies try to run free software
anytime that it is possible. They might not be able to run free
software on their microwave, but if one came out with an open-source
firmware they'd probably try to buy it. I don't see this as being
inconsistent, just practical. The fact that they can't buy an
open-source toaster or mouse doesn't mean that they can't use an
open-source kernel.
>
> Hint, these firmware blobs do not run on your processor, so they have
> nothing to do with the license of your "system".
I'm not really sure where you're coming up with this argument. The
purpose of a license is to ALLOW you to do something you otherwise
wouldn't be allowed to do. Licenses don't actually take away rights,
they grant them. Laws do take away rights. There is a law that says
that if I write a program and give it to you, you can't copy it and give
it to somebody else. However, if I give you a license to copy the file
under some conditions, then you can copy it legally if you follow those
conditions. Nowhere in copyright law is the word "processor" found or
implied - the technology used to copy is also irrelevant except to the
degree that it impacts fair use.
When you run software you aren't distributing it. The concept of a
use-license is a bit blurry - some people think that you don't need a
license to use software, and other people think you do. I don't believe
that court rulings are as uniform on the topic of use as they are on the
concept of copying. In any case, the GPL v2 does not in any way attempt
to restrict or grant the rights to use software - only to distribute it.
GPL v3 is a bit murkier in this regard, but irrelevant to a discussion
on the kernel.
>
> Again, no, the GPLv2 covers the license of all of the code you run in
> the kernel package.
The concern isn't about RUNNING the software - it is about DISTRIBUTING
the software.
> And again, you do not run those firmware images on your processor, so
> the point is moot.
Sure you do - you run them on your sound card processor, or your video
capture card processor, or whatever. However, the concern isn't running
the software, it is redistributing it.
>
> And note, _I_ placed those images in the kernel image, after consulting
> lawyers about this issue, so it's not like I don't know what I am
> talking about here.
Did they say that the GPLv2 applied to the entire tarball containing the
firmware? Or did they simply state that building/running kernels using
the tarball was legal?
Nobody is saying that the presence of the proprietary bits violates the
GPL (v1, v2, OR v3). You're not doing anything illegal.
However, the tarball is not licensed under the GPLv2. I can't modify
that tarball at will, for example, and redistribute it. If I modify 10
bytes in the middle of one of those firmware blobs, reassemble the
tarball, and post that on my website, I can be sued by the maker of that
firmware blob. I haven't violated the GPL in doing any of that - the
problem is that the firmware blob isn't licensed under the GPL.
The license to redistribute the gentoo-sources tarball is NOT GPLv2 - it
is GPLv2 for 98% of it, and a mix of other licenses for the rest. I
don't own a keyspan usb serial device, but that doesn't mean I can
modify the usa28.fw file and put it in a kernel tarball on my website,
as the license for that file SPECIFICALLY states that I'm not allowed to
do this and it is copyrighted. Doing this doesn't violate the GPL, but
the GPL doesn't apply to this file.
The point of this thread is that the gentoo-sources package is
mislabeled as GPLv2 when the entire package is not licensed under GPL
v2. Nobody is saying that it is illegal to distribute gentoo-sources,
only that it cannot be entirely distributed solely under GPLv2.
next prev parent reply other threads:[~2009-12-31 12:32 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
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 [this message]
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=4B3C9975.80104@gentoo.org \
--to=rich0@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