Well, for someone who knows what they are doing, they *can* skip the check. They can simply boot into simple user mode, and use tune2fs to adjust mount count. Or, if you are booting using a plain text console, just edit /etc/e2fsck.conf, add:
[options] allow_cancellation = true This will allow ^C to work. However, if you are using a graphical boot, it's up to the graphical boot manager to forward the ^C to e2fsck, which is not my problem. Personally, I think it's a REALLY, REALLY BAD IDEA, given my understanding of what Ubuntu is aiming for. There are solutions for technically clueful users; they're just not obvious, as you proposed. If you don't know to boot into single user mode, you probably don't have enough clue to understand when it's safe to do this, and when not to. Also, note that for users who are complaining that fsck is freezing at "random places", there's almost some kind of hardware and/or kernel bug going on. Bypassing the fsck isn't going to help, and in fact, may cause much larger forms of data loss later on. -- fsck freezes on laptop https://bugs.launchpad.net/bugs/124773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
