rob at pangalactic.org
Mon Nov 8 16:13:00 MST 1999
Lynn Danielson wrote:
> Rob Riggs wrote:
> > "Howell, Jeff S" wrote:
> > >
> > > So how does one fix this?
> > Ah, right. A new System.map is generated in the top-level of the
> > kernel source tree every time a new kernel is made. This should
> > be copied into the /boot directory.
> A work mate told me last week that this was recommended practice.
> I've never done it.
> The klogd man page says that if a symbol file is not explicitly
> specified the following filenames will be tried:
That may well be the case, but klogd is not the only utility
that makes use of System.map.
> So, is the above info no longer accurate or are there other
> dependencies on the System.map file? If I'm reading the the
> above paragraph correctly then there should be no need to copy
> System.map from /usr/src/linux to /boot. Yes/no?
I can't say if it is accurate or not, but it does not matter.
Other programs that rely on System.map data may not behave in
More information about the LUG