mountall and plymouth

[Phillip Susi]

Much of the boot process has been migrated away from the sysV init
scripts that run serially and attached to the console.  Since the
startup processes are run in parallel their input and output would
become all jumbled.  This is the main reason plymouth was created: to
multiplex console IO.  It makes sure that output is displayed correctly
and that any required input is collected correctly.  Because of this you
can not run Ubuntu without plymouth.  If you don't want the graphical
splash screen, either press escape, or pass the "text" boot parameter.

Plymouth will work in text mode without fb.  If it is crashing, that is
a bug that needs fixed.

On 2/23/2011 10:43 AM, Lukas Hejtmanek wrote:
> Hi,
> 
> first of all, I'm running bleeding-edge unstable Ubuntu to test new features
> (and report bugs I got).
> 
> Now I have the following issue. I tried to unhold mountall from 2.9 version
> and I tried to install 2.22 (the current in unstable). It forced to install
> plymouth packages. I don't want them by world is not perfect, so I installed
> them anyway. 
> 
> However, I don't use initramdisk and I don't use any kind of framebuffer (just
> pure text). I got messages that plymouth got SIGSEGV (I guess because
> the framebuffer is not available) and subsequently, the mountall does not
> mount any file system which hurts a lot, mailny udev that does not start and
> subsequently whole system does not start.
> 
> So, what I could do? I definitely don't want to use frame buffer. I there
> a way how to disable plymouth to trying messing with fb? I want to see
> messages from kernel and from boot scripts. Does this way include functional
> mountall?
>