Cc: Adrian Bunk <bunk@...>, Randy Dunlap <randy.dunlap@...>, Sam Ravnborg <sam@...>, Al Boldi <a1426z@...>, <linux-usb@...>, <linux-kernel@...>, David Brownell <david-b@...>, Greg KH <greg@...>, Andrew Morton <akpm@...>
Ok, I'll bite.
what config options must be selected by the user at build time? (i.e. no
sane default can possibly be deduced from the hardware)
there are a lot of options that, if selected, will affect the final result
significantly. but I can't think of any that can't have a reasonable
default.
what sysadmins like me would really like is a set of scripts that could
generate a .config from an existing system. After we have one that covers
the hardware for the system we will then have a much better starting point
to work from. We may disable some drivers (sound drivers on a server for
example). We may enable other drivers (or combine the results of runs on
seperate hardware to make a slightly more general kernel config). And we
will make many other selections that are not hardware dependant (SLAB vs
SLUB vs SLOB, IO schedulers, etc) but just figuring out what drivers are
needed to support a particular piece of hardware would be a huge help.
It's frequently hard to figure out which drivers are needed for a Vendor X
model 12345 motherboard (major things are easy, it gets hard when you want
to do power monitoring and things like that) it is even harder when you
have to figure out what needs to be enabled so that you can see the help
text of other options to see if they are the right ones.
I started toying with Linux (on my home systems) in the 0.99 days and have
been makeing my living with it starting in the 1.3 days, so it's not that
I am a newcomer to kernel configuration, but even with my experiance it's
sometimes hard to figure out what I need to enable when I start needing a
new set of functionality on a system.
David Lang
--
