Is Arch switching from mkinitcpio to dracut? And if so, how long will mkinitcpio likely be supported?
I’m asking as the Arch linux installation manual says to install mkinitcpio, so I did. I then made a hook that gives the user options to to boot into tmpfs, overlay, or a snapshot. I’m quite happy with it.
Then I came upon a few posts that say Arch is switching to dracut. That would be a shame for those that like injecting scripts/hooks into the boot process. Dracut seems to be exceedingly complex to figure out. And I’ve yet to see any clear documentation showing how to do create a boot script in it. The exception being cryptic man-like pages with no examples.
There was a plan for Arch to switch to dracut but nobody ever picked up the work so they stuck with mkinitcpio. Unless something has changed recently, I don’t think there are plans to switch.
That being said, it might make more sense to ask them directly instead of creating an account to ask here.
That seems true if you just want to use the default settings or change something simple like kernel compression. It’s great for that. However, the nightmare begins when you want to make scripts that interact with the ramdisk environment.
I’ve seen several posts of people who just can’t figure dracut scripting out but who are just fine with mkinitcpio. And dracut is not just a little more complex. It’s on an entirely new level of complexity. It’s pretty much a rabbit hole with little to no documentation for tutorials or scripting.
Anyways, as long as mkinitcpio is still around, I’m happy.
Even if the default were to change, you can still choose which one you want to use. I prefer dracut so I just add it to my pacstrap and just like that my Arch install uses dracut instead of mkinitcpio.
It doesn’t really matter what the default is; no reason to get excited.