-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-06-26 at 09:43 +0200, Stephan Kulow wrote:
On 26.06.2013 04:51, Carlos E. R. wrote:
I dare to guess that the reason is to ensure that binaries in initrd match binaries on your system.
But it is an interesting point.
If we have multiversion, but initrd is remade for both old and current versions, a failure breaks all kernel versions. We can not be sure that the old version will keep working as a failsafe.
It would have saved my laptop, but then again people whos system is fixed by an update would love to have the initrd updated on updates - so where shall we stop? I guess we should leave old kernels with old initrds, but I don't think we should keep an old initrd for the new kernel.
That's my meaning, yes. If updating the previous initrd is an issue, ie, some want it, some do not, then it might be configurable. If possible :-? - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHKvsQACgkQtTMYHG2NR9WtfwCdFx+QKN+4W6y3mXu/QIt5NKYm Ho8An3Q8OBVXvQq9KUugRekO/0lqTBi/ =XtAe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org