This is strange. I just did an installation of a new system with separate /, /usr and /var partitions.
Using systemd 215-5+b1 and initramfs-tools works without any hassle. ii libsystemd0:amd64 215-5+b1 amd64 systemd utility library ii systemd 215-5+b1 amd64 system and service manager ii systemd-sysv 215-5+b1 amd64 system and service manager - SysV links ii libsystemd0:amd64 215-5+b1 amd64 systemd utility library ii systemd 215-5+b1 amd64 system and service manager ii systemd-sysv 215-5+b1 amd64 system and service manager - SysV links Using dracut instead of initramfs-tools does not boot :-( It's not dracut that complains, but systemd. localhost systemctl[214]: Failed to switch root. Specified switch root path /sysroot does not seem to be an OS tree. os-release file is missing. This what the initrd created by dracut contains: paeffgen:~# lsinitrd /boot/initrd.img-3.2.0-4-amd64 |grep release -rw-r--r-- 1 root root 193 Oct 27 14:46 etc/initrd-release lrwxrwxrwx 1 root root 14 Oct 27 14:46 etc/os-release -> initrd-release Whereas the initrd created by initramfs-tools does not contain any os-release file or symlink. So, which package is to blame for not booting? dracut or systemd? -- regards Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
