On 10/25/2017 12:24 PM, Larry Finger wrote:
On 10/25/2017 11:04 AM, Neal Gompa wrote:
On Wed, Oct 25, 2017 at 12:02 PM, Ken Schneider - Factory
wrote: Today when I ran zypper dup to openSUSE Tumbleweed 20171019-0 -> 20171023-0 "dracut" ran no fewer then FOUR times. There is no need for this to happen with ANY dup.
( 21/462) Installing: plymouth-branding-openSUSE-13.3-8.8.noarch ......................................................[done] Additional rpm output: dracut: Executing: /usr/bin/dracut -f
depmod: WARNING: //lib/modules/4.13.5-1-default/weak-updates/updates/nvidia.ko disagrees about version of symbol module_layout Warning: /lib/modules/4.13.5-1-default is inconsistent Warning: weak-updates symlinks might not be created Creating initrd: /boot/initrd-4.13.5-1-default dracut: Executing: /usr/bin/dracut --logf
(145/462) Installing: kernel-default-4.13.8-1.1.x86_64 ......................................................[done] Additional rpm output: Creating initrd: /boot/initrd-4.13.8-1-default dracut: Executing: /usr/bin/dracut --logfi
(462/462) Installing: sddm-branding-openSUSE-0.15.0-2.1.x86_64 ...........................................................[done] Output of kernel-firmware-20171009-1.1.noarch.rpm %posttrans script: Creating initrd: /boot/initrd-4.13.5-1-default dracut: Executing: /usr/bin/dracut --logfil
If something needs "dracut" to be run have it run ONCE at the end of the dup. Surely a flag can be set for this.
It could be done as a post-transaction trigger, probably as a file trigger.
If a zypper run aborts, and dracut has not been run when it was needed, will the system still be bootable?
Larry
I don't see why an older kernel could not be selected. If zypper crashes half way through it can be rerun (zypper) after booting to CLI and if not there are more serious problems with the system. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org