Thanks Steve for taking the time to explain. This is exactly it - people think that plymouth is only "annoying graphical stuff" without realizing that upstart is replacing the System-V init entirely - already has for the symlinks in /etc/init.d. And the way upstart communicates with the display (text or graphical - does not matter) is through plymouth. Which is why if you do a hacked removal of plymouth, upstart jobs don't show up on the boot messages - only the old System-V jobs do.
I have only ubuntu servers here but will take a look at desktop this week. If desktop has a progress bar during fscks, then I guess one approach might be to merge that with details so that we can toggle between them using <esc>? I don't think anybody would mind that much, so long as we have at least some way to get the progress info (graphical or otherwise).
Thanks Steve for taking the time to explain. This is exactly it - people think that plymouth is only "annoying graphical stuff" without realizing that upstart is replacing the System-V init entirely - already has for the symlinks in /etc/init.d. And the way upstart communicates with the display (text or graphical - does not matter) is through plymouth. Which is why if you do a hacked removal of plymouth, upstart jobs don't show up on the boot messages - only the old System-V jobs do.
I have only ubuntu servers here but will take a look at desktop this week. If desktop has a progress bar during fscks, then I guess one approach might be to merge that with details so that we can toggle between them using <esc>? I don't think anybody would mind that much, so long as we have at least some way to get the progress info (graphical or otherwise).