touch-packages team mailing list archive

[Launchpad Bug Tracker <1434058@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

As seen in the failed systemd adt test at [1], installing 'upstart-bin'
and then booting a system with 'init=/sbin/upstart' does not result in a
fully functional system.  The problem is that there are many upstart
jobs provided by 'upstart' package that are essential to Ubuntu system
boot.

To recreate the problem, just launch a cloud-instance, or fresh install with systemd, then:
  sudo apt-get install upstart-bin
  set /etc/default/grub up appropriately and run 'update-grub' (adding 'init=/sbin/upstart to GRUB_CMDLINE_LINUX_DEFAULT).  Alternatively, you can just edit /bo
ot/grub/grub.cfg directly.
  reboot

System will not completely come up.

--
[1] https://jenkins.qa.ubuntu.com/job/vivid-adt-systemd/ARCH=amd64,label=adt/121/consoleFull

** Affects: upstart (Ubuntu)
     Importance: Critical
         Status: Confirmed

-- 
installation of upstart-bin and boot with init=/sbin/upstart does not fully boot
https://bugs.launchpad.net/bugs/1434058
You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu.