On 26.06.2013 11:32, Felix Miata wrote:
On 2013-06-25 21:13 (GMT+0400) Andrey Borzenkov composed:
Felix Miata composed:
This is the other thing that routinely annoys me about working initrds getting rebuilt every time any package that ever affects what makes up an initrd gets an update[1]. Why shouldn't working initrds be left alone, and new packages get put into them only either when a new kernel is installed, mkinitrd is called by a user, or an affirmative answer is given to a request to rebuild by an updated package installation? The way initrds get clobbered now, what point is there to enabling multiversion for kernels?
I dare to guess that the reason is to ensure that binaries in initrd match binaries on your system.
Your reply seems to answer only the first of the two separate questions.
Is it better to have binaries match in a clobbering initrd that won't boot the system? I think not.
And how do you know forehand if the new binaries break or fix the system? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org