> Touch /dev/.in_sysinit, as that stops /lib/udev/rules.d/65-md-incremental.rules > from messing with mdraid sets. > > This patch adds the touching twice, once to our own init, for when running > as standalone installer, and once in python for when running from a livecd, > to stop the udev trigger "block" we do will cause > /lib/udev/rules.d/65-md-incremental.rules to trigger in the livecd case. This means that now we're embedding knowledge of how the udev rules operate into the loader. They're already frustrated with us for using the udevdb directly, and now we'd be relying on knowing how some of the rules work and setting state up to make sure they function differently. I can just see this breaking in a week or two when the rules change. I don't like having to do this at all. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
