Ben Reser wrote on Wed, Oct 30, 2002 at 11:20:23PM -0800 : > On Wed, Oct 30, 2002 at 07:40:16AM -0800, David Walser wrote: > > Installing it it did change the symlinks for > > initrd.img and vmlinuz in /boot, but if failed to > > change the symlinks for config and System.map > It never changes those symlinks. They're always set correctly on > bootup. At least that's been my experience.
Me neither.
To the original poster, the problem comes up when the lilo.conf is using
/boot/vmlinuz instead of /boot/vmlinuz-2.4.19-16mdk (for example). It's
expecting System.map and initrd.img to be valid symlinks as well. If
initrd.img symlink is messed up, lilo won't be able to load the correct
one which will result in modules not matching the kernel version which
will probably result in an unbootable system. If System.map symlink is
messed up, then it will result in a warning message about not matching
the kernel version but will still boot up.
Blue skies... Todd
--
MandrakeSoft USA http://www.mandrakesoft.com
Never take no as an answer from someone who's not authorized to say yes.
--Ben Reser on Cooker ML
Cooker Version mandrake-release-9.1-0.1mdk Kernel 2.4.19-16mdk
msg80392/pgp00000.pgp
Description: PGP signature
