On Mon, Jun 30, 2014 at 1:59 PM, Brian <a...@cityscape.co.uk> wrote: > On Mon 30 Jun 2014 at 13:42:51 -0400, Tom H wrote: >> >> Removing "splash" disables the bootsplash but it doesn't disable >> plymouth. With upstart, plymouth is the interface for fscking or >> decrypting a partition. > > Oh! I've never used Ubuntu in anger and thought the appearence of boot > messages meant it was disabled. Mind you, I only spent seven minutes on > it, unlike Steve Litt's seven years. And I've no axe to grind. > > I had got the impression that upstart and plymouth are intimately > connected but didn't look any further. Thank you for taking the time to > clarify the situation.
You're welcome. Even if the bootsplash is enabled, you can press esc to see the boot messages. AFAIR, if you press esc again, you'll go back to the bootsplash - but I'm not 100% sure. It's too far back fro me to be sure, but I think that Fedora used plymouth before it switched to upstart (plymouth is developed by an RH guy) so it is/was probably integrated into sysvinit too. But Uubntu had to work on integrating it into upstart and mountall - and upstart needs AFAIUI because it serialized input/output in spite of upstart's parallel boot model. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOdo=SxYAMu9yyKVK1gGB2PC7rARQAZr11Vkc8Sy9c=p6in...@mail.gmail.com
