On 04/20/2015 01:06 PM, Per Jessen wrote:
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?
No, it's not too much, but what would you gain? What's the business-case and how does the installer pick the right sets of modules?
The Installer? I'm the one that edited the blacklist. I'm the one that has tor rebuild -- or used to before I adopted Intel -- the nvida driver. That happens when I do things like a mkinitrd. And every time I download a new kernel the old one(s) get purged, according the policy I set in zypp.conf. I see no reason additional purging of blacklisted modules shouldn’t be possible at that point. Because downloading a new kernel from kernel_Stable results in the mkinitrd ... Yes, the initial installer probes the hardware and sets the list of modules to be loaded at boot time for the hardware it sees. And yes, autoyast can be edited to do many things. And yes there is an issue of portability. But I'm talking about a more mature system. heck, any system gets heavily customized after the initial install, even by those of us who aren't Linda! -- 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