Re: Changes to ide-probe.c in 2.6.9-rc2 causing improper detection

[Jens Axboe <axboe@suse.de>]

On Tue, Sep 14 2004, Alan Cox wrote:
> On Maw, 2004-09-14 at 12:12, Jens Axboe wrote:
> > > Drive acked the command is all that proves. Maybe its a nop, maybe it
> > > does it, maybe like the last time someone engaged in this kind of "lets
> > > not check" approach it erases your firmware and leaves your CD-ROM drive
> > > defunct as the Mandrake error of the same form did.
> > 
> > Alan, you are sounding like a broken record :)
> 
> Thats because someone else appears incapable of listening and learning
> that issuing commands that may not be safe is not a good idea. I happen
> to think users should be able to expect their hardware not to go boom

If you had actually read the mail, you'd see that this was just an
experiment to see what kind of drive he had. I'm not suggestion to add
this back to the kernel.

> I've nothing against a well documented "actually I have a cache" option
> with appropriate warnings (and of course possibly a whitelist if we can
> get vendors to help). But one that like hdparm does bother to note when
> you may be playing with fire.

You should be able to turn on support from user space, if you so wish,
if you know that the drive works.

-- 
Jens Axboe