Olaf Hering writes ("Re: [Xen-devel] [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service"): > On Wed, Nov 08, Wei Liu wrote: > > But is there really no way to ask nicely to see if systemd would accept > > a change in behaviour? That is, to make proc-xen.mount (or any attempt > > to mount API fs) a nop when xenfs is added to API file system. > > I have considered that as well. If the failing unit is "proc-xen.mount" > and /proc/xen exists, just ignore the error. I will check if and how > that can be done.
It seems to me that this should be the case for all mount units. Nothing here is Xen-specific, apart from the particular details of the consequential lossage. Ie, mount units should be idempotent even if something else has already mounted them. Certainly mount units should be a no-op if their functionality has been moved into the systemd internal mount table. Can we please see what systemd upstream think of that proposal ? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel