> They have the same problem, you're supposed to unmount volumes the same > way for the same reasons, to make sure everything is synced, to make > sure no other programs try to write the disk (MS word auto-backup) and > the like. It just so happens that no one likes un-mounting floppies so > there's always been an exception there.
Oops, small self-correction here, I forgot, this is in the way FAT works. FAT12/16/32 writes look like this: 1) Write data. 2) Update FAT table 1 3) Update FAT table 2 If you loose media during any stage, you'll end up with the following respectively: 1) Garbage clusters. 2) A corrupt FAT1 table, but a clean FAT2 table and lost clusters. 3) A clean FAT1 table, which is correct, so you can update FAT2. Of course, *nix can use near-any FS on removable media besides FAT, which may not be so robust, which is why it's not so simple to just pull out the drive, hence our situation. -Jason _______________________________________________ Usability mailing list [email protected] http://mail.gnome.org/mailman/listinfo/usability
