Messages in this thread | | | Date | Sun, 15 May 2005 10:08:55 -0400 | From | Scott Robert Ladd <> | Subject | Re: Automatic .config generation |
| |
Jesper Juhl wrote: > Where's the harm in just building all the sound > modules - you only load one in the end anyway, and the space taken by the > other modules is negligible with the disk sizes of today I'd say (ok, > there's some extra build time involved, but that shouldn't be a big deal > either).
A desktop computer with a large hard drive may be the norm for kernel developers, but it isn't (by far) the only environment where the kernel is built. Embedded devices, small systems, older hardware, and heterogenous networks all require a bit more finesse than a simple "build it all and throw the mess at the hardware" approach.
The complexity of the kernel is growing, making it more difficult for people to understand what they need and how to get it. It seems to me that a computer can analyze itself to determine the "best" build options. That's part of the reasoning behind my Acovea technology -- reducing complexity through smarter software.
http://www.coyotegulch.com/products/acovea
Acovea isn't directly applicable to the kernel, but the idea of the computer performing self-discovery is certainly valid. Once I get another project finished, I'm going to take a more formal look at kernel configuration, and see what might be done.
..Scott - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |