[lug] System.map issue
Chris Riddoch
socket at peakpeak.com
Fri Feb 22 15:23:44 MST 2002
"D. Stimits" <stimits at idcomm.com> writes:
> The web page isn't displayable. You may also wish to rename it on the
> web page System.map.txt. The display is:
> [an internal server error occured]
Okay, I should've checked that before just assuming the server
wouldn't treat .map files like that...
Try this, then:
http://www.peakpeak.com/~socket/System.map-corrupted.txt
http://www.peakpeak.com/~socket/System.map-original.txt
> Is your file in /usr/src/linux/System.map (I assume this is the same
> place in Debian as in RH and Slackware and many others) also corrupted?
No, it's not. I've posted that to the website so you can be sure of
it.
> Also, it is a *very* good idea to not copy it as System.map
I didn't, originally. I apparently use the same naming convention as
you for System.map, and I changed lilo.conf appropriately. I tried it
both ways, and both ways, it gets corrupted.
> ...I think only root needs to read this file during boot, but
> possibly others will later. And if some strange daemon runs as
> another user at some point during boot, perhaps a non-root user
> needs to read it earlier on. Perhaps it is silly, but be sure it is
> world readable.
Yes, I noticed the permissions changed, too. This is the original:
socket at laptop:~$ ls -l /usr/src/linux/System.map
-rw-r--r-- 1 root root 428641 Feb 21 13:15 /usr/src/linux/System.map
And this is what it gets changed to, in it's corrupted form.
socket at laptop:~$ ls -l /boot/System.map
-rw------- 1 root root 26624 Feb 22 12:53 /boot/System.map
> And if the file is different between the compile directory root and
> the /boot/ version, then replace it again with the compile directory
> version.
Every time I shutdown and start up again, it's corrupted. Every time I
notice it's corrupted, I replace it with the original. I'd like to
not have to keep copying my System.map file every time I boot my
machine.
I even tried removing write permissions from System.map. It *still*
got changed.
*Something* is breaking this, and it's clearly not a problem with the
original file.
--
Chris Riddoch | epistemological
socket at peakpeak.com | humility
More information about the LUG
mailing list