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!
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!
FS#5386 - Unnecessary noise in the boot process
Attached to Project:
Arch Linux
Opened by Alex Merry (pippin) - Monday, 11 September 2006, 00:04 GMT
Last edited by Roman Kyrylych (Romashka) - Friday, 17 August 2007, 15:54 GMT
Opened by Alex Merry (pippin) - Monday, 11 September 2006, 00:04 GMT
Last edited by Roman Kyrylych (Romashka) - Friday, 17 August 2007, 15:54 GMT
|
DetailsIt's not a big thing, but...
During the boot process, the RAID and LVM setup produces output even when everything is working fine. This messes up the BUSY->DONE transition. In addition, the crypt setup code doesn't produce the "standard" notification - ie: BUSY->DONE - and the RAID setup doesn't show BUSY while it is generating nodes. The attached patches fix this. The cryptsetup one may be considered a bit blunt, seeing as it doesn't output errors (except for showing FAIL), but I couldn't see a straighforward way of getting round the fact that the tools in question output success messages to stderr. One of the patches is for rc.shutdown, since LVM has the same issue then. Note: the RAID patch assumes the fix in task 5385. It probably shouldn't, but it's easy enough to edit the patch and replace -e with -f in the node existance test. |
This task depends upon
rc.sysinit-raid_status.patch
I also added a stat_retval function to clean up the tests for an exit status.