FS#18400 - [initscripts] Users should be allowed to skip a forced filesystem check on boot

Attached to Project: Arch Linux
Opened by Rorschach (Rorschach) - Friday, 19 February 2010, 16:29 GMT
Last edited by Jan de Groot (JGC) - Saturday, 20 February 2010, 13:38 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
The forced filesystem checks on boot are a good idea. But sometimes this can be really annoying for a user, who needs fast access to his system and first is forced to wait until the checks have finished. Some filesystems like ext2 or ext3 need a long time on big partitions...

To fix this the user should be able to abort this check and access his system. The next time the user boots again, the checks are run again. This is the way other distributions like ubuntu handle it in the moment too.

The patch in the attachment is pretty small and unintrusive and extends /etc/rc.sysinit by giving the user the ability to abort the filesystem checks with pressing the escape-key.(Be aware that you can't copy and paste the patch because the escape-key character won't be copied correctly through the paste and this will result in the escape-key not being correctly recognized when pressing it and thus you can't abort...)


Affected package:
core/initscripts 2010.01-1

File to patch:
/etc/rc.sysinit


   abort_fsck_rc.sysinit.patch (1.3 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 20 February 2010, 13:38 GMT
Reason for closing:  Won't implement
Comment by Thomas Bächler (brain0) - Friday, 19 February 2010, 21:34 GMT
So, what does this do that pressing Strg+C during boot doesn't?
Comment by Jan de Groot (JGC) - Saturday, 20 February 2010, 00:10 GMT
I'm pressing Ctrl+C at bootup for months now, and all I see is just "[FAIL]" instead of "[OK]". I'm ok with that, as aborting something on bootup is reason for failure.
Comment by Rorschach (Rorschach) - Saturday, 20 February 2010, 12:52 GMT
Okay, shame on me that I never thought about pressing ctrl+c! This works flawlessly, thus this feature request can be closed and forgotton..

Loading...