Marc Chamberlin wrote:
So now I am stumped, I cannot figure out what/how I need to change in the boot loader/GRUB/system loader stuff to get it to cope with a new location for /usr...
The only suse supported way to have a separate user is to boot from a ram-disk first, which mounts /usr, and then boots the real kernel. It's not really about grub, but about the fact that many of the utils needed to bring the system up to running order were removed from root and placed in /usr/bin and /usr/lib64, with broken symlinks left in /bin pointing to /usr/bin (which of course may not be mounted yet, as you have discovered). Even if you put the programs on root that you need to boot with, you'll find many of the system-startup libraries were also moved out of /lib64 into /usr/lib64 -- like libmount (hope you didn't need to mount any disks onto your root!)... So what I'm wondering is, was your boot setup by a suse installer? If so, aren't you booting first from some init-ramdisk? That should be ensuring your /usr/ is mounted before allowing the boot to continue (or does systemd do that these days?). I really don't know, as I also have a separate usr, boot from my hard disk, and don't use systemd. You might try making a new initrd -- maybe that would pick up the fact that you have a separate usr and do the mounting? Someone more w/more expertise in creating/booting from initrd might be able to chime in here. I feel your annoyance, BTW, as I also have a separate /usr (and /usr/share), and have had to go through hoops to keep that *AND* boot from my hard disk. I have a program that monitors the binaries and libraries on my root and /usr to keep root bootable. It's not exactly 'simple'...though I try to simplified my setup as much as possible. So .. maybe (guessing) remake initrd? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org