2011. december 21. 0:46 napon "Brian K. White"
I think your best option is to:
* make sure all large fs's are journaling (reiserfs, ext4, etc)
* drastically increase or disable altogether the periodic boot time scanning (not disabling the fsk if the fs is found to be dirty at boot)
* manually fsck once in a while if you like.
Because you can't predict when you will want to boot and run as fast as possible, and those times are _exactly_ the times you _don't_ want to have to futz with special boot prompt parameters.
You could also make a menu.lst stanza that just has fastboot added to it.
That way you could boot up fast without having to stop and enter special boot prompt options. Just select the fastboot entry instead of the regular entry.
fsck does process interrupt signals gracefully. You could possibly modify the initrc or other boot script to allow a break signal (ctrl-c) to reach the fsck process (it's probably trapped by a trap command before fsck runs normally, but you could edit the script with another trap command that releases that trap just before fsck). And aborting a read-only checkup fsck should always be safe.
But aborting fsck at all is just a really unwise habit to give yourself.
So I would do one of the other things that avoids running fsck in the first place.
Thank you again. I guess I should increase max mount count and also make a fastboot entry in menu.lst. If I know before boot that I need the system urgently I use fastboot, otherwise the regular boot with increased max mount numbers. Following the drives' states (actual mount count) is not an option as I have ~15 partitions, some mounted automatically, some by users if necessary. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org