From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 2 to 3??
Date: Wed, 18 Jul 2007 19:41:57 -0500 [thread overview]
Message-ID: <200707181942.02458.bss03@volumehost.net> (raw)
In-Reply-To: <200707190148.38140.volker.armin.hemmann@tu-clausthal.de>
[-- Attachment #1: Type: text/plain, Size: 3436 bytes --]
On Wednesday 18 July 2007 06:48:38 pm Volker Armin Hemmann wrote:
> On Donnerstag, 19. Juli 2007, Stroller wrote:
> > On 18 Jul 2007, at 18:40, Volker Armin Hemmann wrote:
> [C]ould
> ANYBODY claim to be surprised by say Tivo?
Yes they can, since the move to DRM/TPM/etc. devices was unannounced and a
change from previous generations of the hardware. There's also the fact that
the code the TiVo runs *must have a signature as one of it parts* and like
any GPLv2 derivative, distributors (like TiVo) must provide the full and
complete source ("preferred form for modification") of all the parts, which
they have not.
This "signature requirement" is implicit in the GPLv2 and explicit in the
GPLv3. So was the patent license stuff. The GPLv3 is just a stronger, more
well-specified GPLv2. If you don't like the GPLv3, you probably didn't
*really* like the GPLv2 and might be more interested in licensing anything
you contribute under something like MIT/X11/BSD.
Those licenses allow others to take your code, cripple it, and sell it to you
(perhaps even on a device) for $100. Oh, and offer you an "upgrade" to (_the
same device_ running) your original code (which still has a few bugs, you
might want a support contract) for $10000.
> Plus, people who are discussing 'ethical' problems with locked hardware
> tend to forget, that there is enough hardware out there that a) needs an
> update once in a while but b) has to be temper proof by the user! You might
> want to read up about clinical equipment or FCC rules. Just for fun.
Actually, during the GPLv3 process, both these points (FCC and medical
equipment) were brought up and experts were brought in. It was determined
that there is no legal requirement to make such devices tamper-proof, if
upgrades are allowed at all.
Equipment distributors are already protected from lawsuits (and the like) once
a device is tampered with as long as they give the tamperer sufficient
warning.
There is no legal reason why devices must be upgradable by their distributor
but not by their owner, including devices under the auspices of the FCC or
medical devices.
> Some people need to realize that there is a fundamental difference between
> code and hardware.
The FSF knows there's a difference between code and hardware. However, there
is no difference between code on a HD and code on an EEPROM. (It's all just
readable and writable bits.) There's also no difference between code on a CD
and code on a ROM chip. (It's all just reabable bits.)
> And telling someone what he can do with HIS hardware is
> just wrong. You don't like the terms of the hardware vendor? Fine. Don't
> buy it. But buying it and than complaining is just lame.
If they sell it to me it is no longer their hardware. It's MINE. That's why
DRM shouldn't be allowed AT ALL, completely independent of the software
distribution requirements (not hardware requirements) that the GPLv3
specifies.
If TiVo was renting (really renting, not just "in name" like "$129 lets you
rent the device for 99 years") the devices, I would probably be on the other
side of this discussion.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-19 1:14 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 10:14 [gentoo-user] 2 to 3?? burlingk
2007-07-17 10:42 ` Abraham Marín Pérez
2007-07-17 11:01 ` Graham Murray
2007-07-17 12:48 ` Stroller
2007-07-17 16:19 ` Volker Armin Hemmann
2007-07-18 13:13 ` Stroller
2007-07-18 17:40 ` Volker Armin Hemmann
2007-07-18 18:10 ` Boyd Stephen Smith Jr.
2007-07-18 22:34 ` Stroller
2007-07-18 23:48 ` Volker Armin Hemmann
2007-07-19 0:41 ` Boyd Stephen Smith Jr. [this message]
2007-07-19 2:10 ` Stroller
2007-07-19 1:58 ` Stroller
2007-07-17 17:14 ` Boyd Stephen Smith Jr.
2007-07-17 19:29 ` Mike Edenfield
2007-07-17 22:05 ` [gentoo-user] " »Q«
2007-07-18 2:23 ` Mike Edenfield
-- strict thread matches above, loose matches on Subject: below --
2007-07-19 14:37 [gentoo-user] " burlingk
2007-07-19 6:13 burlingk
2007-07-19 5:59 ` Boyd Stephen Smith Jr.
2007-07-19 5:54 burlingk
2007-07-18 11:07 burlingk
2007-07-18 12:29 ` Dan Cowsill
2007-07-18 4:26 burlingk
2007-07-18 4:18 burlingk
2007-07-17 17:57 burlingk
2007-07-18 13:51 ` Stroller
2007-07-17 17:38 burlingk
2007-07-17 17:27 ` Boyd Stephen Smith Jr.
2007-07-18 12:38 ` Alan McKinnon
2007-07-18 14:13 ` Stroller
2007-07-18 16:15 ` Boyd Stephen Smith Jr.
2007-07-18 13:48 ` Stroller
2007-07-18 16:33 ` Boyd Stephen Smith Jr.
2007-07-17 12:12 burlingk
2007-07-17 11:29 ` Abraham Marín Pérez
2007-07-16 0:52 burlingk
2007-07-16 12:15 ` Mark Shields
2007-07-16 21:53 ` Jerry McBride
2007-07-17 1:26 ` Volker Armin Hemmann
2007-07-17 1:59 ` Boyd Stephen Smith Jr.
2007-07-17 1:26 ` Volker Armin Hemmann
2007-07-17 2:08 ` Henk Boom
2007-07-13 22:11 Jerry McBride
2007-07-13 22:27 ` Bo Ørsted Andresen
2007-07-18 9:28 ` b.n.
2007-07-18 16:23 ` Boyd Stephen Smith Jr.
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=200707181942.02458.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-user@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