Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9850 - initscripts : kernel quiet option, rc.sysinit and filesystem check

Attached to Project: Arch Linux
Opened by Riri (chicha) - Sunday, 16 March 2008, 19:46 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 16 March 2008, 20:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Filesystem check (fsck) output is not displayed when kernel option "quiet" is set in the bootloader :

if grep -qw quiet /proc/cmdline; then
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK >/dev/null 2>&1
else
/sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null
fi

I think this is not an expected behavior from a user point of view : filesystem check information from fsck are important and might be critical if the check failed.

Morever when the harddisk is big (in term of storage) having the progress bar is very helpfull.
Having no info when the check is long is not good, one might think the system is frozen (I did the first time I added "quiet" to the kernel boot option).

Additional info:
* package version(s)
initscripts 2007.11-2

I considere this as a bug : I rebooted my sytem several times because I thought it was frozen and before I found out that init was just checking my 80GB partition ...

Thank you very much !
Chicha
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 16 March 2008, 20:06 GMT
Reason for closing:  Won't fix
Comment by Roman Kyrylych (Romashka) - Sunday, 16 March 2008, 20:05 GMT
I disagree, I think this *is* an expected behaviour.
When user uses 'quiet' option - (s)he expects kernel to *be quiet*, and usually the reason to use this option is the wish to have a nice splash as soon and as long as possible.
If you're concerned about no progress visible during fsck - I suggest to not use this option.
If you have some idea how this progress could be easily tracked and presented for splash - I will be glad to include your implementation.

Loading...