Steve, Do you think this can be fixed in plymouth correctly?
If not, and you still would recommend .override files which of the following solutions would you think is best (or another you suggest): A.) 'disabler' package built by 'plymouth' source package (sugg name: plymouth-disabler) B.) 'disabler' package built by 'cloud-init' source package (sugg name: cloud-init-plymouth-disabler) Then, which mechanism for disabling would you think is the best solution: 1.) cloud-init installation of .override files via dpkg-divert in postinstall script 2.) cloud-init-plymouth-disabler package built by cloud-init Personally, it seems to me that 'A' is better than 'B', but I completely defer to your judgement on 1 or 2. I'd like to get this in as soon as possible in trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
