linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?
Date: Tue, 20 Jan 2009 16:30:28 +0100	[thread overview]
Message-ID: <20090120163028.63efeb1a@diego-desktop> (raw)
In-Reply-To: <85346.1232422345@turing-police.cc.vt.edu>

El Mon, 19 Jan 2009 22:32:25 -0500, Valdis.Kletnieks@vt.edu escribió:

> The $64 question is, of course: What exactly should the operating system
> *do* if it detects one of these drives?  Prohibit it from bricking later
> by essentially bricking it *now*?   What if the drive already has a lot of
> production data on it?

Yeah, that's why I asked. Now that I think about it, it should probably be
the HAL people who should add one of those desktop "bubbles" warning the
users about the possible failure (they already do it for faulty batteries)

  reply	other threads:[~2009-01-20 15:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 23:29 Faulty seagate drives, are going to be blacklisted? Diego Calleja
2009-01-20  0:22 ` David Rees
2009-01-20  2:55 ` Robert Hancock
2009-01-20 15:26   ` Diego Calleja
2009-01-21  0:30     ` Robert Hancock
2009-01-26 19:04   ` Felix Miata
2009-01-26 19:54     ` Mark Lord
2009-01-26 20:57       ` Gene Heskett
2009-01-26 21:34         ` Felix Miata
2009-01-26 23:56         ` Mark Lord
2009-01-20  3:32 ` Valdis.Kletnieks
2009-01-20 15:30   ` Diego Calleja [this message]
2009-01-20 17:24     ` Valdis.Kletnieks
2009-01-20 18:18       ` Diego Calleja
2009-01-21 10:27 ` Patrick Horn
2009-01-25  1:12   ` Tejun Heo

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=20090120163028.63efeb1a@diego-desktop \
    --to=diegocg@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-ide@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).