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
projects / thirdparty / systemd.git / blobdiff