Comment 26 for bug 559761

I've committed what I believe to be the correct fix to the plymouth bzr branch. With this change, mountall reliably emits all signals for me, instead of hanging like before.

The only remaining issue I see here is that trying to cancel fsck when there are more than 2 filesystem checks queued results in the additional ones marked failed and showing the 'i'gnore, 's'kip, 'm'aintenance prompt. Pressing 'i' succeeds in progressing for the first filesystem, but for the second filesystem there appears to be no reaction - the message stays on the screen and the boot stops. But as this isn't a regression (prior to this upload of plymouth, pressing 'C' to cancel fsck doesn't work *at all*), and the remaining problem doesn't appear to be a bug in plymouth (it appears to be a bug in mountall), I don't think it's a reason to block the plymouth half of this fix, at least. I've uploaded plymouth to the lucid unapproved queue.