Something that helps to is to never remove your known working kernel entry from your bootloader, and make your new kernel the secondary manually selected kernel on your first boot. This way if your kernel is hosed for some reason, you should always be able to recover your system with minimal pain by rebooting into your default working kernel. later, Steve Andrew Dahlin wrote: > honestly, compiling a kernel is trivial once you build one successfully. the first time will take a few hours to get it right (tops), but by the time you're done, you know exactly what you're doing. i can configure a kernel from scratch in about 20 minutes... and i'm not a hacker or anything... i just know what i need. i'm not saying everyone should build their own kernel, but if you install your distro's sources (with their .config), it's fairly risk free. just back up your old kernel. [OT: if you run lilo, don't forget to run lilo after copying over the new kernel. TONS of people don't realize this their first time] > > --Andrew > > > On Thu, 12 Aug 2004 21:35:36 -0400 > Lee Revell <rlrevell@xxxxxxxxxxx> wrote: > > >>On Thu, 2004-08-12 at 21:25, Russell Hanaghan wrote: >> >> >>>I appreciate both points guys... >>> >>>I think the main one to take from this is a classic; >>>"If it ain't broke, Don't fix it!" :) >>> >>>I find myself digging into a perfectly tight operating system with all >>>the array of perfectly functional audio apps I use....and hours and >>>hours later sit there pissed off and frustrated because I didn't achieve >>>any noteworthy results from it all...and I only like to do so much >>>_learning_ at a time! :) >>> >> >>One other tip I found useful is, if you do have to compile your own >>kernel from a kernel.org kernel, use the .config from your vendor's >>kernel source package. That way you get a kernel that is close as >>possible to the vendor kernel, and you minimize the chance of breaking >>anything that currently works. >> >>Lee >>
