I just used YAST to update my kernel from 3.6.8 to 3.7.1, and after the process was over, I checked /boot and noted that the System.map link was pointing to the (deleted) previous system.map file.
This is from an openSUSE 12.2 system (you forgot to identfy your version):
boven:/boot # l
total 30208
drwxr-xr-x 4 root root 4096 Dec 22 12:51 ./
drwxr-xr-x 24 root root 4096 Jan 11 17:23 ../
-rw-r--r-- 1 root root 2487319 Oct 5 00:30 System.map-3.4.11-2.16-desktop
-rw------- 1 root root 512 Dec 11 12:15 backup_mbr
lrwxrwxrwx 1 root root 1 Dec 11 12:04 boot -> ./
-rw-r--r-- 1 root root 1236 Jul 15 15:34 boot.readme
-rw-r--r-- 1 root root 131351 Oct 4 22:56 config-3.4.11-2.16-desktop
drwxr-xr-x 2 root root 4096 Dec 11 12:04 grub/
drwxr-xr-x 6 root root 4096 Dec 22 12:51 grub2/
lrwxrwxrwx 1 root root 26 Dec 22 12:51 initrd -> initrd-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 16827154 Dec 22 12:51 initrd-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 581632 Dec 11 12:48 message
-rw-r--r-- 1 root root 222379 Oct 5 00:51 symvers-3.4.11-2.16-desktop.gz
-rw-r--r-- 1 root root 520 Oct 5 00:51 sysctl.conf-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 5719500 Oct 5 00:50 vmlinux-3.4.11-2.16-desktop.gz
lrwxrwxrwx 1 root root 27 Dec 11 12:51 vmlinuz -> vmlinuz-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 4919280 Oct 5 00:30 vmlinuz-3.4.11-2.16-desktop
boven:/boot #
As you see there isn’t even such a symlink. Thus I wonder how you got it al all. And when you got it by another action then earlier installation, I do not wonder that it is not updated.
PS. Using CODE tags (the # button in the toolbar) is easier and gives better results then changing fonts only.
Yes, thanks for your answer – but notice you do not have ANY system.map files at all – maybe it’s because you haven’t installed some package I did install? Checking with YAST, I find that “kernel-desktop” (I got 3.7.1-17.1 installed) does include it.
I strongly suggested you to reveal what level of openSUSE you have. No answer.
You talk about “ANY system.map files”. I thought we talked about a file name System.map (and only one of it, that is in /boot) that is a symbolic link to to the current System.map-<kernel-id> of the active kernel (or that is what you guess).
Then after introducing “files”, you say that YaST shows “it” is included.
Now do you mean that YaST shows that in the RPM for the kernel you have there is a file* /boot/System.map* additional to /boot/System.map-3.7.1-17-desktop?
I do not have a /boot/System.map in my YaST list.
On 01/11/2013 02:36 PM, fkereki wrote:
>
> I recreated the symlink by hand, just in case – I didn’t dare reboot
> the machine with that problem.
well, see you should left it alone and just rebooted…because after
you install a new kernel but before you reboot you are still using the
OLD kernel…
and the reason YaST tells you to boot as soon as possible (after a
installing a new kernel) is because there is a script which will be run
on the next power up which puts the stuff where it should be…
BUT, i have NO idea what that script will do when it sees the simlink
you recreated, just after the kernel install routine set it up the way
YaST (the devs) wanted…
> My questions:
>
> - is the System.map symlink needed?
> - if so, why isn’t it updated by YAST?
it would have been all swell after the directed “as soon as possible”
reboot.
> - if not, can I simply delete it?
i don’t know, and by the way i may not know what i’m talking about
here…so, listen to the others…but, i can tell you i’ve done a lot
of kernel upgrades with YaST and never felt the need to creatively
mess around in /boot until after the entire replace-the-kernel-process
was complete (which requires a reboot)…
Then you should have started the thread in the Tumbleweed forums. Your fellow Tumbleweed users are probably much better equiped to help you then those who do not use Tumbleweed (like me).
Please look agin at my listing in post #2. The fifth line from the top of the Code part shows:
-rw-r--r-- 1 root root 2487319 Oct 5 00:30 System.map-3.4.11-2.16-desktop
That was 10 days ago. What did you do during those 10 days? Apparently not concentrating on your problem and the fact that people try to help you. I would normaly already have disconnected from this thread a few days ago, thinking that you were not interested anymore and simply decided to walk away leaving people here staring at a black hole.