Kernel-compile tips or tricks?
Hi, all: Does anyone have tips, tricks, pointers, suggestions or other help for someone about to compile their first (SuSE) kernel? I'm currently running SuSE 7.2 with the stock 2.4.4 kernel. I've read some RedHat docs. I've peered over a colleague's shoulder as he ('way too quickly!) compiled his Slackware kernel. My only other experience compiling a kernel was Slackware 1.3.something (long time ago...). Does SuSE have any How-To's, or do they have kernel-sources on their web-site? Are there SuSE-specific things I have to watch out for? Can I take my SuSE7.2 kernel configuration, and use 'make oldconfig' to produce a (hopefully-workable!) starting point for my own 'make xconfig'? Any and all help is greatly appreciated, -Gord -- Gordon Pritchard, P.Eng., Member IEEE Technical University of B.C. - Research Lab Engineer mailto:gordon.pritchard@techbc.ca direct phone: 604-586-6186
On 14 Feb 2002 15:59:35 -0800
Gordon Pritchard
Hi, all:
Does anyone have tips, tricks, pointers, suggestions or other help for someone about to compile their first (SuSE) kernel? I'm currently running SuSE 7.2 with the stock 2.4.4 kernel.
/usr/src/linux/README walks you thru it step by step. basically make menuconfig make dep make clean make bzImage make modules make modules_install cp /usr/src/linux/arch/i386/boot/bzImage to /boot/vmlinuz(add your uname) edit /etc/lilo.conf to note name changes run lilo reboot Spend alot of time looking at the HELP for each config item, and enable the option "Prompt for incomplete code or drivers". -- $|=1;while(1){print pack("h*",'75861647f302d4560275f6272797f3');sleep(1); for(1..16){for(8,32,8,7){print chr($_);}select(undef,undef,undef,.05);}}
On Thu, 2002-02-14 at 16:36, zentara wrote:
Does anyone have tips, tricks, pointers, suggestions or other help for someone about to compile their first (SuSE) kernel? I'm currently running SuSE 7.2 with the stock 2.4.4 kernel.
/usr/src/linux/README walks you thru it step by step.
Thanks - I'll read that carefully. Someone else suggested I read the README that will accompany the new kernel-source.
Spend alot of time looking at the HELP for each config item, and enable the option "Prompt for incomplete code or drivers".
Again, knowing that there's help available for each item is great! -Gord
On 14 Feb 2002 15:59:35 -0800
Gordon Pritchard
Hi, all:
Does anyone have tips, tricks, pointers, suggestions or other help for someone about to compile their first (SuSE) kernel? I'm currently running SuSE 7.2 with the stock 2.4.4 kernel.
I forgot, copy /usr/src/linux/System.map to /boot There are ways to match up different kernel versions with multiple system.maps. You can get that detail later. ALSO, when you copy your new kernel to /boot, don't overwrite the old one, but make a name for it by editing the /usr/src/linux/Makefile at the top where you enter EXTRAVERSION. Then you will get a separate kernel name and modules directory, named to match. Then edit the /etc/lilo.conf to add this to your boot menu. This way, you can boot your new kernel as vmlinuz-test (for example); so if it hangs on boot, you can fall back onto your old kernel. If you make a bad kernel, don't worry, just do a "make mrproper" and start over. Once you do it a couple of times, it's easy. And finally, before you exit makemenuconfig there is an option to SAVE your config to a file. Save it!!! So when you come back for a second attempt, you will have all your old options saved and ready to load. -- $|=1;while(1){print pack("h*",'75861647f302d4560275f6272797f3');sleep(1); for(1..16){for(8,32,8,7){print chr($_);}select(undef,undef,undef,.05);}}
participants (2)
-
Gordon Pritchard
-
zentara