It likely is the same, yes.
Personally, I stopped caring. I got tired of ubuntu shoving things like
plymouth down our throats and came to realize that it was my fault for
realizing that ubuntu was not the appropriate distribution for my needs anymore.
It's meant for people who don't tinker with
Seems related to bug #595648.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665789
Title:
plymouth breaks 'read' in initramfs
To manage notifications about this bug go to:
Sorry, I'm going to re-open this because this is still an unaddressed bug:
- plymouth breaks initramfs' cryptsetup.
- it grabs stdin away from its shell scripts with no rationale as to why or how
to turn it off
- i t is utterly undocumented whch is unacceptable for a core piece of the
system
plymouth is the standard boot-time I/O multiplexer. The initramfs
script is not there for eye candy, it's there for the express purpose of
prompting for passphrases for encrypted filesystems. Why are you not
using the standard cryptsetup initramfs script here instead? The
cryptsetup hook is
[not sure if you get a reply on closed bugs, so Cc just in case. My
apologies if it's redundant]
On Sun, Oct 24, 2010 at 06:36:53AM -, Steve Langasek wrote:
plymouth is the standard boot-time I/O multiplexer. The initramfs
script is not there for eye candy, it's there for the express
