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
Desktop Bugs, which is subscribed to systemd 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1421117/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
