On Jun 19, 2007, "David Schwartz" <davids@webmaster.com> wrote:

quoted text
>> Right to control what software runs on the hardware is no different.
>> For any hardware on which I can run the software, I'm a user there,
>> and I'm entitled to the rights granted by the license.

quoted text
> Exactly. However, that right does not include the right to run the software
> on any particular piece of hardware.

I think that's correct, in general.  But when I receive the software
along with a particular piece of hardware, on which I'm to expected to
run it, I'm also receiving all other freedoms that ought to be
respected by whoever distributed the software to me, which means the
distributor can't impose restrictions on my running modified versions
of the program there (or anywhere else I can run the software, for
that matter).

quoted text
> It includes the right to run the software on *ANY* hardware, so long
> as one is authorized to choose what software runs on that hardware.

That's correct, too, with the provision that the distributor cannot
impose restrictions on running modified versions of the program.  Not
on any other hardware I can control, not on the hardware with which I
received the software along with the freedoms to control it in as far
as running the GPLed software goes.

quoted text
> You keep conflating things like access to the source code and the legal
> right to modify that source code with the authorization right to install
> that modified kernel on some particular piece of hardware. The GPL was never
> about how such authorization decisions are made.

That's correct.  All it says is that you can't impose further
restrictions.  This means you can't use anything (source code
deprivation, patents, copyright, authorization, nothing) to disrespect
users' freedoms.  Is this so hard to accept?  There's nothing special
about these authorization rights you're talking about that distinguish
them from copyrights or patent rights or any other rights.  The GPL
says: don't use them against users' freedoms regarding the GPLed
software.  No excuses.

quoted text
> If I make you a user of my laptop, do I have to let you install a modified
> kernel?

Does interacting with your laptop over the network make me a user of
your kernel?

quoted text
> What if I even let you access the kernel source, so I have
> distributed it to you.

You have distributed the source to me, I can modify it.

But did you distribute the kernel binary installed on your computer to
me?  That's the one I'm (possibly) using per the above.  Whether you
also gave me sources is irrelevant, unless you gave them to me as part
of your obligation of distributing the corresponding sources, in case
we conclude you distributed the kernel binary installed on your
computer to me when you granted me remote access to it.

And then, GPLv3 makes it clear that, in the case of remote access,
you're not conveying the binary to me, therefore the conditions for
conveying do not apply.

quoted text
> The GPL was never, ever about such authorization decisions. They are
> completely alien to both the wording and the spirit of the GPL.

You can repeat that as much as you want, this won't change the fact
that the GPL has never permitted you to use whatever rights you have
to impose restrictions on users' freedoms as to GPLed software once
you've (implicitly) accepted the conditions of the license.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}
-
unsubscribe notice
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/