On 04/19/2015 04:16 PM, Linda Walsh wrote:
Wouldn't it be possible to modify something like Wicked to draw up a list of needed modules for a user's specific machine -- building in required HW (disks, file systems, etc) and making modules for "possible modules for your machine.
After you have a list of your HW, for future builds, you can simply copy the previous config and do a "make oldconfig". I can't imagine kernel build times taking that long, but I don't compile modules for HW I don't have -- most of the modules are for software options. # modules per 'section':
Never mind the "build"! I can understand the install medium needing every possible module since at install time the installer has to probe for hardware. I can understand the USB means many more possible devices. But ... There are a lot of "Buts..." There are probably mnore for a laptop than a desltop. Laptops don't have the open chassis that many desktops have :-) I can understand a generic build for a distribution, yes. But ... Lets face it: ... Better than 99% of Linux users aren't "doing" the specialized kernel builds that Linda does. ... Better than 95% of Linux users aren't as technically sophisticated as the regular contributors here, not do that want to be. The just want their applications to work. Think "Android". When I get a new kernel from Kernel_Stable I still have ... ... To run a mkinitrd or equivalent. And OUCH, that hits all four cores and for a few seconds I'm not getting much work done! Well! At this point we get back to a situation like Linda describes. I've downloaded ALL the modules, even those for hardware I can't imagine using (or affording!). This is not the debugging kernel, so like most of the application binaries, it is 'stripped". (See 'man 1 strip') So why not 'strip' out the modules that aren't needed/wanted? Or make them a load on demand? We are already doing a load-on-demand for kernel modules. If you run a ATI or a Nvida GPU then you have to load the driver. Is it too much to ask to extend the /etc/modules/d/ tree to 'strip' or ever load "blacklisted" modules? Oh, right, "HERESY!" perhaps not quite as controversial as KDE4 or systemd.... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org