From: jbradford@dial.pipex.com
To: rmk@arm.linux.org.uk (Russell King)
Cc: alan@lxorguk.ukuu.org.uk, andre@linux-ide.org,
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 13:17:27 +0100 (BST) [thread overview]
Message-ID: <200209171217.g8HCHRWt002001@darkstar.example.net> (raw)
In-Reply-To: <20020917130225.C28438@flint.arm.linux.org.uk> from "Russell King" at Sep 17, 2002 01:02:25 PM
> On Tue, Sep 17, 2002 at 12:17:53PM +0100, Alan Cox wrote:
> > On Tue, 2002-09-17 at 12:09, Russell King wrote:
> > > 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.
> >
> > Then you take them to the small claims court. Its their burden of proof.
>
> Ok. So the vendor gets out their technology that says "this drive
> has been exposed to excessive G force." So they have proof that it
> has been dropped by someone. However, the vendor can't prove that:
>
> 1. the vendor didn't drop it
> 2. the parcel company didn't drop it
> 3. you didn't drop it
>
> Conversely, you can't prove:
>
> 1. that the vendor dropped it
> 2. the parcel company dropped it
> 3. you dropped it (not that you'd want to)
>
> So its now their word against yours, and as you say, its up to the
> vendor to prove that _you_ caused the damage. Fortunately, this
> technology doesn't do that, so honest users might be safe for the
> time being.
Am I missing something, though, or is it not the case that if it has been dropped by the parcel company or the vendor, errors are likely to show up pretty soon if they are going to show up at all. You can't phone up 35 months in to a three year warranty, and expect them to believe, "Oh, the parcel company broke it, and it hasn't shown up because it damaged the last sector on the disk", (especially since most disks park the heads on the outside of the disk, so if that is the problem, you're going to notice it straight away).
I suppose that you could have a problem like a cracked spindle that didn't show up straight away, but realistically, if it's not your fault it got broken, then it's not likely to show up after a couple of years, is it?
John.
next prev parent reply other threads:[~2002-09-17 12:06 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
2002-09-17 11:17 ` Alan Cox
2002-09-17 12:02 ` Russell King
2002-09-17 12:17 ` jbradford [this message]
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=200209171217.g8HCHRWt002001@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@veltzer.org \
--cc=nuitari@balthasar.nuitari.net \
--cc=rmk@arm.linux.org.uk \
--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