I have created a small problem with my lilo configuration. I have
removed memory from one of my Linux machines to put in my new Linux
server. I traded some SIMM memory chips to get new DIMMs.
Like an idiot, I didn't change my lilo.conf file and remove the
"append=80M" (this box now has 32 MB) until after I traded the RAM.
After removing the RAM, but not changing the lilo.conf file causes the
kernel to hang just after the file system is remounted rw. So, I booted
this machine off floppy and edited the lilo.conf file. The problem is
that now I cannot run the lilo program to read my new lilo.conf file.
I used the slackware install disks to boot a vanilla install kernel. I
then mounted my boot file system (/dev/hda4) on /mnt, while the
slackware disks boot onto /. So, when I run the lilo program: lilo -C
/mnt/etc/lilo.conf (to read my boot lilo config file) lilo complains
that it cannot find my kernel in /. This is correct because the boot
kernel is on /mnt/ while the slackware installation kernel is in /. I
cannot copy the /mnt/vmlinuz kernel to / because the installation file
system on / after floppy boot is too small.
My next thought was to umount the installation file system on / and
mount my boot file system (/dev/hda4) there. It appeared that I did
umount the installation file system on /, but when I tried to mount
/dev/hda4 on /, mount complained that '/dev/hda4 is not found or / is
The bottom line is that I need to run lilo to read my new lilo.conf file
so I can boot the kernel without the "append=80M".
Suggestions are welcome.