← Back to team overview

touch-packages team mailing list archive

[Bug 1351295] Re: Boot fails if /sbin/init (or init= arg) is an absolute symlink

 

Actually, i take that back. To support running upstart user sessions
under systemd-sysv, we'd need to split upstart package. In that case
upstart will ship /sbin/init which would be a symlink as well. Similar
to how systemd-sysv is packaged.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1351295

Title:
  Boot fails if /sbin/init (or init= arg) is an absolute symlink

Status in “initramfs-tools” package in Ubuntu:
  In Progress

Bug description:
  Booting current Utopic with init=/bin/systemd fails., or installing
  systemd-sysv fails. In both cases we are dealing with an absolute
  symlink "/bin/systemd -> /lib/systemd/systemd" or "/sbin/init ->
  /lib/systemd/systemd". I see:

  /init: line 307: readlink: not found
  Target filesystem doesn't have requested /bin/systemd
  and then a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1351295/+subscriptions


References