3 ms·
'litter their repos with broken-out kernel modules' You don't seem to understand why modules exist. It doesn't matter how many modules are available, they won'
by nailer 17y ago
'litter their repos with broken-out kernel modules'
You don't seem to understand why modules exist. It doesn't matter how many modules are available, they won't be loaded unless they're needed. Eg, for PCI hardware, unless you have hardware that modules.pcimap matches to a driver. There is no overhead from having modules available to load, just extra convenience next time you, say, add a NIC or somesuch.
Also no distro force-feeds you a kernel. You're always able to build your own in the rare event that you need to, or the more likely event that you just feel interested in doing so.
For a business, most people can understand the benefit of using the same software that a few million others do.
- blasdel 17y agoWhen I said 'broken-out kernel modules', I was referring to modules that are distributed as independent packages in the repository, instead of just sitting in /lib/modules/$(uname -r) I know exactly why modules exist, having written my own several times. The real benefit for stuff distributed with the mainline kernel is not runtime loading (you could just build them all statically), but unloading and reloading.