Karlos wrote:
EyeAm wrote:
Okay, Astral. :-)
EDIT: just can't leave without the Linux reply (to two above posts by others): It was definitely LINUX's fault, an upgrade of their software (and their upgrader sucks, more specifically). :lol: There, I'm done.
Which one? rpm? yum? apt-get? You obviously haven't a clue what you are talking about with regards to linux. What did you do, pull out a pen drive without properly unmounting it? User error. Maybe you should have set it up not to write cache removable media.
IMHO all that bunch of redundant programs that do the same are a problem because it shows lack of a properly accepted standard.
In the example of the pen drive the write cache should be disabled as default and advanced users should activate it to get extra speed. Most of users prefer to plug and unplug their pendrives when they want... if many users don't expect having to unmount anything it shows that certain Linux distros may lack user friendliness.
Was it your hard disk that went wonky? You don't know how to use fsck or replay the journal? Well, the OS can't really help that, other than by giving you extensive documentation on how to deal with such issues. How many other OS will let you unmount a drive at runtime, check it and even manually edit the disk's inodes if the disk has truly become damaged? Not many.
I guess any unix clone like linux will allow that. I think AmigaOS/MorphOS allows unmounting drives in a more or less legal way (at least with 3rd party commands) and you could edit any part of the disk (no memory protection, you know).
I'm not sure about QNX or BeOS but they'll probably allow it too. I guess the only one that may not allow it is Windows
