For the record, the chroot is done here: # Work around absolute symlinks if [ -d "${rootmnt}" ] && [ -h "${rootmnt}${checktarget}" ]; then case $(readlink "${rootmnt}${checktarget}") in /*) checktarget="$(chroot ${rootmnt} readlink ${checktarget})" ;; esac fi
So if chroot doesn't work, we would indeed fail if /sbin/init is an absolute symlink. However, /sbin/chroot is supposed to exist in the initramfs: $ zcat /initrd.img |cpio -tv | grep chroot -rwxr-xr-x 141 root root 0 Oct 27 09:40 sbin/chroot How does that look for you? Perhaps you have a different initramfs config which skips that? ** Package changed: systemd (Ubuntu) => initramfs-tools (Ubuntu) -- 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/1421117 Title: fails to boot with "Attempted to kill init" in VMWare, absolute /sbin/init symlink does not work Status in initramfs-tools package in Ubuntu: Incomplete Bug description: My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after permanently switching to systemd. I've switched to systemd with "apt install systemd-sysv --purge" (it only purged the upstart package) and with the default "Ubuntu" entry the boot fails after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it works when edit the grub entry (in the grub shell) and add "init=/lib/systemd/systemd". Attached is the serial output (with "debug" but no "init=" parameter). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1421117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp