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 *why* plymouth was pulled into your initramfs.
If you want to override the standard behavior, you can add a file to
/etc/initramfs-tools/conf.d/ that sets FRAMEBUFFER=n to override the
inclusion of plymouth in the initramfs. If you want to avoid splash
screens altogether, you can remove 'splash' from the boot commandline.
This will not stop plymouth from being run by init, because it's still
needed to handle I/O for processes such as mountall which need to
communicate with the user at boot time in the event of filesystem
problems.
The default behavior is correct for the common case, and if you really
need a custom prompt instead of the standard cryptsetup script, it's
overridable, so I'm closing this report as invalid.
** Changed in: plymouth (Ubuntu)
Status: New => Invalid
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
--
plymouth breaks 'read' in initramfs
https://bugs.launchpad.net/bugs/665789
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
