You are not logged in.
Today I did pacman -Syu and rebooted (didn't pay much attention what all got upgraded, but it wasn't a lot). Now I'm getting
Failed to execute /init (error -2)
Failed to execute /usr/lib/systemd/systemd (error -2)
So I booted from a USB stick and then chrooted to have a look, and /usr/lib/systemd/systemd is still there. ldd says it's not a dynamic executable, which is apparently not true. (Why does it say that? I've been noticing it lately on other libs and executables.) objdump -x | grep NEEDED shows it linking to libpcap.so.2 and several others, but there is no libpcap.so.2. So I tried linking libpcap.so -> libpcap.so.2, rebooted, and got the same error.
Surprised nobody ran into this... so I guess I must be missing something stupid.
Offline
Did you misread 'libcap'; because my init has no dependency on libpcap. If yours really does I'd run a rootkit scanner
Offline
What is in your pacman log?
Offline
You're right, it's probably libcap. So the libs it links with probably have nothing to do with this.
I'll look at the log on Friday.
Offline
I think it's the init in the initrd that is the problem, because when I remove the "quiet" option by editing the grub config before booting, I don't see any extra messages flying by: it's still just as quiet. systemd was not upgraded recently (but I upgraded it again just to be sure it wasn't corrupted in some way, while chrooted). However the initrd had already been rebuilt on the 19th, probably automatically as a result of installing some package. And I cannot rebuild it now with the chroot because the USB stick has a different kernel than the one on the disk, so the modules don't match (mkinitcpio complains that it can't find modules for 3.17.6-1-ARCH). Also tried reinstalling grub and regenerating grub.cfg, which of course didn't make a difference. Using the fallback initramfs also doesn't help. So maybe I'll copy an alternative kernel and initramfs and matching modules from a working system. Or build a kernel that can boot without an initramfs.
Offline
You should be able to rebuild the initramfs while chrooted into the installation. If you can't, you have deeper issues.
Offline
OK I got the initramfs rebuilt. (mkinitcpio with no args complains, whereas mkinitcpio -p linux works... and yeah, I always did it that way too, just have to look at the wiki each time to remember) That didn't fix it.
Offline
And then I got it to boot with a custom kernel, without initramfs. Just like the good old days...
Offline