> > This is frighteningly true, here are 2 suggestions, > > we probably need them both. > > 1) While an fsck is occurring in non-verbose startup mode > > we need a message to that effect with a progress bar. > > 2) On shutdown; if a routine fsck WOULD happen next reboot, > > the OS asks if the user minds converting the shutdown to a reboot. > > The fsck can happen on a fresh boot but not when the computer is needed. > > Once booted the system puts up a window a la Mac, > > waits 2 minutes and shuts back down automatically. > > With the fsck done, the next reboot happens normally. > Could you add those to the feature wishlist in our wiki so that it > does not get forgotten?
I don't want to sound too trolling ;), but this is just a workaround to a very unsatisfactory situation, nervertheless catapulting Linux back into archaic computing times for the average desktop user. I'm not a file system specialist and I don't want to become one, but why on earth has a file system in the 21st century to perform time consuming checks - with absolutely no other reasons for this behaviour apart from the fact that the system has been booted x times? If there is reason to assume that something might be wrong, then let the fs check itself - but not just because the computer has been sut off cleanly off a couple of times. As I said, I am no specialist, and I am no ReiserFS evangelic, but for me one of the biggest advantages of ReiserFS was that I was rid of the absolutely maddening periodic fs checks. While I understand the rationale for changing the default fs from a maintainer's point of view, I consider it major flaw from the end-users pov. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
