1 files changed, 52 insertions, 35 deletions
diff --git a/upstream/fedora-rawhide/man5/systemd.mount.5 b/upstream/fedora-rawhide/man5/systemd.mount.5
index 62d7fb91..894df873 100644
--- a/upstream/fedora-rawhide/man5/systemd.mount.5
+++ b/upstream/fedora-rawhide/man5/systemd.mount.5
@@ -1,5 +1,5 @@
 '\" t
-.TH "SYSTEMD\&.MOUNT" "5" "" "systemd 255" "systemd.mount"
+.TH "SYSTEMD\&.MOUNT" "5" "" "systemd 256~rc3" "systemd.mount"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -104,10 +104,12 @@ If a mount unit is beneath another mount unit in the file system hierarchy, both
 .IP \(bu 2.3
 .\}
 Block device backed file systems automatically gain
-\fIBindsTo=\fR
-and
+\fIRequires=\fR,
+\fIStopPropagatedFrom=\fR, and
 \fIAfter=\fR
-type dependencies on the device unit encapsulating the block device (see below)\&.
+type dependencies on the device unit encapsulating the block device (see
+\fIx\-systemd\&.device\-bound=\fR
+for details)\&.
 .RE
 .sp
 .RS 4
@@ -180,9 +182,18 @@ local\-fs\-pre\&.target, and a
 \fIBefore=\fR
 dependency on
 local\-fs\&.target
-unless
-\fBnofail\fR
-mount option is set\&.
+unless one or more mount options among
+\fBnofail\fR,
+\fBx\-systemd\&.wanted\-by=\fR, and
+\fBx\-systemd\&.required\-by=\fR
+is set\&. See below for detailed information\&.
+.sp
+Additionally, an
+\fIAfter=\fR
+dependency on
+swap\&.target
+is added when the file system type is
+"tmpfs"\&.
 .RE
 .sp
 .RS 4
@@ -197,17 +208,19 @@ Network mount units automatically acquire
 \fIAfter=\fR
 dependencies on
 remote\-fs\-pre\&.target,
-network\&.target
+network\&.target, plus
+\fIAfter=\fR
 and
-network\-online\&.target, and gain a
+\fIWants=\fR
+dependencies on
+network\-online\&.target, and a
 \fIBefore=\fR
 dependency on
-remote\-fs\&.target
-unless
-\fBnofail\fR
-mount option is set\&. Towards the latter a
-\fIWants=\fR
-unit is added as well\&.
+remote\-fs\&.target, unless one or more mount options among
+\fBnofail\fR,
+\fBx\-systemd\&.wanted\-by=\fR, and
+\fBx\-systemd\&.required\-by=\fR
+is set\&.
 .RE
 .PP
 Mount units referring to local and network file systems are distinguished by their file system type specification\&. In some cases this is not sufficient (for example network block device based mounts, such as iSCSI), in which case
@@ -312,8 +325,13 @@ In the created mount unit, configures a
 \fIWantedBy=\fR
 or
 \fIRequiredBy=\fR
-dependency on another unit\&. This option may be specified more than once\&. If this is specified, the normal automatic dependencies on the created mount unit, e\&.g\&.,
-local\-fs\&.target, are not automatically created\&. See
+dependency on another unit\&. This option may be specified more than once\&. If this is specified, the default dependencies (see above) other than
+umount\&.target
+on the created mount unit, e\&.g\&.
+local\-fs\&.target, are not automatically created\&. Hence it is likely that some ordering dependencies need to be set up manually through
+\fBx\-systemd\&.before=\fR
+and
+\fBx\-systemd\&.after=\fR\&. See
 \fIWantedBy=\fR
 and
 \fIRequiredBy=\fR
@@ -324,12 +342,16 @@ for details\&.
 Added in version 245\&.
 .RE
 .PP
-\fBx\-systemd\&.requires\-mounts\-for=\fR
+\fBx\-systemd\&.wants\-mounts\-for=\fR, \fBx\-systemd\&.requires\-mounts\-for=\fR
 .RS 4
 Configures a
 \fIRequiresMountsFor=\fR
+or
+\fIWantsMountsFor=\fR
 dependency between the created mount unit and other mount units\&. The argument must be an absolute path\&. This option may be specified more than once\&. See
 \fIRequiresMountsFor=\fR
+or
+\fIWantsMountsFor=\fR
 in
 \fBsystemd.unit\fR(5)
 for details\&.
@@ -550,13 +572,14 @@ Mount unit files may include [Unit] and [Install] sections, which are described
 \fBsystemd.unit\fR(5)\&.
 .PP
 Mount unit files must include a [Mount] section, which carries information about the file system mount points it supervises\&. A number of options that may be used in this section are shared with other unit types\&. These options are documented in
-\fBsystemd.exec\fR(5)
+\fBsystemd.exec\fR(5),
+\fBsystemd.kill\fR(5)
 and
-\fBsystemd.kill\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
+\fBsystemd.resource-control\fR(5)\&. The options specific to the [Mount] section of mount units are the following:
 .PP
 \fIWhat=\fR
 .RS 4
-Takes an absolute path of a device node, file or other resource to mount\&. See
+Takes an absolute path or a fstab\-style identifier of a device node, file or other resource to mount\&. See
 \fBmount\fR(8)
 for details\&. If this refers to a device node, a dependency on the respective device unit is automatically created\&. (See
 \fBsystemd.device\fR(5)
@@ -574,6 +597,13 @@ Takes an absolute path of a file or directory for the mount point; in particular
 Takes a string for the file system type\&. See
 \fBmount\fR(8)
 for details\&. This setting is optional\&.
+.sp
+If the type is
+"overlay", and
+"upperdir="
+or
+"workdir="
+are specified as options and they don\*(Aqt exist, they will be created\&.
 .RE
 .PP
 \fIOptions=\fR
@@ -649,20 +679,7 @@ Check
 for more settings\&.
 .SH "SEE ALSO"
 .PP
-\fBsystemd\fR(1),
-\fBsystemctl\fR(1),
-\fBsystemd-system.conf\fR(5),
-\fBsystemd.unit\fR(5),
-\fBsystemd.exec\fR(5),
-\fBsystemd.kill\fR(5),
-\fBsystemd.resource-control\fR(5),
-\fBsystemd.service\fR(5),
-\fBsystemd.device\fR(5),
-\fBproc\fR(5),
-\fBmount\fR(8),
-\fBsystemd-fstab-generator\fR(8),
-\fBsystemd.directives\fR(7),
-\fBsystemd-mount\fR(1)
+\fBsystemd\fR(1), \fBsystemctl\fR(1), \fBsystemd-system.conf\fR(5), \fBsystemd.unit\fR(5), \fBsystemd.exec\fR(5), \fBsystemd.kill\fR(5), \fBsystemd.resource-control\fR(5), \fBsystemd.service\fR(5), \fBsystemd.device\fR(5), \fBproc\fR(5), \fBmount\fR(8), \fBsystemd-fstab-generator\fR(8), \fBsystemd.directives\fR(7), \fBsystemd-mount\fR(1)
 .SH "NOTES"
 .IP " 1." 4
 API File Systems