* Jerry Kreps [Tue, 27 Mar 2001 22:45:52 -0600]:
I've noticed that lilo.conf doesn't contain any mention of the system.map. So, how does one tell the kernel which System.map to use, especially if two different kernels create two different System.maps???
Name the kernels and matching system.map identically, i.e. if your kernel is named vmlinuz-2.2.18, klogd will try to load System.map-2.2.18. To make running different kernels easier, I have a changed rule in arch/i386/boot/Makefile: zlilo: $(CONFIGURE) $(BOOTIMAGE) if [ -f $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) ]; then \ mv $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE)(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE).old; \ fi if [ -f $(INSTALL_PATH)/System.map-$(KERNELRELEASE) ]; then \ mv $(INSTALL_PATH)/System.map-$(KERNELRELEASE) $(INSTALL_PATH)/System.map-$(KERNELRELEASE).old; \ fi cat $(BOOTIMAGE) > $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) cp $(TOPDIR)/System.map $(INSTALL_PATH)/System.map-$(KERNELRELEASE) if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi This way you only need to make a new entry in /etc/lilo.conf before compiling a new kernel and then do 'make bzlilo'. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390