On Tuesday 11 October 2005 10:18 pm, Mark wrote: > Is there a way I can apply all of the options I set last time I ran make > menuconfig to the new kernel I just downloaded, or do I have to go through > all the settings again?
1. cd /usr/src 2. tar xjf /path/to/downloaded/kernel.tar.bz2 3. cd linux-new-kernel 4. make mrproper 5. cp ../path.to.old.kernel/.config ./.config 6. make oldconfig 7. make && make modules_install && cp .config /boot/config-new-version && cp System.map /boot/System.map-new-version && cp arch/i386/boot/bzImage /boot/vmlinuz-new-version && /bin/rm -f /usr/src/linux && ln -s /usr/src/linux-new-kernel /usr/src/linux && vi /boot/grub/menu.lst A little terse, but yes. make oldconfig pulls in your existing .config file. It will prompt for new offerings not part of your old .config, usually the suggested default at the prompt is the way to go. When managing your own kernel, don't forget to a) install the modules (plus any other third party modules (i.e. nvidia driver modules) or your new kernel will give you grief, and b) recreate your /usr/src/linux symlink to point at the new kernel. Those steps above are the ones that I typically take (yes, folks will say to use "make install", but I'm still from the old school. The only part of the rote script above that I'm unsure about is the System.map stuff. I know it gets generated when the kernel is built, I know most systems have them in /boot, but for the life of me I never a) found out what it was for, b) found out if it had to be in /boot and if it had to be a special name (i.e. /boot/System.map explicitly), and c) why I even bother in the first place. Dave -- gentoo-user@gentoo.org mailing list
