diff options
| author | Lennart Poettering <lennart@poettering.net> | 2019-03-14 11:22:47 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-03-15 16:37:17 +0100 |
| commit | f0e3650de1a9655ead18e433456bd535ee3321d9 (patch) | |
| tree | 7fc685b205c4532c5f61ca02d2b93617196ef7c0 /man/systemd-mount.xml | |
| parent | 75910ed9f40471d3d25684ae61d242dbc2766f5a (diff) | |
| download | systemd-f0e3650de1a9655ead18e433456bd535ee3321d9.tar.gz | |
man: clarify that /run/media/system/ is where mounts are placed by default
Prompted by the discussions on: https://github.com/systemd/systemd/issues/11982#issuecomment-472781806
Diffstat (limited to 'man/systemd-mount.xml')
| -rw-r--r-- | man/systemd-mount.xml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/man/systemd-mount.xml b/man/systemd-mount.xml index cfb15ef518..e557ee80a1 100644 --- a/man/systemd-mount.xml +++ b/man/systemd-mount.xml @@ -55,13 +55,14 @@ the service manager job queue, so that it may pull in further dependencies (such as parent mounts, or a file system checker to execute a priori), and may make use of the auto-mounting logic.</para> - <para>The command takes either one or two arguments. If only one argument is specified it should refer to a block - device or regular file containing a file system (e.g. <literal>/dev/sdb1</literal> or - <literal>/path/to/disk.img</literal>). If it is a block device, which is then probed for a label and other - metadata, and is mounted to a directory whose name is generated from the label. In this mode the block device must - exist at the time of invocation of the command, so that it may be probed. If the device is found to be a removable - block device (e.g. a USB stick) an automount point instead of a regular mount point is created (i.e. the - <option>--automount=</option> option is implied, see below).</para> + <para>The command takes either one or two arguments. If only one argument is specified it should refer to + a block device or regular file containing a file system (e.g. <literal>/dev/sdb1</literal> or + <literal>/path/to/disk.img</literal>). The block device or image file is then probed for a file system + label and other metadata, and is mounted to a directory below <filename>/run/media/system/</filename> + whose name is generated from the file system label. In this mode the block device or image file must + exist at the time of invocation of the command, so that it may be probed. If the device is found to be a + removable block device (e.g. a USB stick) an automount point instead of a regular mount point is created + (i.e. the <option>--automount=</option> option is implied, see below).</para> <para>If two arguments are specified the first indicates the mount source (the <replaceable>WHAT</replaceable>) and the second indicates the path to mount it on (the <replaceable>WHERE</replaceable>). In this mode no probing of the |