From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Mudama, Eric" <eric_mudama@Maxtor.com>,
"'Hans Reiser '" <reiser@namesys.com>,
"'Wes Janzen '" <superchkn@sbcglobal.net>,
"'Rogier Wolff '" <R.E.Wolff@BitWizard.nl>,
"'John Bradford '" <john@grabjohn.com>,
<linux-kernel@vger.kernel.org>, <nikita@namesys.com>,
"'Pavel Machek '" <pavel@ucw.cz>,
"'Justin Cormack '" <justin@street-vision.com>,
"'Vitaly Fertman '" <vitaly@namesys.com>,
"'Krzysztof Halasa '" <khc@pm.waw.pl>
Subject: Re: Blockbusting news, results get worse
Date: Mon, 27 Oct 2003 18:34:48 +0900 [thread overview]
Message-ID: <3cba01c39c6f$141529a0$24ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C105CDB39B@mcoexc04.mlm.maxtor.com>
Eric Mudama wrote:
> 1. Pay a premium for longer warranty.
I've commented on this already.
> 2. Do qualification tests yourself during the first year of operation.
Yeah, I need to deliberately damage one block in order to test the firmware,
but I don't want to damage multiple blocks and use up the reallocation
space. I am a home user, even if I also do programming at work, even if I
also volunteer one day each weekend to test Linux. How can I arrange to
damage one block on a disk?
> 3. Look at what products are being shipped in large volume from OEMs, and
> buy the same product yourself. Dell or HP or IBM can't afford to ship
> products that don't have the lowest in-the-field failure rates, so buying
> what they buy would make sense since they'll run their own tests like #2.
I'm not sure how many Dell notebooks you'll have to open to see a Toshiba
drive, but I'll bet the number is low. Also do you recognize the name
Toshiba as a large maker of notebook PCs, and do you have any guesses as to
how many Toshiba notebooks you'll have to open to see a Toshiba drive?
Toshiba already reduced their former US 3-year warranties to 1 year and
provide 0 warranty directly to customers in Japan. (Maybe they should
follow the ideas of a certain dominant software maker and pretend to have a
90-day warranty but in fact renege every time a failure occurs? There would
be 0 difference in what needs to be done in software to make up for it.)
next prev parent reply other threads:[~2003-10-27 9:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 18:33 Mudama, Eric
2003-10-26 22:03 ` Andre Hedrick
2003-10-27 9:34 ` Norman Diamond [this message]
2003-10-27 10:23 ` Jan-Benedict Glaw
2003-10-27 23:31 ` Jason Lunz
2003-10-28 20:56 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 20:11 Mudama, Eric
2003-10-27 18:06 Mudama, Eric
2003-10-27 19:18 ` Andre Hedrick
2003-10-27 17:43 Mudama, Eric
2003-10-27 18:48 ` Hans Reiser
2003-10-27 19:47 ` Jeff Garzik
2003-10-27 20:03 ` John Bradford
2003-10-29 20:01 ` Pavel Machek
2003-10-30 8:30 ` John Bradford
2003-10-28 1:21 ` Pavel Machek
2003-10-28 12:54 ` Krzysztof Halasa
2003-10-27 13:07 Samium Gromoff
2003-10-26 22:12 Mudama, Eric
2003-10-26 7:37 Norman Diamond
2003-10-26 10:39 ` John Bradford
2003-10-26 9:41 ` Pavel Machek
2003-10-26 11:38 ` Norman Diamond
2003-10-26 11:56 ` Pavel Machek
2003-10-26 12:06 ` Hans Reiser
2003-10-26 13:59 ` Krzysztof Halasa
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='3cba01c39c6f$141529a0$24ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=R.E.Wolff@BitWizard.nl \
--cc=eric_mudama@Maxtor.com \
--cc=john@grabjohn.com \
--cc=justin@street-vision.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@namesys.com \
--cc=pavel@ucw.cz \
--cc=reiser@namesys.com \
--cc=superchkn@sbcglobal.net \
--cc=vitaly@namesys.com \
/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
all inboxes | Powered by JetHome®