> It must be nice to live in such a perfect world where one can replace disks
> instantly at the first sign of a problem. Why have such badblock code in the
> kernel in the first place -- just insist that all your users have error-free
> drives.
We demand the same from memory.
> But out here in the real world we don't have such a luxury. It could be days
> before a drive can get replaced. In the meantime, we have to make do.
It would bloat the kernel with uncertain success - so if this is desired at
all, do it in userspace somehow.
Regards,
bert hubert..
--
| http://www.rent-a-nerd.nl
| - U N I X -
| Inspice et cautus eris - D11T'95
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/