On Tue, Jun 18, 2013 at 01:45:09PM -0400, Phillip Susi wrote: > Various tools, but most notably partitioners, manipulate disks in such > a way that they need to prevent the rest of the system from racing > with them while they are in the middle of manipulating the disk. > Presently this is done with a hodge podge of hacks that involve > running some script or executable to temporarily hold off on some > aspects ( typically only auto mounting ) of plug and play processing. > Which one depends on whether you are running hal, udisks, udisks2, or > systemd. > > There really needs to be a proper way at a lower level, either udev, > or maybe in the kernel, to inhibit processing events until the tool > changing the device has finished completely. The question is, should > this be in the kernel, or in udev, and what should the interface be? What events are you wishing to inhibit? And who is in control of them? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
