Kernel/lilo/initrd upgrade issue

[Greg Madden <gomadtroll@gci.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Something I noticed installing a kernel I compiled without using the initrd 
stuff. I have been using the kernels provided by Debians archives. They do 
the prompt to add 'initrd=/initrd.img' to  lilo.conf. The prompt suggests 
adding to the actual stanza for the kernel. i.e image=/vmlinuz. When I 
install my own kernel, run lilo, the messages suggest everything is  okay, 
i.e. 'added Linux, Linux.old. This doesn't work because the 
'initrd=/initrd.img' is in the 'image=/vmlinuz' stanza which now has my 
kernel without the initrd stuff. The Debian kernel with initrd is now in 
the 'image=vmlinuz.old' stanza  It seems that running lilo used to catch 
this type of mis-configuration though it has been awhile since I used my 
own kernels I could have forgotten something.

This sequence leaves both kernels unable to boot the box, kernel panic error 
message. A question from all this: can I add  'initrd=initrd.img' as an 
option in lilo.conf but not in the stanza'a mentioned above ?
- -- 
Greg Madden
Debian GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/DZbrk7rtxKWZzGsRAmzaAJ9yF+vuIHwRCyIqkWMcNBexSJcZnACgsOAB
cb19/ikKnAYndadQbM7wnl4=
=ZVC0
-----END PGP SIGNATURE-----