Hi, Not interested in a debate over systemd. But I have a boot issue and since there isn't a bug that matches the symptoms, I suspect my setup may be peculiar and I'm hoping someone may have some insight.
The package systemd-sysv installs a symlink ./sbin/init -> /lib/systemd/systemd. The system fails to boot, complaining that "/sbin/init" can't be found. In bug #750360, I found a workaround that I have been using for several months: change the link from absolute to relative ../lib/systemd/systemd. Then the system boots fine and runs fine. Now #750360 describes a situation with nfs mounts but I don't use any nfs mounts. I don't do anything exotic at all! I have just two partitions: / and /backup. Both are straightforward ext4 filesystems, so no nfs, no encrypted fs, nothing. This leads me to believe that my problem is distinct from that issue. Indeed, I tried yesterday with the latest initramfs-tools where #750360 is fixed and I still have the same problem. Is anyone else in the same boat (absolute symlink fails even though / is not nfs)? The fact that my plain vanilla system is having a problem but no-one else appears to be having this problem puzzles me. One thing that may be different is that the OS install was initially done maybe 5 years ago and I just follow "sid" by updating once every week or two. It's possible that a weird configuration crept in over the years: it's happened to me before (#726472). My system has initramfs-tools installed and I can't seem to remove them, so I guess everyone else uses initramfs? Why would I be the only one having this problem? Thanks for any pointers or advice, -Steve -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/2542519.4t9z0E1R1X@riemann
