Ack. I've just spent a frustrating couple of hours trying to get a new potato install to boot from the hard drive. It has a small /boot partition at hda1, / at hda2. The install process set up lilo.conf to boot /vmlinuz, which is a symlink to the real kernel in /boot. I thought maybe the cross partition link was a problem, so I changed it to boot /boot/vmlinuz and made that a symlink to the real kernel. Still no joy. I guess I could make lilo point directly to the kernel image, but it should be able to follow the symlink, shouldn't it?
About the only thing left is when I partitioned the drive I did not make hda1 bootable. It's my understanding that lilo doesn't care about the bootable flag, but now i'm starting to wonder. I seem to remember going through about this same hassle when I put potato on this box. Installing from cdrom, at the point where you make the system bootable directly from hard disk and then reboot, I have yet to get a potato system to boot without a lot of manual intervention. I have the feeling that I've missed something simple and obvious here. Can someone give me a hint? -- Bud Rogers <[EMAIL PROTECTED]> http://www.sirinet.net/~budr All things in moderation. And not too much moderation either.
