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

[Philip Hands <phil@hands.com>]

> If Debian installed kernels as
> 
> /boot/linux-2.0.30
> /boot/system.map-2.0.30
> /boot/linux-2.1.47
> /boot/system.map-2.1.47
> 
> etc. and then behaved correctly by symlinking /system.map and /vmlinux
> on boot with something like:
> 
>    ln -s /boot/linux-`uname -r` /vmlinuz
> 
> and
> 
>    ln -s /boot/system.map-`uname -r` /system.map

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

Cheers, Phil.


--
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 .