Carlos E. R. wrote:
On 2016-04-12 20:46, Dave Howorth wrote:
On Tue, 2016-04-12 at 21:00 +0300, Andrei Borzenkov wrote:
What possible reason is there for an update to rebuild anything, kernel or initrd -wise? Updates should be installing a new kernel and initrd and leaving everything that is already installed completely alone. If udev or, god forbid, systemd need it rebuilding then they should be part of the kernel multi-versioning system. Updates shouldn't break existing working systems under any circumstances.
The initrd image does not only contain kernel modules, but also configuration files (like /etc/fstab) and binaries needed for initial fsck and mount, even in the case that /usr is on a different partition.
The only way I can see to protect from these mishaps is to keep backup copies of the initrd, made automatically somehow - perhaps a daily cronjob, storing them in /var/adm/backup/, for instance (only if modified, not really a daily copy).
Another way would be for the upgrade process to create a backup before writing a new one. If I ran dracut myself and forgot to back up the initrds, I would have only myself to blame, but with an otherwise innocent "zypper patch", I have to remember it before I hit enter, just in case. Sometimes our otherwise solid openSUSE system framework feels more like some rickety bamboo scaffolding. -- Per Jessen, Zürich (13.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org