On 2014-01-12 15:35 (GMT-0500) Carlos E. R. composed:
On 2014-01-12 21:27, Felix Miata wrote:
On 2014-01-12 12:27 (GMT-0300) Cristian Rodríguez composed:
remember to rebuild your initrd afterwards.
Why? Yet another new misfeature? Once an initrd has been written for a particular installation and kernel and confirmed working as designed and/or desired, it should not need to be rewritten just because some package with a component that an initrd might contain has been updated, especially not 5 times per update run. https://bugzilla.novell.com/show_bug.cgi?id=786318
It is not that.
What is not what?
If you change a label or uid or id reference to a partition that needs to be used while booting, you have to rebuild initrd.
Keyword: IF!!! Simply update OS and applications is not changing a label or changing a UUID or ID or reference that needs to be used while booting. WRT OP and 13.2, I thought I found a poor, apparent kludge. To /etc/dracut.conf add omit_driver+="sata_sil" then rebuild initrd(s). But, that only works if the sata_sil module is missing from the modules tree when the initrd is built, then restored until such time as another initrd is to be built. 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? -- "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