[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
Theoretically https://bugs.launchpad.net/ubuntu/+source/init-system- helpers/+bug/1436691 is a duplicate of this report but the first symptoms haven't revealed this. And as I have figured out later that this happened because init is not essential I haven't remembered this ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
This is the case now in vivid, "init" is essential and ensures that systemd-sysv or upstart-sysv is installed. ** Changed in: init-system-helpers (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
Sometimes cgmanager starts up under systemd, then things break (I haven't seen it break up to the point of not booting, though). You can try installing systemd-sysv and removing cgmanager to verify this. Please feel free to report a new bug against systemd for this, as this is different from enforcing which init system is installed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
Martin Pitt wrote: "Right, that will switch the default init to systemd. If you want to experiment with that, you can do either that or boot with init=/bin/systemd (you don't need both)." Well I did test that with my high-end setup (Intel Core i7 4790 + Asus Z97 Sabertooth + Samsung 850 Pro SSD) using CPU integrated GPU (Intel HD 4600). 1. If I only install systemd-sysv (thus upstart, upstart-bin and ureadahead are removed) and not do the kernel line addition, the setup will not boot at all. It will stop early complaining having init issues. 2. If I then recover the setup by chrooting (live USB) and re-installing upstart and upstart-bin plus removing systemd-sysv), the setup boots OK. 3. If I then only add the kernel line: init=/lib/systemd/systemd, the setup boots well, using systemd. Note: systemd-sysv not installed. 4. Lastly I tested booting by reinstalling systemd-sysv and removing all this: upstart, upstart-bin, systemd-shim, cgmanager, libcgmanager0, ifupdown, libjson0. The setup boots well. Note: the kernel line addition in use. So, at least for me only installing systemd-sysv will break the setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
> ubuntu-minimal depends on upstart and ifupdown, so supposedly you removed that. This is really not a supported configuration. If this is not officialy supported I recommend to make ubuntu-minimal essential in this case. At least removing it is currently a valid configuration. > Debian has a new essential package "init" which depends on systemd-sysv | > upstart | sysvinit. We could decide to adopt that. > Systemd (or perhaps something else too), does that as well. You can install systemd-sysv, purge ifupdown and upstart, and lo will be up. This sounds like a possible solution for this problem then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present
> First of all, for the removal of upstart, one must install package systemd-sysv. Right, that will switch the default init to systemd. If you want to experiment with that, you can do either that or boot with init=/bin/systemd (you don't need both). This is indeed not officially supported yet as there are still some hundred packages to update which only have upstart jobs, but for a day to day desktop it works quite fine these days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357713 Title: Use essential "init" package to ensure that an init system is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1357713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
