On 3/28/06, <b class="gmail_sendername">Josh Trutwin</b> <<a href="mailto:josh@trutwins.homeip.net">josh@trutwins.homeip.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I just did this tonight finally on a remote production Debian box -<br>went fairly well. You can usually do the following:<br><br>1.) download newest kernel source tree - untar and go into the source<br>directory.<br>2.) cp /boot/config-
2.4.xx .config (where xx is your current version)<br>3.) make oldconfig - answer when prompted about new/changed<br>configuration items - most answers will be 'N'<br>4.) make<br>5.) su<br>6.) make modules_install<br>7.) cp .config /boot/config-
2.6.xx<br>8.) cp System.map /boot/System.map-2.6.xx<br>9.) cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.xx<br>10.) Edit lilo or grub config files to load new kernel boot record<br>into MBR.<br>11.) reboot<br><br>At least that's what works for me - I'm not saying it's that simple.
<br>With a major release upgrade you'll want to carefully compare the<br>config files between the working 2.4 version and the one you get after<br>make oldconfig (or make menuconfig/xconfig if you prefer) - for<br>example, I had to manually redo all my Netfilter (iptables) options in
<br>my 2.6 config file because "make oldconfig" didn't enable a lot of the<br>options I had in my 2.4 kernel for some reason - rebooted and my<br>firewall didn't come up. Other than that though it went well.<br>
<br>Here's a nice tip if you use lilo on a remote server. If you run:<br><br>lilo -v<br>lilo -v -R LinuxNEW<br><br>where LinuxNEW is a new entry in lilo.conf - then the next reboot will<br>boot into the kernel defined in the LinuxNEW label and if it fails and
<br>you get a kernel panic the next reboot will boot back into your usual<br>working default kernel image.<br></blockquote></div><br>Thanks Josh. At the moment, I think I'm going to stick with the 2.4 kernel. Not sure if I'm feeling brave enough to attempt a massive upgrade to Slack-current on my desktop.
<br><br>Being that I haven't had a successful compile before on a kernel, I want to keep the same config I have, just tweak it for larger memory (>1GB), nForce drivers and an AMD processor. Is this the correct process?
<br><br>cp /usr/src/linux /usr/src/linux-newversion<br>cd /usr/src/linux-newversion<br>step the EXTRAVERSION in /usr/src/linux-newversion<br>make oldconfig<br>make dep<br>make menuconfig or xconfig (modifying the kernel)<br>
make dep<br>make clean<br>make bzImage<br>make modules<br><br>Beyond that is where I get mixed up. I've read Slack documentation, and countless other places from <a href="http://Linuxquestions.org">Linuxquestions.org</a>
and alt.os.linux.slackware and beyond. Everyone has their own way of doing it, but I have yet to find on that seems to work for me.<br><br>Thanks!<br><br>-- <br>-Shawn<br><br>-Nemo me impune lacessit. Ne Obliviscaris..
<br>