On Wednesday 28 March 2001 20:05, S.Toms wrote:
On Wed, 28 Mar 2001, Jerry Kreps wrote:
jk> I have been and I am. But, check the documentation and you'll find jk> nothing about System.map's. So, even though you compile a new jk> kernel and install bzImage and System.map, your new System.map is jk> not being referenced. You have to rename it to what SuSE used: jk> System.map-2.2.18, and this is not a logical way to do things. jk> If I were to recompile using the 2.4 kernel I would get a new jk> System.map and then I would have to name it System.map-2.2.18 in jk> order for it to be used at boot. This doesn't make sense. What jk> should happen is that a setting in lilo would allow me to tell the jk> system which System.map to use. JLK jk>
Take a look at /etc/rc.d/syslog and make the necessary changes there. Can't recall who, possibly Stefan but not positive, mentioned this on a similar discussion back in November of 2000. Your looking for the line that possibly looks like the following:
startproc /usr/sbin/klogd -k "/boot/System.map-$(/bin/uname -r)" \ -c $KERNEL_LOGLEVEL || return=$rc_failed
I say possibly because I'm using 7.0 and it used to look like this startproc /usr/sbin/klogd -c $KERNEL_LOGLEVEL || return=$rc_failed
until I patched it to the above line.
jk> jk>
Thanks S., That looks like a good, although temporary, workable solution. SuSE should either modify syslog so that upgrades won't have to be tinkered with or, modify lilo so that a System.map can be assigned in the specific kernel section. This has been done for initrd, even though the documentation for how an initrd file is created leaves a lot to be desired. Linux, and SuSE, are on the verge of leaping onto the non-technical user desktop space. The distro that ties up these loose ends first will be the one that wins. JLK