В Tue, 25 Jun 2013 13:02:23 -0400 Felix Miata <mrmazda@earthlink.net> пишет:
On 2013-06-25 18:12 (GMT+0200) Stephan Kulow composed:
It looks like I just broke my laptop by updating to factory, I can't get past the initrd with something that sounds like broken storage setup in systemd/mkinitrd/udev. So I advise everyone not to update before I found out it was my fault :)
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. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org