Hi, one additional point to consider against using initrd/initramfs path argument in kernel hooks.
On my system I have set up dracut to generate UKIs using uefi option: $ cat /etc/dracut.conf.d/99-uefi.conf uefi=yes With the option set and output filename not specified, dracut generates UKIs and places them in /boot/efi/EFI/Linux But if the output filename is set resulting kernel images overwrite initrd/initramfs files, which is confusing and lead to broken boot: $ sudo apt install --reinstall linux-image-6.11.10-amd64 ... /etc/kernel/postinst.d/dracut: dracut: Generating /boot/initrd.img-6.11.10-amd64 ... $ file /boot/initrd.img-6.11.10-amd64 /boot/initrd.img-6.11.10-amd64: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows, 9 sections Please consider avoiding explicitly specified initrd/initramfs filenames in kernel hooks. Best, Roman
