X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.mount.xml;h=d1940831a9d6bd14f23442386a66eaf55088f8ee;hp=f32861b159ed48cd7f766f5ccc1c1697b74137f5;hb=236bc7573a400b77e515c441a34419b133d11b18;hpb=878836df2d714a9580ad31b9db88fda862e0df50
diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml
index f32861b15..d1940831a 100644
--- a/man/systemd.mount.xml
+++ b/man/systemd.mount.xml
@@ -75,9 +75,14 @@
binary is executed in, and in
systemd.kill5
which define the way the processes are
- terminated. The User= and Group= options are not useful
- for mount units specifying a Type= option; the mount
- binary must run as root if there is a specified type.
+ terminated. Note that the User= and Group= options are
+ not particularly useful for mount units specifying a
+ Type= option or using configuration
+ not specified in /etc/fstab;
+ mount8
+ will refuse options that aren't listed in
+ /etc/fstab if it is not run as
+ UID 0.
Mount units must be named after the mount point
directories they control. Example: the mount point
@@ -97,10 +102,18 @@
in the file system hierarchy, a dependency between both
units is created automatically.
- Mount points created at runtime independent on
- unit files or /etc/fstab will be
+ Mount points created at runtime (independently of
+ unit files or /etc/fstab) will be
monitored by systemd and appear like any other mount
unit in systemd.
+
+ Some file systems have special semantics as API
+ file systems for kernel-to-userspace and
+ userspace-to-userpace interfaces. Some of them may not
+ be changed via mount units, and cannot be disabled.
+ For a longer discussion see API
+ File Systems.