On Thursday 29 March 2001 00:34, Togan Muftuoglu wrote:
Other alternative could be as suggested by Phillip Thomas almost a year ago
".....edit zlilo in linux/arch/i386/boot/Makefile helpfull:"
zlilo: $(CONFIGURE) $(BOOTIMAGE) if [ -f $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) ]; then \ mv $(INSTALL_PATH)/vmlinuz-$(KERNELRELEASE) $(INSTALL_PATH)/vmlinuz.old; \ fi if [ -f $(INSTALL_PATH)/System.map-$(KERNELRELEASE) ]; then \ mv $(INSTALL_PATH)/System.map-$(KERNELRELEASE) $(INSTALL_PATH)/System.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
As you can see, calling 'make zlilo' (or 'make bzlilo') will result in a kernel and symbol map that both have the version as part of the name. The only thing you have to do manually is to add a new section to /etc/lilo.conf for every kernel you want to be able to boot.
I know that you will correct me if I am wrong, BUT, doesn't this method require that lilo.conf be edited before zlilo or bzlilo is run? Doesn't either of these cause the boot loader to be saved to disk? JLK