I need to get LILO to boot a ramdisk in which the root file system is on /dev/ramdisk. I have tried many iterations of lilo.conf files. The following is one that I would think would work because it worked under 2.4 kernels:
default=linux
boot=/dev/hda
install=/mnt/flash/boot/boot.b
map=/mnt/flash/boot/map
lba32
verbose 3

image=/mnt/flash/boot/vmlinuz-2.6.25.14
label=linux
initrd=/mnt/flash/boot/bos.img
read-write
root=/dev/ram0
append = "ramdisk=262144"

The boot starts out good saying:
Loading Linux .............................


And that is where it stops. It seems as though it either runs out of ramdisk space or it can't find the kernel? The OS in the ramdisk is CentOS 5 and grub with the same ramdisk and setup works fine. Unfortunately I am required to use lilo.

This works, why doesn't lilo work where the following grub configuration does?
#boot=/dev/hda
default=0
timeout=10
hiddenmenu
title DOOW (2.6.25.14-3)
root (hd0,0)
kernel /boot/vmlinuz-2.6.25.14 rw root=/dev/ram0 ramdisk_size=262144
initrd /boot/bos.img

Solved:
The problem was that old installations were running an old version of LILO and 2.4 kernels. When I copied the new ramdisk over and the new 2.6 kernel over to running systems, I was running lilo meant for the old days. The new version of LILO works fine, however I have some chicken and egg stuff going on with this tricky update.