On Jun 14, 2007, Daniel Hazelton <[email protected]> wrote:
> On Thursday 14 June 2007 15:13:31 Alexandre Oliva wrote:
>> On Jun 14, 2007, "Chris Friesen" <[email protected]> wrote:
>> > Alexandre Oliva wrote:
>> >> It's your position that mingles the issues and permits people to use
>> >> the hardware to deprive users of freedom over the software that
>> >> they're entitled to have.
>> > The software license controls the software. If the hardware has
>> > restrictions on it that limit what software it will run, then that is
>> > unrelated to the software license.
>> As in, the license controls the software. If a patent creates
>> restrictions that limit what you can do with the software, then that
>> is unrelated to the software license.
> No - because this case is covered in GPLv2. Lose the straw-men.
It's not a straw man. See, I was just showing that there's precedent
to ensuring that other tricks can't be used to deny users the freedoms
that the GPL is meant to defend.
By pointing out this is in the GPLv2, you acknowledge the point I
wanted to make.
So what is it that makes hardware so different that it can be used as
a trick to deny users freedoms, if other tricks can't?
> But that right has never been guaranteed by the GPL. It might have been the
> *intent* of RMS when he wrote GPLv1 and the *intent* of the FSF when they
> wrote GPLv2, but intent is worth exactly *NOTHING* in the law *UNLESS* that
> intent is spelled out.
That's the different between legal terms and the spirit. And the
promise of the GPL is to retain the spirit, to defend the freedoms.
>> That would be an unfortunate machine to have, but if Linux or some
>> other GPLed software was not shipped in it, then I don't see how this
>> is relevant to this discussion. It's not about the hardware, it's
>> about the software in it, and about passing on the freedoms related
>> with it.
> Exactly. However, you are making it about the hardware by making the claim
> that "replacing a program, in its entirety, with another is a modification".
> It isn't. A modification is when you replace or change a *portion* of a
> program. By your logic I could write an operating system that is 100% binary
> compatible with Linux and I'd be *required* to release it under the GPL,
> because, even though it *replaces* Linux, it's still a "modification".
I'm not sure I agree with the reasoning here, but I'm already
convinced that the argument about modification by replacement won't
fly.
But then again I ask you: why do you think TiVO is making these
hardware locks? What do they want to cause or stop?
--
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}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
