DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer
         :mime-version:content-type:content-transfer-encoding;
        b=M9WaaORY0KwfUyqa5GCZHy09uLImMXPfsNmqQCcj9Fr54o6EER1ZqqkRZhikimZISm
         j9AUAO8GoruYUh6TBd9llu3eL/D5WlrDFdmqqWJdtYNyC1IjGDqllPdZnSrDBG5rkaxp
         sRCe8s8XvpwbKmZj6x7I5szN5A3zqukCMVcKQ=
Date: Tue, 20 Jan 2009 16:30:28 +0100
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?
Message-ID: <20090120163028.63efeb1a@diego-desktop>
In-Reply-To: <85346.1232422345@turing-police.cc.vt.edu>
References: <20090120002923.065f24ca@diego-desktop>
	<85346.1232422345@turing-police.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 793
Lines: 15

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)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/