Hello..
Seems you have installed a new kernel and not called lilo before
reboot...
I would suggest one of these two ways:
-Boot from your older hdd and mount the new one, e.g. under /mnt/test.
Call lilo, but give him the configfile from your new hdd, it should ly
under /mnt/test/etc/lilo.conf, if you have mounted your new, defective
linux under /mnt/test: "lilo -C /mnt/test/etc/lilo.conf
Before, check that your lilo.conf is correct!
(I have to admit that i' ve never tried this myself)
-Boot from your older hdd and use the distro-tools to produce an
"emergency repair disk", e.g. "mkbootdisk" under RedHat or "yast" under
SuSE. Use this repairdisk to boot the defective linux-installation,
check /etc/lilo.conf and call lilo.
And one hint:
It is always a good idea to have a bootdisk on hand...:-)
Solong..
Frank.
-- Frank Schneider, <SPATZ1@T-ONLINE.DE>. Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ... -.- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/