Re: boot-time kernel selection and /System.map mismatch

[Bill Mitchell <mitchell@mozcom.com>]

On Wed, 30 Jul 1997, Philip Hands wrote:

> Am I living in a parallel universe, or something ?
> 
> You're requested behavior is exactly what debian kernel packages give me now:
> 
> [phil] palm:~$ ls -l /vmlinuz* /System.*
> lrwxrwxrwx 1 root root   22 May  1 11:06 /System.map -> boot/System.map-2.0.30
> lrwxrwxrwx 1 root root   22 Apr 26 20:18 /System.old -> boot/System.map-2.0.28
> lrwxrwxrwx 1 root root   19 May  1 11:06 /vmlinuz -> boot/vmlinuz-2.0.30
> lrwxrwxrwx 1 root root   19 Apr 26 20:18 /vmlinuz.old -> boot/vmlinuz-2.0.28

Suppose, though, you have lilo.config'd alternatives for both of these
kernel images, and your next boot is with the vmlinuz-2.0.28 image.
What do you have then?  Do the /vmlinuz and /System.map symlinks match
what you're actually running?



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .