It can’t be that hard to do.Ī: Such a functionality isn’t needed on a properly configured system. See the udev faq (small fraction follow): Your assertion about checking each /dev/* is flawed on these days. Today almost all computers and devices come in one or another PnP flavor and they generate the appropriate event about their existence (and luckily, the kernel will recognize it). This is not how things work on linux, at least, not since udev started to be used, it was partially true on devfs era. The only time when kernel size matters is on small boot devices that simply don’t have the space, but there are techniques to go around that. I honestly don’t see what a lightweight kernel would accomplish. Provide the full kernel and make software that looks at the hardware and uses the appropriate drivers. Just to obtain a more lightweight kernel? Why? What distro’s do today makes much more sense. Who’s going to do that? Teoretically you could design software that can probe all the /dev entries known to mankind and still not obtain 100% accurate results.Īnd in order to do that you’d need to do what distro’s already do (put together a full kernel), except instead of leaving it there and using what you need, you attempt to conduct a complicated hardware investigation, error prone, with the end result of deleting the full kernel you went to the trouble of producing and using a smaller subset of it.Īnd for what? You’re losing perspective. Some of them need configuration (module parameters and device-module aliasing) to work. And who’s going to load just the modules that are actually needed by the machine? Modules get loaded automatically when a program attempts to access the relevant /dev devices.
0 kommentar(er)
