*** This bug is a duplicate of bug 1357713 ***
https://bugs.launchpad.net/bugs/1357713
** This bug has been marked a duplicate of bug 1357713
Use essential "init" package to ensure that an init system is present
--
You received this bug notification because you are a member of Ubuntu
Bugs
@Martin Pitt: In my case this happened likely because I'm configuring my
system to be minimalist. This means that I'm removing all packages which
are not needed (and init wasn't needed for a working system). The
upgrade caused then that the new package upstart-sysv hasn't made it to
such systems wi
** This bug is no longer a duplicate of bug 1436956
Critical system files such as /sbin/shutdown and /sbin/init missing after
updating upstart
** Changed in: init-system-helpers (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1436956 ***
https://bugs.launchpad.net/bugs/1436956
As far as I know, in the scenario I described in my previous comment,
the "apt-get dist-update" process will NOT require the install of either
systemd-sysv or upstart-sysv. It will just update "upstart" to t
*** This bug is a duplicate of bug 1436956 ***
https://bugs.launchpad.net/bugs/1436956
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug 1436956
Critical system files such as /sbin/shutdown and /sbin/init missing after
updat
The idea is that the "Priority: required" init package is always
installed, which depends on systemd-sysv | upstart-sysv. upstart-bin is
history, that's "upstart" now (and as you already found out, upstart-
sysv now contains /sbin/init).
Any idea how "init" got missing on your system?
** Summary
