On Fri, 25 Dec 2009 05:07:55 -0500 Paul Cartwright <a...@pcartwright.com> wrote:
> On Thu December 24 2009, Celejar wrote: > > > relating to doing so. When compiling one's first custom kernel one > > > should start with _ONLY_ the functionality one needs. Then build things > > > up from there as you need more abilities from you kernel. ;) > > > > But I'd add that it's very easy to disable something that you don't > > realize you need, so be very careful about what you disable. The > > quality and penetrability of the kernel docs really varies widely ... > > this is the "learning" part.. knowing what you need, what you MIGHT need, and > what you don't have to have to make it work.. Absolutely. I'm just warning you to be prepared for a lot of very frustrating "why can't the kernel find my root filesystem?" and "why has this piece of HW / SW suddenly stopped working". One thing I'd recommend, although I've never really done this myself, is keeping some sort of journal where you record changes you make and their results. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
