Perhaps someone could explain to me the concept of multiple kernels...
I have 2.2.16 and 2.4.0 installed on my system. I am currently running -18tgz version of SuSE's 2.4.0 kernel (the httpd service fails). I have no problem using vmlinuz for 2.2.16 and vmlinuz.240 for the 2.4.0 kernel. My confusion relates to the System.map and the initrd file. A new System.map is generated everytime you recompile a kernel. Yet, I don't know of any way in lilo.conf to tell a kernel to use a specific map. Chris references "initrd=/boot/initrd-x.y.z" in his example of lilo.conf BUT, recompiling the kernel does NOT produce a new initrd file, at least not on my box, so why reference a different initrd file? Also, when you do "make modules" and "make modules_install" you change the modules to reflect the newly compiled kernel, not the old one. When I boot the old kernel it gives me a message bout the modules not being current, or something like that. Ok, Linux gurus.... what's the scoop? JLK -- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
On Thu, Jan 11, 2001 at 12:15:59AM -0600, Jerry Kreps wrote:
I have 2.2.16 and 2.4.0 installed on my system. I am currently running -18tgz version of SuSE's 2.4.0 kernel (the httpd service fails). I have no problem using vmlinuz for 2.2.16 and vmlinuz.240 for the 2.4.0 kernel. My confusion relates to the System.map and the initrd file. A new System.map is generated everytime you recompile a kernel. Yet, I don't know of any way in lilo.conf to tell a kernel to use a specific map. Chris references "initrd=/boot/initrd-x.y.z" in his example of lilo.conf BUT, recompiling the kernel does NOT produce a new initrd file, at least not on my
/sbin/mk_initrd is supposed to create initrd. Sorry, don't have answers to other questions. -Kastus
box, so why reference a different initrd file? Also, when you do "make modules" and "make modules_install" you change the modules to reflect the newly compiled kernel, not the old one. When I boot the old kernel it gives me a message bout the modules not being current, or something like that.
Ok, Linux gurus.... what's the scoop? JLK
Jerry Kreps wrote:
"make modules_install" you change the modules to reflect the newly compiled kernel, not the old one. When I boot the old kernel it gives me a message bout the modules not being current, or something like that.
This is my Makefile located at /usr/src/linux/arch/i386/boot/Makefile Now I am using 2.2.16 and I have 2.4.0-test-12 (well I decided to wait for SuSE to release a bug fixed one) and I do not have in switchinh kernels no complains reagrding modules (BTW IIRC this was a hinht from Phillip Thomas you may want to search the arhieves as there were are proposals) 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-$(KERNELRELEASE); \ 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
Ok, Linux gurus.... what's the scoop? JLK
-- Scientific theories, according to Sir Karl Popper, can be "falsified," or proven wrong, by experiment. Unscientific theories -Marxist dialectical history and Freudian psychology were Popper's favorites- are formed in such a way that they cannot be falsified by data.
-- 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/faq
-- Togan Muftuoglu
participants (3)
-
Jerry Kreps -
kastus＠tsoft.com -
Togan Muftuoglu