* debian/initscripts/lib/init/usplash-fsck-functions.sh:
- When pressing ESC, do not kill the logsave command (since this does not
reliably kill the subprocess), but the fsck.ext[23] processes directly.
(LP: #203322)
- When checking multiple partitions in succession, print the name of the
next device when it comes to its turn. NB that this still does not work
with checking multiple partitions in parallel, that's an fsck bug.
(LP: #203323)
- Use usplash 0.5.17's new FAIL_NO_USPLASH mode to avoid being stuck at
reading from the usplash FIFO if usplash died during fsck.
- Also output fsck progress information to the current console. This looks
quite dodgy ATM, but is better than not printing anything at all if
usplash died in between.
-- Martin Pitt <email address hidden> Wed, 26 Mar 2008 13:35:10 +0100
This bug was fixed in the package sysvinit - 2.86.ds1- 14.1ubuntu42
--------------- 14.1ubuntu42) hardy; urgency=low
sysvinit (2.86.ds1-
* debian/ initscripts/ lib/init/ usplash- fsck-functions. sh:
- When pressing ESC, do not kill the logsave command (since this does not
reliably kill the subprocess), but the fsck.ext[23] processes directly.
(LP: #203322)
- When checking multiple partitions in succession, print the name of the
next device when it comes to its turn. NB that this still does not work
with checking multiple partitions in parallel, that's an fsck bug.
(LP: #203323)
- Use usplash 0.5.17's new FAIL_NO_USPLASH mode to avoid being stuck at
reading from the usplash FIFO if usplash died during fsck.
- Also output fsck progress information to the current console. This looks
quite dodgy ATM, but is better than not printing anything at all if
usplash died in between.
-- Martin Pitt <email address hidden> Wed, 26 Mar 2008 13:35:10 +0100