that has to be the problem. somehow, the wrong map is being loaded for your kernel. there's simply no other possibility. use ls to determine the last access time of each kernel and System.map pair. make sure the right pair was loaded last time you rebooted the system. peter On Thu 14 Dec 00, 4:10 PM, Pollywog said... > > On Wed, 13 Dec 2000 23:07:18 -0800, Peter Jay Salzman said: > > > i wrote a very nice piece on the System.map file. you can find it at my > > personal website, along with other bits and pieces of linux knowledge: > > > > http://www.dirac.org/p/linux/systemmap.html > > > > 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. > > > > That does not appear to be the problem, and I have not had a similar > problem before. > > thanks > > -- > Andrew -- ------------------------------------------------------------------ linux To err is human, to forgive is divine. p@belial.ucdavis.edu - To oink is porcine, to meow is feline. http://www.dirac.org/p ._. To neigh is equine to howl is lupine, /v\ To moo is bovine to bleat is ovine. // \\ ------------------------------------------------------------------ ^^ ^^ GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D rules
Attachment:
pgpTjcsPgzJxz.pgp
Description: PGP signature