The output is fairly similar for both I don’t favor either one for output, it does stuff, tells u what stuff it does, tells u if something goes wrong (or is at least supposed to do so).
But on dracut, I had a boot issue, and for whatever reason I decided to backup my initramfs before trying to fix it; so I booted off the install usb, chrooted in, ran something like dracut --regenerate-all, output looked good, everything seemed fine, tried to reboot, it was still broken.
Now I don’t remember how I actually solved that issue (dracut was actually the root cause of the issue though, it had to do with drive encryption password… yeah right i remember now, it defaulted the keyboard to english on boot for a certain version of dracut, it was fixed pretty quick but the result was i couldn’t boot because i used non-english characters in my password, i solved it by making a new password with only english characters BUT) after I had solved it, I thought I still had a problem cuz I still couldn’t boot and the result sitll looked basically the same as the original issue, until I restored my initramfs backup, then it booted just fine.
I.e. dracut created a broken initramfs and didn’t so much as give me a warning about it.
Maybe I was supposed to use some other command, but I wasn’t exactly looking to become a dracut wizard or anything, so --regenerate-all was the most promising command I saw in the help dialogue, and it looked like it worked too, generated all the right files, no errors, but didn’t work.
mkinitcpio by comparison never failed, I stil lremember the command roughly, or maybe exactly (which implies to me that arch users use it a lot, cuz it’s been a long time for me), mkinitcpio -p linux although depending on distro and system configuration you may have to specify which linux you’re referring to, but that was easy to find as well in like a dozen different ways.
