On 6/6/08, Geoff Steckel <[EMAIL PROTECTED]> wrote: > Threats of unspecified system instability are hard to believe.
http://marc.info/?l=openbsd-misc&m=109088660014351&w=2 > For systems which must boot very quickly, removing unused drivers > whose probe routines cause significant timeouts can make a big > difference. Sometimes timeouts are the only way to check for an > I/O device behind a blind interface. For instance, checking > a floppy drive's seek time is a significant wait. introducing config. You're compiling your own kernel, so you must have read the man page for config, right? So you know there's no reason to actually compile anything, right? > For systems which are intended to run with little memory or which > are straining at architectural limits, 100K here and 100K there > can make quite a big difference in what applications can run. > Many drivers are over 150K when linked. When a megabyte or two > counts, removing 10 drivers could make a big difference. Given the cost of hardware today, the fraction of total memory that one megabyte represents, and the nature of any job that needs "all your memory", by the time you finish compiling that kernel it's going to need two megabytes more, not just one. And then what? > If the kernel code is well structured, the following must be true: > > Removing a driver which is essential to normal operation must > cause the kernel compile or link stage to fail. What compiler are you using that can detect your system's hardware for you?
