On 30/03/2023 11.30, Carlos E. R. wrote:
On 2023-03-30 11:14, Antonio Feijoo via openSUSE Factory wrote:
On 30/03/2023 10.47, Carlos E. R. wrote:
On 2023-03-30 09:49, Antonio Feijoo via openSUSE Factory wrote:
Hi,
As you might know, for quite some time `mkinitrd` is just an incomplete wrapper that internally calls `dracut` and `update-bootloader` (unless it's called with `-B`).
Finally, all known packages that required it in their spec file or were found to be using it have been fixed. Hence, it's time to move on. The next `dracut` update in Factory will not provide the `dracut-mkinitrd-deprecated` package. This is planned to be submitted in mid-April, before 2023-04-14, so if you still use `mkinitrd` in any of your packages or custom scripts, please replace it with `dracut` (plus `update-bootloader` if necessary).
Please advise us users what exact command concoction to use instead. Me, and many others, are used to just run "mkinitrd" for many years.
There is no direct match between the arguments accepted by both commands. I'm afraid you need to check what arguments you're currently using with `mkinitrd`, and find their corresponding `dracut` arguments. Both commands provide `-h` for quick usage help.
I don't remember ever using any parameter with mkinitrd, unless being told to do so at some point.
`mkinitrd` = `dracut -f --regenerate-all --logfile /var/log/YaST2/mkinitrd.log ; update-bootloader --refresh` - If you just want to build your current initrd, you can avoid `--regenerate-all`. There is also a nice `--parallel` option to speed up this process (not available using `mkinitrd`). - If you still want a log file, you can set `logfile=` in /etc/dracut.conf to avoid using `--logfile` on every call.
The main difference is that `mkinitrd` updates the bootloader configuration by default, using the `update-bootloader` command internally, unless called with the `-B' option.
I don't know that that command is.
For the purpose of the initrd generation, it updates `grub.cfg`, among other things.