I edited my lilo.conf in this way:

prompt
timeout=50
default=RedHat_7.3
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32

image=/boot/vmlinuz-2.4.18-3
label=RedHat_7.3
initrd=/boot/initrd-2.4.18-3.img
read-only
root=/dev/hda5

image=/boot/vmlinuz-2.4.19
label=LFS
read-only
root=/dev/hda8


Then, I did execute lilo ($lilo -v) and rebooted it,
all worked o.k., but when loged on my LFS system and
ran lilo from it (I took special care to copy the
kernel file and initrd file of my old distro onto my
LFS /boot directory) it seemed to be o.k., but when
the machine was booting a lot of 40s and then a not
ended sequence of Ls appeared on the screen. I used a
boot disk and ran lilo again inside my old distro (by
the way It is RedHat 7.3) to fix my boot record.

Then, I rebooted the machine and loaded LFS, after a
while looking for a diference, I noticed that the size
of the boot.b file into the LFS's /boot directory is 0
(zero). I tried to run it copiying a boot.b file from
my old distro's /boot dir but lilo gives an error
saying that it is a file of and older version (21.4)
and It was expecting 22.2, Also, I tried to do it (run
lilo) using a bootfile named boot-bmp.b but in booting
time the same error occurred.

Ok. It seems to be hapenning because the boot.b file
that comes with the lilo package is damaged. Now, Is
it possible to happen??? How could happen it?? and It
is not, What is wrong then???


Francisco Moreno.

ps.
I think it is obvious that English is not my native
language. My apologise for my errors.

If your boot.b and other such files are zero size, you can recreate them simply by reinstalling LILO. Boot into LFS, and use the chapter 6 instructions for lilo, everything should be ok then.

I did it, and the LILO's Installation rename all my old .b files to .b.old and then put on the /boot directory the new files, BUT the newer boot.b file still given 0 (zero) bytes.

/boot/boot.b is a symlink to something else, probably /boot/boot-menu.b

Does that file exist?

Yes, it does....

So, I'll try erasing boot.b and remaking the sym link.

It didn't work... Could my ln command working wrong??

I'll try setting boot-menu.b directly onto the lilo.conf 's install option.

It didn't work... the same 40s and Ls are appearing....

I'd download from freshmeat.net the most recent version, compiled and installed it again..., but the samething is happening....