On 01/29/2019 10:58 AM, Rich Freeman wrote:
Can't say I've tried it recently, but I'd be shocked if it changed much. The linux kernel guys generally consider this somewhat deprecated behavior, and prefer that users use an initramfs for this sort of thing. It is exactly the sort of problem an initramfs was created to fix.
I see no reason to use an initramfs (swingroot) if the kernel can do what is needed by itself.
Honestly, I'd just bite the bullet and use dracut if you want your OS on RAID/etc.
You obviously have a different opinion than Alan and I do. I dislike using an initramfs (swingroot) without a specific reason to actually /need/ one. As in the kernel is unable to do what is necessary by itself and /requires/ assistance of an initramfs (swingroot). (An encrypted root device or iSCSI connected root device comes to mind as a legitimate /need/ for an initramfs (swingroot).)
It is basically a one-liner at this point to install and a relatively small tweak to your GRUB config (automatic if using mkconfig).
The dracut command may be a one-liner. But the alteration to the system and it's boot & mount process is CONSIDERABLY more significant.
Dracut will respect your mdadm.conf, and just about all your other config info in /etc. The only gotcha is rebuilding your initramfs if it drastically changes (but, drastically changing your root filesystem is something that requires care anyway).
I can think of some drastic changes to the root file system that would not require changing the kernel, boot loader, or command line options.
But, if you're not using an initramfs you can get the kernel to handle this. Just don't be surprised when it changes your device name or whatever.
There are ways to get around the device naming issue. -- Grant. . . . unix || die
