Public bug reported:
>From the plymouth changelog:
plymouth (0.8.1-1) lucid; urgency=low
* Restored code to disable Plymouth's graphical plugins when an alternate
init= is given on the kernel command-line, otherwise init=/bin/bash
doesn't work so well when Plymouth is in the initramfs.
What I want to do is to put "init=/sbin/ltsp-init", which prepares a
netbooted cow file system for live booting, and then exec's /sbin/init
to continue with the boot process.
Could you please restrict the graphical plugin disabling code to
"init=/bin/bash", or at least to "init=/bin/*" ?
Or even if you just allowed "init=/sbin/init*", we could name ours
"/sbin/init-ltsp".
I know I can use "plymouth:force-splash" in the kernel command line to
force loading the graphical plugins, but it's getting a bit complicated
for the end users.
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930865
Title:
Please don't disable graphical plugins for any alternate init=
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/930865/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
