lilo is quite resilient in that, if the partitions and kernel images you reference in /etc/lilo.conf aren't there, the lilo command will throw an error and not install. And I'm assuming you did run lilo after editing? (just editing the config file isn't enough).

lilo can also chainload to the other OS' bootloaders (grub can do this as well). So you could have just installed the standard bootloader for the Linux distribution on each HDD, picked the one you want to boot by default and then just have which ever one chainload the others' bootloaders...

Of course, if it's a new fangled UEFI system, not a "legacy" x86 BIOS, it's a different matter.

1 members found this post helpful.

Oh, I wasn't aware that the kernel images had to be included.

I'll look for an example online.

Thanks