← Back to team overview

touch-packages team mailing list archive

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

 

This is coming from "init" line284:

                 case $(readlink "${rootmnt}${checktarget}") in /*)

That's the readlink that isn't found (not the chrooted one in the next
line). I added a few debugging steps, and "type readlink" says "readlink
is readlink". I cannot reproduce this in break=bottom, in the
interactive shell readlink /root/bin/systemd works just fine. But as
soon as I Ctrl+D, readlink doesn't work any more. Some subtle busybox
difference between interactive and shell script mode?

It works if I replace this with

                 case $(/bin/busybox readlink
"${rootmnt}${checktarget}") in /*)

but that's not a proper solution but a workaround.


** Summary changed:

- Boot fails if /sbin/init is an absolute symlink
+ Boot fails if /sbin/init (or init= arg) is an absolute symlink

-- 
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