For a proposed fix: I would suggest that 1. /usr/lib/kernel/install.d/50-dracut.install be moved to dracut instead of dracut-core (dracut-core should be inert and not run hooks, and dracut conflicts with initramfs-tools which reduces ambiguity as to what should generate the initrd), 2. renamed /usr/lib/kernel/install.d/60-dracut.install so it runs after /usr/lib/kernel/install.d/55-initrd.install 3. 60-dracut.install should detect the initrd.img-$KERNEL_VERSION that was just copied by 55-initrd.install, and not run if it finds it. Because the hooks are all in dracut, the prior initrd was generated by dracut anyway.
This change preserves /boot/initrd.img-$KERNEL_VERSION, which may be used by other boot loaders installed in parallel with systemd-boot. An advanced user that doesn't need the initrd in /boot can chmod -x /etc/kernel/postinst.d/dracut, that file is under /etc and so the change will be preserved by dpkg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100296 Title: Double initrd in /efi/<machine-id>/<kver>/ with systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2100296/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
