Hi everyone, Couple of questions on the topic 1) When running "susewmif kernel en" other than changing the /usr/src/linux symbolic link to the kernel release path ie linux-2.2.14 or linux-2.2.15 is there any other way to choose which kernel release to choose ? Philipp Thomas wrote:
Yep, I'd have to agree here. BTW, if you compile and use different kernel versions you might find this changed rule for 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. But otherwise I find this very handy, specially if you're also using development kernels, e.g. 2.2.X-preY or 2.3.X.
2) I am not quite sure if I got his right? By editing the /etc/lilo.conf do you mean other than putting the following image= /boot/vmlinuz.xxx root= /dev/hdx label= xxx Thnks in advance -- Togan Muftuoglu toganm@turk.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/