On Wed, Dec 26, 2007 at 10:34:35PM +0100, Josip Rodin wrote: > I suppose, although that's a much more general change that would have many > more consequences. How was the current priority for multipath-tools-boot > selected, is there a rationale for it being as high as 3 (now 4)? > I can't say I can see the reason offhand. I suppose you want it to be > before S30checkfs.sh and S35mountall.sh so that people can put multipath'd > drives into fstab, but why would it run as early as 3 or 4? It was moved that early because it had to be started _before_ udev. Basti was maintaining the package back then (0.4.5-2) and the changelog doesn't give a reason why this was done.
I moved it to start _after_ udev so the /dev/mapper entries get created correctly on the tmpfs (0.4.7-3). We can probably move it even later in the boot process but not after LVM cryptdisks and mdadm which would mean [21,24] if we also want to have it after module-init tools. But there might very well be something earlier that also wants access to block devices, who knows? 21 looks like a good choice but I wonder if we gain that much - you could always load necessary modules with modprobe <module> || treue in /etc/default/multipath-tools for your special requirements. In other cases an initramfs makes much more sense. Cheers, -- Guido
signature.asc
Description: Digital signature
