On 2014-01-12 20:08 (GMT-0800) Linda Walsh composed:
Felix Miata wrote:
Anyone know a better way to keep a module out of a dracut initrd, or an equivalent way to prevent mkinitrd from including sata_sil in initrds for 13.1?
Wouldn't it be faster to rebuild your kernel once?
Maybe if: 1-I ever build any binary of any kind for any reason and have room for devel software and have it installed (I don't, & I don't, & I don't) 2-I didn't have multiple multiboot systems with similar trouble multiplied but different hardware
If you updated a driver, make would only need to compile that driver and relink once and place results in usable format on the boot disk.
Or just flip a switch in the right place so that that an unwanted module won't be loaded without prior permission, top notch reason and/or appropriate timing.
Um... I think the limitations of the workaround of not allowing users to build their own kernel for native boot of their HW are beginning to rise exponentially.
Not just for kernel, but for other things being overhauled and/or supplanted without thorough investigation of ramifications, testing "edge cases" and uncommon hardware in particular. I routinely wonder if the average FOSS programmer works with more than one or maybe two systems, or uses any systems more than 3-6 years old, and is conscious that his small hardware sample is often wholly inadequate as test vehicle. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org