Someone in #debian mentioned to me that they were getting some odd errors in their logs when running gparted. It seems that several years ago there was someone with a problem caused by systemd auto mounting filesystems in response to udev events triggered by gparted, and so as a workaround, gparted masks all mount units. Curtis Gedeck and I can't seem to figure out now, why this was needed because we can't seen to get systemd to automatically mount a filesystem just because it's device is hot plugged. Are there any circumstances under which systemd will mount a filesystem when it's device is hotplugged? Also I'm pretty sure this part is a bug in systemd: any service that depends on -.mount ( so most of them ) it will refuse to start while -.mount is masked. It shouldn't matter that it's masked if it is already mounted should it? Only if it isn't mounted, then it can't be mounted to satisfy the dependency. _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel