dracut VS mkinitcpio

Upstream has been telling people not to use a central configuration file for 8 years so nobody should really be putting anything in there to begin with. One can make a reasonable argument that ZFSBootMenu ought to override the configuration file just like it overrides the configuration drop-in directory, but another can make a reasonable argument that people who really know what they want may wish to load common configuration options for both their system and ZBM images in /etc/dracut.conf.

I absolutely have no idea... Seems like somehow something is not supported. You should create an issue in the dracut repo: https://github.com/dracutdevs/dracut/issues. That's something you should probably everywhere like I did in my issue: https://www.reddit.com/r/voidlinux/comments/11ofqt2/booting_with_dinit. The void community can sometimes be really unhelpful so I hope you will get help there.

bug 1529311 is closed as duplicate of bug 1476039 which was fixed by https://access.redhat.com/errata/RHBA-2018:0964 included in dracut-033-535.el7. These patches were mentioned in 1476039: https://github.com/dracutdevs/dracut/commit/19453dc8744e6a59725c43b61b2e3db01cb4c57c and https://github.com/dracutdevs/dracut/pull/261. Also it was mentioned that it was fixed in

It's a shell script that sets up some basics and runs an event loop to run hooks that eventually lead to the availability of your root device.

dracut can build initrd with bluetooth support

The documentation is super minimal, but the livenet module supports torrent files using the live:torrent: URL syntax.

Nope, all these environments are missing initial device configuration required for keyboard to be able to connect. (There was an attempt to add bluetooth support into dracut, that didn't go well)

I get exactly this error. So it turns out, the decryption depends on a systemd unitsystemd-cryptsetup-generator, which will not read any embedded cmdline parameters, only ones passed in the commandline so when the commandline parameter is asking to decrypt things, it is not generated.

This file has been changed recently and the wiki still references the old line. You have to modify this line now:

mkinitcpio is an arch thing: https://github.com/archlinux/mkinitcpio

The Arch Linux devs don't have infinite time and energy, so yes less-important issues that affect less users get diprioritized. You're welcome to PR the fix yourself, here's the mkinitcpio repo: https://github.com/archlinux/mkinitcpio

The general logic was changed in the new mkinitcpio release. https://github.com/archlinux/mkinitcpio/pull/54/files

That's an odd one since reinstalling the package fixes the issue. I wouldn't be so sure it's grub because it just loads the vmlinuz and initramfs that are suffixed with the pkgbase. That will not change based on the kernel version and pkgrel version. Someone brought up needing a hook. the mkinitcpio package already installs hooks and scripts necessary for maintaining a mkinitcpio prefix for each kernel for the initramfs image generation and installing vmlinuz to /boot/vmlinuz-${pkgbase} on upgrades. Everyone with the official mkinitcpio package is going to have the same /usr/share/libalpm/scripts/mkinitcpio-install shell script. Running grub-mkconfig is pointless for a kernel upgrade for the reason stated. All it does is export variables from /etc/default/grub and concatenates /etc/grub.d/* into a single config file. If there was a grub config issue it's unlikely you would ever be able to boot.

mkinitcpio made zstd the default on 2021-02-17

The number of thread is, but the compression level isn't. Because -3 is a sane default for the compression level in time of compression time and output file size, but this can differ for your machine. I find that on my machine best compression level is -15 or -16 for size and compression time. Since it will take a 1 second more to compress but it will yield a file 80% more compressed than the default. Here is the pill request where the defaults where changed mkinitcpio#47