© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
The kernel probably does it right (one space). But the kernel has to communicate with udev which communicates with hal (transmission across several spaces).
device_connect . udev_called . hald_reads_
What if the device disconnects between hald receiving the connect message and mounting the filesystem? Or, what if the device is mounted, then disconnects and data is written to the device before hald receives the disconnect message?
But, if you see this without hal, then my argument does become very weak.
It's just that everytime I ran into "lost page write" or "buffer i/o errors" it apparently had something to do with a mismatch between what was perceived to be mounted and what was actually (not) mounted or vice versa.
David