RE: [SLE] Compiling a new kernel
I always fully compile my kernel with the following commands: make dep;make clean;make modules;make install;make modules_install;make bzImage Never had any problems. Plus if I'm feeling really swish and like to try some beta kernels then I run make zlilo instead of make bzImage when I've updated the appropriate Makefile with the patch that Lenz sent. This appends the version number to the System.map and kernel keeping them co-existing with one another. And before you ask, I don't have the "patch" available here in work. Lenz is the man to ask for that if you are in desperate need. Make sure you copy arch/i386/boot/vmlinuz /boot and /linux/System.map to /boot. Kev -- 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/
You might want to make those ;s into &&s: make dep && make clean && make modules ... If any one of the commands fails the others won't get executed. (What happens to your existing setup, for example, if "make modules" fails and you do a "make modules_install"?)
I always fully compile my kernel with the following commands:
make dep;make clean;make modules;make install;make modules_install;make bzImage
-- 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/
On Thu, Apr 27, 2000 at 08:44:35AM +0100, Kevin Jackson wrote:
I always fully compile my kernel with the following commands:
make dep;make clean;make modules;make install;make modules_install;make bzImage
Never had any problems. Plus if I'm feeling really swish and like to try some beta kernels then I run make zlilo instead of make bzImage when I've updated the appropriate Makefile with the patch that Lenz sent. This appends the version number to the System.map and kernel keeping them co-existing with one another. And before you ask, I don't have the "patch" available here in work. Lenz is the man to ask for that if you are in desperate need. Make sure you copy arch/i386/boot/vmlinuz /boot and /linux/System.map to /boot.
Heck. You should try it the easy way then... make dep clean bzlilo modules modules_install 2>errors "2>errors" so you can look at any compile time errors after the fact and post if necessary `*8> -- Brad Shelton On Line Exchange http://online-isp.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/
On Thu, 27 Apr 2000, Kevin Jackson wrote: kj> I always fully compile my kernel with the following commands: kj> kj> make dep;make clean;make modules;make install;make modules_install;make kj> bzImage kj> kj> Never had any problems. Plus if I'm feeling really swish and like to try kj> some beta kernels then I run make zlilo instead of make bzImage when I've kj> updated the appropriate Makefile with the patch that Lenz sent. This kj> appends the version number to the System.map and kernel keeping them kj> co-existing with one another. kj> And before you ask, I don't have the "patch" available here in work. kj> Lenz is the man to ask for that if you are in desperate need. kj> Make sure you copy arch/i386/boot/vmlinuz /boot and /linux/System.map to kj> /boot. kj> I'd be interested in seeing that script/patch as I wrote my own long detailed one a while back in bash that does (sounds like anyway) virtually the same thing by entering: make-kernel [imagetype [bootdir [sourcedir]]] if no parameters are chosen, then it will default to making a bzImage installing it into /boot and building it from the /usr/src/linux source. It also alerts you to update lilo if it's a new kernel, or reinstalls lilo if its a current kernel. kj> Kev kj> kj> -- S.Toms - tomas@primenet.com - www.primenet.com/~tomas SuSE Linux v6.3+ - Kernel 2.2.14 -- 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 (4)
-
dns＠online-isp.com -
fountai＠hursley.ibm.com -
kevin.jackson＠jhallpr.demon.co.uk -
tomas＠primenet.com