Oh ho,
I'll blame the lack of sleep, lack of coffee, the heat, a flat tyre...
something :)
Someone has pointed out that bad144 was taken outta the source tree ages ago
so I must have been using an old binary.
No comments required, I have flamed myself privately :)
Kent Ibbetson
[EMAIL PROTEC
Hi again,
On 26-Feb-00 Kelly Yancey wrote:
> On Sun, 27 Feb 2000, kibbet wrote:
>
>> Hi all,
>>
>> Quick question, how does the new ata driver handle bad blocks?
>> I've been tracking -current since around Nov 99 but haven't
>> seen this come up.
>
> As I recall, it doesn't. The reasoning is t
On Sun, 27 Feb 2000, kibbet wrote:
> Hi all,
>
> Quick question, how does the new ata driver handle bad blocks?
> I've been tracking -current since around Nov 99 but haven't
> seen this come up.
As I recall, it doesn't. The reasoning is that modern IDE drives perform bad
block reassignment so
On Sun, Feb 27, 2000 at 02:39:03AM +1030, kibbet wrote:
> Hi all,
>
> Quick question, how does the new ata driver handle bad blocks?
> I've been tracking -current since around Nov 99 but haven't
> seen this come up.
ad does not any longer support bad144 (IIRC). Soeren can tell you more.
--
Wil
In message <[EMAIL PROTECTED]>, kibbet writes:
>This message is in MIME format
>--_=XFMail.1.3.p0.FreeBSD:000227023903:2009=_
>Content-Type: text/plain; charset=us-ascii
>
>Hi all,
>
>Quick question, how does the new ata driver handle bad blocks?
>I've been tracking -current since around Nov 99 bu
