On Sat, 06 Jul 2002 16:50, Damian G wrote: <snip> > ok, so in order to use my new kernel i've got > to rename my new System.map to something like > System.map2.4.28mine and change that link to make > it point to my file. > > now, my question is: > > how am i supposed to keep both kernels? > i've checked lilo.conf and the boot sections seem > to have no reference to these files... > > what do i have to add in order to make lilo choose > the corresponding system.map whenever i choose a kernel > to boot?
Took a quick look at the link that Charles provided (http://www.linuxmafia.com/~rick/linux-info/systemmap.html) which explains the answers to your questions. This is how I interpreted it: 1) System.map is a file containing the kernel symbol info. 2) System.map has versioning info (eg. System.map-2.4.18-16mdk or System.map-2.4.18-20mdk). 3) If a kernel oops occurs it is intercepted by klogd (a kernel logging daemon) which performs name-address resolution. 4) klogd uses the System.map file to perform the address resolution and looks for this file in 3 places in the following order: (i) /boot/System.map (ii) /System.map (iii) /usr/src/linux/System.map So if you have two System.map files: /boot/System.map-2.4.18mdk /boot/System.map-2.4.18mine and you boot with your new kernel image /boot/vmlinuz-2.4.28mine then klogd will first look in the /boot dir for the matching System.map file (ie. System.map-2.4.18mine). Still, I usually remove the old link in /boot and create a new one pointing to the new System.map-[new one] before I boot my new kernel. Same with the vmlinuz link - I delete the old and create a new link. Its also safer to put the actual kernel image filename in /etc/lilo.conf rather than link, eg. image=/boot/vmlinuz-2.4.18mine and NOT: image=/boot/vmlinuz Sharrea -- oxymoron: Microsoft Works
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
