[lug] System.map issue

John Karns jkarns at csd.net
Tue Mar 12 19:14:55 MST 2002

Behind with my mail as usual.  Just wanted to acknowledge that you (Dan)
were apparently right about the system writing to the map file at boot
time.  The problem turned out to be that it wasn't able to due to the fact
that I had added a command to unmount my boot partition in my system init
scripts to avoid possible corruption in cash of abnormal system halt.

SuSE has a /etc/rc.d/boot.local script supposedly for such user purposes,
but it gets called very early in the boot process.  So I created an
additional script, /etc/rc.d/boot.local.final and symlinked it in the run
level dir such that it will get called as one of the very last scripts.


On Fri, 1 Mar 2002, D. Stimits said:

> John Karns wrote:

> > This relates to a long standing issue I've had as well.  From the very top
> > of my boot.msg system log:
> >
> > Cannot find map file.
> > Loaded 63 symbols from 3 modules.
> >
> > I checked and there was no "map=" line in my lilo.conf, which is from a
> > SuSE 7.1 install.  But the man page for lilo.conf says:
> >
> >        map=<map-file>
> >               Specifies the location of the map file. If `map' is
> >               omitted, the file /boot/map is used.
> >
> > Furthermore, although /boot/map exists, lilo was ignoring it.

> I'm no expert on the map file, but I think it has to be written to at
> boot time (maybe not), depending on which kernel is booted. Is your

John Karns                                        jkarns at csd.net

More information about the LUG mailing list