From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Blockbusting news, this is important (Re: Why are bad disk se ctors numbered strangely, and what happens to them?)
Date: 21 Oct 2003 12:10:22 -0700 [thread overview]
Message-ID: <bn40au$hdu$1@cesium.transmeta.com> (raw)
In-Reply-To: 785F348679A4D5119A0C009027DE33C105CDB2EF@mcoexc04.mlm.maxtor.com
Followup to: <785F348679A4D5119A0C009027DE33C105CDB2EF@mcoexc04.mlm.maxtor.com>
By author: "Mudama, Eric" <eric_mudama@Maxtor.com>
In newsgroup: linux.dev.kernel
>
> If current trends hold, in the next few years, hard drives are going to have
> to pick up and rewrite their data continuously to avoid signal decay on the
> media... a drive gets closer and closer to a DRAM cell than a stone tablet.
> (And yes, I've heard all the jokes about bricks/stones/etc)
>
Quite frankly, I think you'll have a hideously hard time selling that
to customers, once a few of them have lost their Quicken records due
to having had their computers turned off/disconnected for some time.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-10-21 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 17:18 Blockbusting news, this is important (Re: Why are bad disk se ctors numbered strangely, and what happens to them?) Mudama, Eric
2003-10-18 18:06 ` Matthias Urlichs
2003-10-20 15:54 ` Rik van Riel
2003-10-20 16:09 ` Richard B. Johnson
2003-10-20 16:24 ` Chris Friesen
2003-10-21 19:13 ` H. Peter Anvin
2003-10-20 17:49 ` John Bradford
2003-10-20 17:48 ` David Lang
2003-10-20 18:29 ` John Bradford
2003-10-21 19:10 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 16:14 Mudama, Eric
2003-10-18 16:54 Mudama, Eric
2003-10-18 18:19 ` Maciej Zenczykowski
2003-10-18 20:08 ` John Bradford
2003-10-19 22:53 ` Pavel Machek
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='bn40au$hdu$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.