System.map error after Kernel update

[Stephen J. Turnbull <nospam [at] sk.tsukuba.ac.jp>]

>>>>> Barrie == Barrie Bremner <TheEnglishman [at] ecosse.net> writes:

Barrie> I`ve upgraded (not patched) from 2.2.12-20 to 2.2.14.

Barrie> The system boots and runs OK, except for the fact that
Barrie> I`m getting various messages (during boot and strangely
Barrie> when I run top) telling me that /boot/System.map has the
Barrie> incorrect kernel version...

System.map tells everybody but the kernel where kernel variables are.
I'm not sure why top needs this info, there should be sysctl or ioctl
interfaces for everything top gets. In general you are only
interested if you are debugging the kernel. Ie, you can ignore it.

Try ls -l /boot/System.map*. That file is probably a symbolic link to
one with a version number attached. Your new kernel should have
installed one in the /boot directory (or somewhere else, check out the
symlink's target). If not, use rpm to list the .rpm file and find out
where it put the .map file (if there's one in the .rpm at all).
(Sorry, I dunno the switch, I'm a Debian person.)

--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
/- /System.old /apps /bin /boot /dev /etc /home /lib /lost+found /misc /mnt /net /proc /root /sbin /share /tmp /usr /var What's the big deal about the millennium? .............................
.... There are still 360 shopping days left until the millennial epoch! */

Start your own FREE mailing list at

&copy; 2000 Microsoft Corporation. All Rights Reserved