Grub should have actually been pointing at Fedora's /boot, not the volume group.
If you install Fedora last, it might or might not see some of the other systems--it's good at seeing Windows or other Fedora/RH/CentOS installs, but actually, on various laptops where I"m testing different O/S's , I install it first.
If it doesn't see the other systems, grub has a 0 time out, a poor decision in my opinion. However, as long as it boots properly, that's fine, you can fix it after the first boot. (You'll see timeout=0, change it to 3 or 4.
What I usually do is this. Install Fedora first. Install the next one, and make sure (one usually has to pick advanced options when installing the boot loader) that system2 installs *its* grub in its own partition. (That choice should be offered by most systems.)
Hrrm, not sure what PCBSD does. With FreeBSD, I choose to not install a bootmanager, then, boot it with
(say it's on partition 3)
Then for sam linux, be sure *it* installs grub in its own root partition. You can then boot it with
That's if you're install Fedora first. If you do the others, PCBSD should still work the way I've described it. With Sam Linux, I would, if Sam Linux hasn't done it already, symlink its vmlinuz and initd.img. For example, if in Sam Linux's /boot you have vmlinuz-<longnumber> and initrd-<longnumber>.img I would
ln -s vmlinuz-<longnumber> vmlinuz
ln -s initrd-<longnumber>.img initrd.img
Then in Fedora's GRUB, I *think* this will work
title SAM Linux
(Not positive about that though.)
This is if you put in PCBSD and SAM Linux first, lettting them put their boot loaders where they will.
Do NOT PM forum members with requests for technical support. Ask your questions on the forum.
"I don't know why there is the constant push to break any semblance of compatibility" --anon