Yes, this is a server on labs.online.net, using their "InstantApps" image named "Docker 1.3.2 + fig + nsenter + pipework + gosu".
Here are the outputs from aptitude:
root@labs-XXXXX:~# aptitude search upstart
p libupstart-dev
- Upstart Client Library (development files)
p libupstart1
- Upstart Client Library
p netscript-2.4-upstart
- Linux 2.4/2.6 router/firewall/VM host
network config. system.
i upstart
- event-based init daemon - essential binaries
v upstart-app-launch
-
v upstart-app-launch-tools
-
i upstart-bin
- event-based init daemon - transitional dummy
package
v upstart-compat-sysv
-
p upstart-dconf-bridge
- DConf bridge for upstart
v upstart-job
-
p upstart-monitor
- event monitor for upstart
p upstart-sysv
- event-based init daemon - SysV links
p upstart-watchdog
- watchdog jobs to reboot when system or
session jobs fail
root@labs-XXXXX:~# aptitude search systemd
p click-systemd
- Click hook for systemd unit
p dh-systemd
- debhelper add-on to handle systemd unit
files
p golang-go-systemd-dev
- Go client bindings for systemd socket
activation, journal and dbus
p libghc-libsystemd-journal-dev
- Haskell bindings to libsystemd-journal
v libghc-libsystemd-journal-dev-1.1.0-96c59
-
p libghc-libsystemd-journal-doc
- Haskell bindings to libsystemd-journal;
documentation
p libghc-libsystemd-journal-prof
- Haskell bindings to libsystemd-journal;
profiling libraries
v libghc-libsystemd-journal-prof-1.1.0-96c59
-
i A libpam-systemd
- system and service manager - PAM module
p libsystemd-daemon-dev
- systemd utility library (transitional
package)
p libsystemd-dev
- systemd utility library - development files
p libsystemd-id128-dev
- systemd 128 bit ID utility library
(transitional package)
p libsystemd-journal-dev
- systemd journal utility library
(transitional package)
p libsystemd-login-dev
- systemd login utility library (transitional
package)
i libsystemd0
- systemd utility library
p python3-systemd
- Python 3 bindings for systemd
i A systemd
- system and service manager
p systemd-cron
- systemd units to provide minimal cron daemon
functionality
p systemd-dbg
- system and service manager (debug symbols)
p systemd-gui
- transitional package for systemd-ui
v systemd-services
-
i A systemd-shim
- shim for systemd
p systemd-sysv
- system and service manager - SysV links
p systemd-ui
- graphical frontend for systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1436956
Title:
Critical system files such as /sbin/shutdown and /sbin/init missing
after updating upstart
Status in upstart package in Ubuntu:
Incomplete
Bug description:
1)
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2)
upstart:
Installed: 1.13.2-0ubuntu9
Candidate: 1.13.2-0ubuntu10
Version table:
1.13.2-0ubuntu10 0
500 http://mirror.cloud.online.net/ubuntu-ports/ vivid/main armhf
Packages
*** 1.13.2-0ubuntu9 0
100 /var/lib/dpkg/status
3) What you expected to happen
System continues to run normally with critical system files (listed below)
intact.
4) What happened instead
The following critical system files are all missing after updating the
upstart package using apt-get:
/sbin/halt
/sbin/init
/sbin/poweroff
/sbin/reboot
/sbin/runlevel
/sbin/shutdown
/sbin/telinit
This is a serious bug which could prevent rebooting/shutdown of the OS
and completely disable it due to missing /sbin/init.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1436956/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
