Andrew,
> I recently tried to compile a new kernel on my RedHat7 system and all went
> okay except LILO hangs at LIL-.
....
If you can boot from a floppy (and I assume you mean your new kernel)
then
all is well with your file systems, you just need to re-install your MBR
by first checking lilo.conf is ok and then doing a
# lilo
I've been trying to find out what is actually in a lilo master boot
record.
So far I know that bytes 0-445 are the boot code, 446-509 is the
partition
table and 510-511 are the bootable flag. It seems that the boot code
points
to the sector of the disk where the kernel or bootmap or something is
living,
cause if you use a tool like cpio to copy your entire system to another
disk
and then use dd to copy the mbr over, it won't boot the new disk (you
get a
LIL- prompt), but if you use dd to copy the entire disk then it will
boot.
The same windoze mbr seems to be able to boot any doze install but
lilo's
mbr seems to be specific to that installation and file system.
If anyone knows more about the actual boot code or has pointers to info
about --> much appreciated.
HTH
Pete
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
