On 9/21/14, Steve M. Robbins <st...@sumost.ca> wrote: > 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?
This may or may not help but I had an oddball problem with symlinking vmlinuz and initrd's in this *mess* I've got going here.. They weren't visually looking right. A quick right click peek at properties showed system was treating them as broken links when they theoretically were correct.. SOMETIMES I was able to see a difference by eliminating the first slash.. Instead of /lib/systemd/systemd, for example, I had to change *just those* boot symlinks to be along the lines of lib/systemd/systemd. I can't honestly tell you now what booted and didn't when I started playing with that.. I do know that my system began reporting them as properly functioning after that change was made. It SEEMS LIKE mine became apparent after I did my first debootstrap.. There were a couple or few things that happened after the debootstrap that I'm hoping to keep following up on. Am guessing there's a possibility mine was somehow related to a necessary debootstrap step that I missed by being so new at it.. In the meantime, it continues to FEEL LIKE two different operating systems keep taking potshots at each other under the hood here with things similar to what you're experiencing being what's occurring as a result.... Cindy -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * I comment, therefore I am (procrastinating fixing a 2^64 - 1 GRUB flub) * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAO1P-kDLeXOZ9UsucTakxiKWu5otA_L0SbcyL5VeV7khzXb=h...@mail.gmail.com
