From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andre Hedrick <andre@linux-ide.org>,
jbradford@dial.pipex.com, Nuitari <nuitari@balthasar.nuitari.net>,
venom@sns.it, linux-kernel@vger.kernel.org,
xavier.bestel@free.fr, mark@veltzer.org
Subject: Re: Hi is this critical??
Date: Tue, 17 Sep 2002 12:09:37 +0100 [thread overview]
Message-ID: <20020917120937.B28438@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1032259304.13990.5.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Tue, Sep 17, 2002 at 11:41:44AM +0100
On Tue, Sep 17, 2002 at 11:41:44AM +0100, Alan Cox wrote:
> On Tue, 2002-09-17 at 09:20, Andre Hedrick wrote:
> > MORONS that think the drive vendors are not clued into the issue.
> > I have to read and vote on NASTY proposals, whose intent is to check for
> > G-Force damage. If you think that record is not findable, even if you
>
> Sounds good news for honest users. What it does want though is the
> ability of users to check that data when the disk arrives, because we
> have delivery people, and they think that if looks like a box its
> probably a football.
No. Sounds _bad_ news for honest users. Lets be realistic here.
Parcel company uses package as a football, then delivers it.
How many parcel companies will wait while you unpack the hard drive,
dismantle your machine, connect the drive, power it up and check to
see if the drive has suffered too much shock?
Yep, that's right, none. If you try to, the parcel delivery person
will get really ratty. So you sign for it after checking that the
outside box is undamaged.
Then you find out that its been used in the world cup. You try to
return it to the vendor, but the vendor says its your fault for
dropping the drive. You protest, but the vendor refuses to listen
because they've got their technology that says so in their product.
So, its NOT great for honest users. Its another form of "Digital
Rights Management."
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-09-17 11:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 20:05 2.4.19 - not a real problem raptor
2002-09-16 13:31 ` Hi is this critical?? louie miranda
2002-09-16 13:34 ` DevilKin
2002-09-16 13:37 ` venom
2002-09-16 13:47 ` Xavier Bestel
2002-09-16 14:16 ` Mark Veltzer
2002-09-16 14:14 ` Xavier Bestel
2002-09-16 15:57 ` venom
2002-09-16 23:23 ` Nuitari
2002-09-16 18:27 ` jbradford
2002-09-16 22:46 ` venom
2002-09-17 5:18 ` Nuitari
2002-09-17 8:02 ` jbradford
2002-09-17 8:20 ` Andre Hedrick
2002-09-17 10:41 ` Alan Cox
2002-09-17 11:09 ` Russell King [this message]
2002-09-17 11:17 ` Alan Cox
2002-09-17 12:02 ` Russell King
2002-09-17 12:17 ` jbradford
2002-09-17 12:02 ` jbradford
2002-09-17 18:39 ` Bill Davidsen
2002-09-18 6:00 ` Daniel Berlin
2002-09-17 17:34 ` Andre Hedrick
2002-09-17 17:54 ` Russell King
2002-09-17 19:30 ` jbradford
2002-09-17 18:34 ` Bill Davidsen
2002-09-18 5:56 ` Daniel Berlin
2002-09-17 18:23 ` Bill Davidsen
2002-09-16 14:43 ` Russell King
2002-09-17 8:40 ` Rogier Wolff
2002-09-17 9:03 ` jbradford
2002-09-16 14:53 ` Alan Cox
2002-10-05 12:58 ` 2.4.19 - not a real problem Adrian Bunk
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=20020917120937.B28438@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@veltzer.org \
--cc=nuitari@balthasar.nuitari.net \
--cc=venom@sns.it \
--cc=xavier.bestel@free.fr \
/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