On Jul 19, Ferenc Wagner <wferi@niif.hu> wrote: > > If you need udevsettle anywhere else than after running udevtrigger then > > something is either buggy or broken by design. > Really? So is /usr/share/initramfs-tools/scripts/local-top/mdadm > (from the mdadm package) wrong, or something else buggy or broken by > design? I also experienced the need for udevsettle when booting from > LVM over partitioned multipath devices. I thought it was the kpartx > invocation which I had to wait for before the lvm2 script. I'd be > grateful for some advice on how to handle such cases properly. In an event driven model everything should happen as a reaction to a kevent, introducing a serialization point is just a workaround for a broken design. Other distributions (SuSE at least) mount file systems with udev RUN rules as a side effect of the relevant device appearing. -- ciao, Marco
Attachment:
signature.asc
Description: Digital signature