On Fri, Jan 28, 2000 at 04:16:07AM +0200, Shaul Karl wrote: > > [04:09:47 shaul]$ uname -a > Linux rakefet 2.2.13 #1 Sat Nov 20 12:44:19 EST 1999 i586 unknown > [04:10:11 shaul]$ ls -l /vmlinuz > lrwxrwxrwx 1 root root 20 Jan 28 03:53 /vmlinuz -> > /boot/vmlinuz-2.2.14 > [04:10:20 shaul]$ > > Is that a bug or done intentionally by the kernel-image-2.2.14 package > or does it because I did not run lilo before rebooting?
Yes, unless you don't use lilo at all on your system. Even if the symlink or the lilo.conf file changes, the boot sector on your disk will still be using the old setup until you rerun lilo to impliment the new configuration. At the point in the boot process where the kernel is loaded, nothing is available which knows how to check the symlink. lilo writes the physical location of the kernel on your disk into the boot loader. -- finger for GPG public key. 8 Jan 2000 - Old email addresses removed from key, new added
pgpgEMXc8Awax.pgp
Description: PGP signature
