RE: [SLE] Compiling several kernels on the same computer
Nah, I've sorted it. Edited the script compilekernel to point to the place where I extract my kernel source to. Just never used susewmif before and I was curious! I've got this habit of posting a problem to here and then sorting it myself! BTW - I can compile kernels a lot easier than susewmif by typing in the full make commands (dep,clean,modules, etc, etc). At least I know what I'm compiling and how, etc! FYI: SuSE 6.3 with Kernel 2.2.14 Kev -----Original Message----- From: Mark Hounschell [mailto:dmarkh@cfl.rr.com] Sent: 05 April 2000 08:16 To: Kevin Jackson; suse-linux-e@suse.com Subject: RE: [SLE] Compiling several kernels on the same computer On Wed, 05 Apr 2000, Kevin Jackson wrote:
I keep getting an error when running:
susewmif kernel en
It brings up a red window saying: no rule to make xconfig.
Now I'm assuming its changing to a directory and runs the make xconfig command, but the Makefile in that directory doesn't have it as an option.
Kev
It sounds like your kernel sources aren't correctly installed. Can you (as root) cd /usr/src/linux then make xconfig. What revision of suse are you running? Mark -- Mark Hounschell dmarkh@cfl.rr.com -- 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/ -- 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/
* Kevin Jackson (kevin.jackson@jhallpr.demon.co.uk) [20000405 16:06]:
BTW - I can compile kernels a lot easier than susewmif by typing in the full make commands (dep,clean,modules, etc, etc). At least I know what I'm compiling and how, etc!
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. Philipp -- Philipp Thomas <pthomas@suse.de> SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany #define NINODE 50 /* number of in core inodes */ #define NPROC 30 /* max number of processes */ -- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h -- 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/
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/
* Togan Muftuoglu (toganm@turk.net) [20000519 10:56]:
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
Yep, that's what I meant. If you use that make rule it would look something like: image = /boot/vmlinuz-2.3.99-pre8 label = linux image = /boot/vmlinuz-2.3.99-pre5 label = lxpre5 Philipp -- Philipp Thomas <pthomas@suse.de> Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany #define NINODE 50 /* number of in core inodes */ #define NPROC 30 /* max number of processes */ -- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h -- 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/
participants (3)
-
kevin.jackson＠jhallpr.demon.co.uk -
pthomas＠suse.de -
toganm＠turk.net