Boot fails if /sbin/init (or init= arg) is an absolute symlink
Bug #1351295 reported by
Martin Pitt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
Undecided
|
Dimitri John Ledkov |
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/
/init: line 307: readlink: not found
Target filesystem doesn't have requested /bin/systemd
and then a kernel panic.
Related branches
Changed in initramfs-tools (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
status: | New → In Progress |
tags: | added: systemd-boot |
To post a comment you must log in.
This is coming from "init" line284:
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
but that's not a proper solution but a workaround.