Theres a plea for review/accept at http://irclogs.ubuntu.com/2013/11/25/%23ubuntu-devel.html#t14:18 that is met with 2 questions:
a.) why isn't this in plymouth package (because slangasek requested it not be)
b.) why isn't this in cloud-init package (because its not at all related to cloud-init)
Rbasak mentioned that disabling plymouth does have fallout, for example lightdm is 'start on started plymouth'. Other upstart jobs on my system that mention plymouth are:
Theres a plea for review/accept at http:// irclogs. ubuntu. com/2013/ 11/25/% 23ubuntu- devel.html# t14:18 that is met with 2 questions:
a.) why isn't this in plymouth package (because slangasek requested it not be)
b.) why isn't this in cloud-init package (because its not at all related to cloud-init)
Rbasak mentioned that disabling plymouth does have fallout, for example lightdm is 'start on started plymouth'. Other upstart jobs on my system that mention plymouth are:
$ grep -r plymouth /etc/init -l | grep -v "/plymouth" console- font.conf lightdm. conf failsafe. conf setvtrgb. conf mountall. conf friendly- recovery. conf
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
lightdm and failsafe are the ones that seem most worrysome there.