On 2013-06-26 12:11 (GMT+0200) Stephan Kulow composed:
The way initrds get clobbered now, what point is there to enabling multiversion for kernels?
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?
Again, this is about behavior when multiversion is enabled for kernels. What ain't broke don't need fixin. If if got you booted, it wasn't broke. If you had to rescue boot instead, it was. Either save the new binaries for a newly installed kernel's initrd, or put them in _one_ old initrd only after acquiring permission to do so, either via config file, zypper cmdline option, interactively, or if some automagic mechanism determined that _it_ (one initrd) had been tried but never did work. And again I ask, what purpose is served having multiversion enabled for kernels if 100% of initrds get clobbered regardless whether they ever worked or not? -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org