On Fri, 2003-12-26 at 15:57, David B. Stevens wrote:Generally it just complains that you pulled out the device prematurely, I've never seen one give a STOP error from that but I guess a bad driver or USB controller could cause anything.
While I agree that the kernel should provide decent error handling and reporting I still have to ask questions about what is reasonable.
What does that other OS do when you pull a USB stick out? What do you think the kernel should do? Why don't the applications operating on the data take better care of handling error conditions?
I don't have one here to try, but at some point the (ab)user needs to take a bit of the heat for his or her action(s) or lack thereof.
After all you could just reach in your case and rip out the IDE or SCSI cables. Bet that leads to all kinds of stuff (tm).
Cheers,
Dave
Helge Hafting wrote:
On Tue, Dec 23, 2003 at 11:42:17PM +0100, Jos Hulzink wrote:
Hi,You aren't supposed to do that. If you want to pull devices like that,
First of all... Compliments about 2.6.0. It is a superb kernel, with very few serious bugs, and for me it runs stable like a rock from the very first moment.
As an end user, Linux doesn't give me a good feeling on one particular item yet: Error handling.
What do I mean ? Well... for example: Pull out your USB stick with a mounted fs on it.
with no warning, access them in other ways than mounting. mtools are nice when you don't want to mount/umount floppies - a
similiar approach should work for usb sticks too.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Sometimes Windows 2k or XP dump (BSOD), or maybe you just get an error.