This has been planned for quite some time (actually about a year now)......
Dracut is a much more generic Intiramfs tool then Mkinitcpio (pretty much Arch only) and way better maintained.
A first version of Dracut is up in the [build] repo. It does not include any KaOS specific config files. So to test, you will have to run dracut command manually.
Testing locally right now with an image created with:

sudo dracut --hostonly --no-hostonly-cmdline --kernel-image  --zstd --kver 5.11.11-1-next /boot/initramfs-linux-dra.img --no-early-microcode --force

Boots without issue, just some mismatches with local udev rules, not matched by that image (yet).
ISO testing (internal) with Dracut will start shortly too, if all goes well, expect Dracut to be on the next stable release.

Yes. Boots OK on Older AMD PC and with no noticible glitches or errors, limited usage so far.

I've not use it since years, actually think it's dated but it looks like Mandriva was using future of Linux more than 10 years ago 😃

  • demm replied to this.

    bvbfan actually think it's dated

    Mkinitcpio lost it's original maintainers (was not maintained for 2 years, seems many of the long-term devs have been leaving Arch recently), Dracut is constantly maintained, and always with many distro's in mind.
    Since KaOS uses systemd-boot as default, it even includes the --uefi option to create an .efi image that is automatically added to the systemd-boot menu. Probably won't use that option as long as as BIOS systems are still supported in KaOS. So, in all, not dated at all.

      8 days later

      The linux-next kernel (from 5.11.12 on) now defaults to using dracut for initramfs creation, if dracut is installed on the system. If all goes well, then linux-next will hard depend on dracut so all linux-next users will automatically switch.
      No need to make any changes to the bootloader, img has the same name & path, so the bootloader does not see any change.