Lilo is the only bootloader working on non-ia32 emulation enabled kernels. Then the installation handbook should recommend lilo for the people who planed *not* to enable ia32 emulation in their kernel and grub/grub-static for the others.
amd64, please advise.
No need; we talked with the team awhile ago, and that's why they told us to add the following bits to hb-install-x86+amd64-bootloader.xml: "If you are using a non-multilib profile, you should *not* emerge grub, but instead you should emerge *grub-static*" Also, we warn the users *more than once in that document*: "Using LILO on the AMD64 architecture is not recommended." ...with a big ol' red WARNING box. The instructions are already all there.
After a chat with Josh, we'll wait for our amd64 folks here.
we arent talking about just non-multilib, we're talking about non-multilib and no 32bit support in the kernel ... so grub-static still wouldnt work
I see no good reason to disable IA-32 emulation in the kernel.. Is the lilo userspace thing even compiled in 64bit ?
i dont know anything about lilo to comment on it, but i wouldnt be surprised if it had native binaries that do the bootloader install that can be 64bit, but the actual bootloader itself that gets installed remains 32bit. assuming that is actually how lilo works, that would make it usable when 32bit support has been disabled in the kernel. i would check these things, but lilo doesnt even build for me on my multilib amd64 system ...
(In reply to comment #6) > i would check these things, but lilo doesnt even build for me on my multilib > amd64 system ... > I guess my input on this bug is neutral. I *only* use lilo on my amd64 multilib systems and have never been told why we recommend against it. *shrugs*
As far as I'm concerned, I have a 64 bits box without ia32 emulation, neither is multilib, lilo did install witout any trouble and has been running fine for a few days. I have a trickier box where I'm about to test lilo:64 bits, no ia32 emulation, no multilib, kernel/initramfs on RAID1 block device. I'll report the result as soon as I tried to reboot it with lilo.
Worked like a charm on my second box.
So, we have confirmed that lilo works in every possible configuration. Wonder why it was even warned against in the first place. /me shrugs
No idea who originated the warning. It does indeed work happily in configurations where Grub won't. The warning is not endorsed by the LILO maintainer and I would certainly be happy to see it go. It is misleading at best.
Fixed in CVS.
