[Bug 1351295] [NEW] Boot fails if /sbin/init is an absolute symlink

[Martin Pitt]

Public bug reported:

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.

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
     Assignee: Martin Pitt (pitti)
         Status: In Progress

** Changed in: initramfs-tools (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: initramfs-tools (Ubuntu)
       Status: New => In Progress

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

Title:
  Boot fails if /sbin/init 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