On 2/26/06, Mark Lord <[email protected]> wrote:
> Jesper Juhl wrote:
> >
> > Or how about an option for the IDE driver to "not do that" that people
> > could enable if needed/wanted?
> > Or just change the code to "not do that" since we are no longer in the
> > mid-1990s?
>
> Well, yes. That's what I would do, were I still maintaining the IDE layer.
>
> But that code has become so twisted and confused since then,
> that a change like this is probably too risky/challenging for
> the current maintainers. It seems really easy to break stuff
> when touching parts of that code now, and people don't like it
> much when their hard drives get corrupted.
>
> But perhaps someone may successfully implement this.
>
Unfortunately my machines only have SCSI devices, so I'd have no way
to actually test a patch, otherwise I'd be happy to give it a shot - a
parameter to disable the behaviour shouldn't be too difficult to
implement, and if the default stays as the current behaviour then it
shouldn't be too controversial.
I wouldn't mind trying to hack up a patch, but it would be untested...
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
