You are not logged in.
Pages: 1
Greetings!
I recently started using an initramfs due to moving my root filesystem to a RAID-1 array with 1.2 metadata. I have been using the following hooks until now:
HOOKS="base autodetect fsck mdadm"
However, I noticed that a few guides recommends using mdadm_udev instead of mdadm. That, however, requires adding the udev hook as well.
I switched to that configuration at the last kernel upgrade, but I don't notice any difference, except for a considerably larger initramfs image.
What exactly is the advantage of having udev in your init filesystem? Will the plain old mdadm hook become obsolete in the future?
Thanks.
Offline
You can read the help page to these hooks if you want to know more.
$ 'mkinitcpio -H mdadm'
$ 'mkinitcpio -H mdadm_udev'
Offline
I recently started using an initramfs due to moving my root filesystem to a RAID-1 array with 1.2 metadata.
What were you using before? A custom-compiled kernel? If not, I cannot grasp how could you boot without initramfs.
As far as I know udev is the preferred method to load the modules, so I don't see a problem in using it. What is exactly your concern?
Offline
What exactly is the advantage of having udev in your init filesystem?
Using udev means you don't have to worry about knowing exactly which modules to load, and you can effectively wait on devices which might take a while to show up (as you can expect symlinks like /dev/disk/by-*/* to be created asynchronously by udevd). I'm not sure why you're concerned about your initramfs image size -- udev really doesn't add that much weight.
Will the plain old mdadm hook become obsolete in the future?
Yes, it will. mdadm will soon™ be what mdadm_udev is now, with the latter being deprecated.
Offline
Pages: 1