Thanks for your prompt response!
On 2024-06-19 13:41, Thomas Lange wrote:
> I rembember there was a discussion about the initrd name and the
> plan was to have the same name on all distributions
That's reasonable, but regardless of what the "standard" initrd
name is or will be, probably *both* manual dracut and
post-install hooks should use the same standard name, then. Plus
GRUB should pick up that new name. (I haven't checked whether
update-grub picks up the initramfs-*.img names.)
> , and there's a new option in dracut.conf
The "initrdname" option does not seem to be suitable for the
"--regenerate-all" use-case since it does not allow for the
kernel version to be templatized (from /usr/bin/dracut):
if ! [[ $initrdname ]]; then
initrdname="initramfs-${kernel}.img"
fi
[...]
else
outfile="$dracutsysrootdir/boot/$initrdname"
fi
My experiments with 'initrdname="initrd.img"' confirm that:
------------------------- snip -------------------------
[~]$ cat /etc/dracut.conf
[...]
initrdname="initrd.img"
[~]$ sudo dracut --quiet --force --regenerate-all
[~]$ ll -tr /boot
[...]
-rw------- 1 root root 28742715 Jun 18 11:07 initrd-fallback.img-6.7.12-amd64
-rw------- 1 root root 28477336 Jun 19 12:08 initramfs-6.6.15-amd64.img
-rw------- 1 root root 28742400 Jun 19 12:08 initramfs-6.7.12-amd64.img
-rw-r--r-- 1 root root 28538617 Jun 19 13:48 initrd.img-6.6.15-amd64
-rw------- 1 root root 28804327 Jun 19 13:48 initrd.img-6.7.12-amd64
drwxr-xr-x 5 root root 4096 Jun 19 13:58 .
-rw------- 1 root root 28804621 Jun 19 13:58 initrd.img
------------------------- snip -------------------------
> It seems that dracut uses initramfs... by default but Debian is
> using initrd... when calling /etc/kernel/postinst.d/dracut
I dug a bit deeper into this, and for dracut <= 60 there was
patch debian/patches/initrd-not-initramfs.patch. More
specifically:
dracut (059-4) unstable; urgency=low
* Fix file name in patch initrd-not-initramfs.patch
Closes: #1029413, #1030191
Thanks to nabijaczleweli for for the patch
-- Thomas Lange <la...@debian.org> Thu, 09 Mar 2023 19:13:42 +0100
Probably we could have something like that again, to lower user
confusion? I can provide an updated patch, if needed.
> So if you still using the kernel postinst hook, things are fine
> IMO.
Not sure what you mean here. That I call the kernel postinst
hook manually to regenerate the initramfs's?
If yes, using the kernel postinst hook manually has the minor
disadvantage that you have to loop over the installed kernels to
cover all of them, while "dracut --regenerate-all", well, does
*all* kernels out of the box.
Thanks
Jens
