On Tue, Nov 8, 2011 at 12:32 PM, Michal Soltys <sol...@ziu.info> wrote: > On 11-11-08 17:46, Michal Soltys wrote: >> >> Then even existing intiramfs image could (probably) be mdmon-agnostic. > > Actually: > > chroot /run/initramfs mdmon --takeover --all
One of the suggestion earlier in the thread is not mess with takeover at all. The rootfs md device is always monitored by a mdmon instance launched from /run/initramfs. The only way to update mdmon is to recreate the initramfs and reboot (which is similar to the experience of trying to update raidfoo.ko for the rootfs blockdev). _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
