On Wed, Dec 13, 2000 at 11:28:23PM -0900, Ethan Benson wrote:
> On Wed, Dec 13, 2000 at 11:07:18PM -0800, Peter Jay Salzman wrote:
> > what's most likely happening is that the System.map file that klogd is
> > finding is in /boot/System.map, since that's the first location klogd will
> > look by default.
Actually there is only one System.map and one kernel on the system (both from
the same compile run) so I'm quite certain that the right file is present.
Here is what ps's complaint looks like:
hajhouse@nitro-9:~$ ps
{__cpu_logical_map} {__cpu_logical_map_R__ver___cpu_logical_map}
Warning: /boot/System.map-2.2.17 does not match kernel data.
{__cpu_logical_map} {__cpu_logical_map_R__ver___cpu_logical_map}
Warning: /usr/src/linux/System.map does not match kernel data.
PID TTY TIME CMD
[... further ps output]
> unecessary, this has not been required ever since 2.2 kernels came
> out, and possibly even before that. everything that uses System.map
> looks for System.map-`uname -r` you don't need that symlink. redhat
> still does this for incomprehensible reasons. all it accomplishes is
> allowing you to only boot one version of the kernel with a matching System.map.
I did not know this, thanks!
--
Henry House
OpenPGP key available from http://hajhouse.org/hajhouse.asc
Attachment:
pgpJjaVX7Grx1.pgp
Description: PGP signature