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.. -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 http://usdebtclock.org/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
