|
I've had this in mind for a while and have wondered why it hasn't yet been implemented . . .
What prevents the distribution install, either during the installation, or on first boot, from detecting the specific hardware of the machine on which it's been installed, and producing a custom installation of the OS? Effectively, 'lspci', "Oh, you have that particular piece of hardware, no need for /that/ module, but *this* one is exactly what you need."
Advantages:
* unneeded kernel modules definitely not in memory, because ...
* unneeded kernel modules no longer kept on disk
* if compiled, can be compiled /exactly/ for user hardware
* faster startup as only needed modules are available/scanned
On a related note, what keeps the installation from compiling (perhaps optionally) a custom kernel, with gcc optimizations for the individual machine, processor, ram, etc?
|
