[Bug 1357713] Re: Use essential "init" package to ensure that an init system is present

[Harry]

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
Server Team, which is subscribed to init-system-helpers in 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