<listitem><para>Query the user for locale, keymap, timezone, hostname

and root password. This is equivalent to specifying

<citerefentry><refentrytitle>org.freedesktop.machine1</refentrytitle><manvolnum>5</manvolnum></citerefentry>.

<citerefentry><refentrytitle>org.freedesktop.LogControl1</refentrytitle><manvolnum>5</manvolnum></citerefentry>

<listitem><para>Specifies the file system type to mount (e.g. <literal>vfat</literal>, <literal>ext4</literal>,

…). If omitted (or set to <literal>auto</literal>) the file system is determined automatically.</para></listitem>

<listitem><para>Do not synchronously wait for the requested operation to finish.

Use of this option is only recommended when <command>systemd-notify</command>

is spawned by the service manager, or when the invoking process is directly spawned

by the service manager and has enough privileges to allow <command>systemd-notify

</command> to send the notification on its behalf. Sending notifications with

<listitem><para>Takes a PKCS7 formatted binary signature of the <varname>RootHash=</varname> option as a path

to a DER encoded signature file or as an ASCII base64 string encoding of the DER encoded signature, prefixed

by <literal>base64:</literal>. The dm-verity volume will only be opened if the signature of the root hash

signature is valid and created by a public key present in the kernel keyring. If this option is not specified,

but a file with the <filename>.roothash.p7s</filename> suffix is found next to the image file, bearing otherwise

the same name (except if the image has the <filename>.raw</filename> suffix, in which case the signature file

must not have it in its name), the signature is read from it and automatically used.</para>

is not enabled. This setting not affect commands prefixed with <literal>+</literal>.</para>

<listitem><para>These options take a whitespace-separated list of directory names. The specified directory

names must be relative, and may not include <literal>..</literal>. If set, one or more

directories by the specified names will be created (including their parents) below the locations

defined in the following table, when the unit is started. Also, the corresponding environment variable

is defined with the full path of directories. If multiple directories are set, then in the environment variable

the paths are concatenated with colon (<literal>:</literal>).</para>

<listitem><para>Sets up a new file system namespace for executed processes. These options may be used to limit

access a process might have to the file system hierarchy. Each setting takes a space-separated list of paths

relative to the host's root directory (i.e. the system running the service manager). Note that if paths

contain symlinks, they are resolved relative to the root directory set with

<listitem><para>If the <varname>LogNamespace=</varname> service setting is used, contains name of the

selected logging namespace.</para></listitem>

<para>The control group path in the systemd hierarchy, the

the systemd slice unit name, the systemd unit name, the

unit name in the systemd user manager (if any), the systemd

session ID (if any), and the owner UID of the systemd user

unit or systemd session (if any) of the process the journal

entry originates from.</para>

<para>The kernel device name. If the entry is associated to

a block device, the major and minor of the device node,

separated by <literal>:</literal> and prefixed by

<literal>b</literal>. Similar for character devices but

prefixed by <literal>c</literal>. For network devices, this

is the interface index prefixed by <literal>n</literal>. For

all other devices, this is the subsystem name prefixed by

<literal>+</literal>, followed by <literal>:</literal>,

followed by the kernel device name.</para>

<para>The [MACVTAP] section applies for

netdevs of kind <literal>macvtap</literal> and accepts the

same key as [MACVLAN].</para>

<para>The [IPVTAP] section only applies for

netdevs of kind <literal>ipvtap</literal> and accepts the

same key as [IPVLAN].</para>

<para>Accepts the same key in [VXLAN] section.</para>

match the <literal>PeerTunnelId=</literal> value being used at the peer. This setting is

compulsory.</para>

<para>Accepts the same key in [MACsecReceiveChannel] section.</para>

<para>Accepts the same key in [MACsecReceiveChannel] section.</para>

<para>Accepts the same key in [MACsecTransmitAssociation] section.</para>

<para>Accepts the same key in [MACsecTransmitAssociation] section.</para>

<para>Accepts the same key in [MACsecTransmitAssociation] section.</para>

<para>Accepts the same key in [MACsecTransmitAssociation] section.</para>

<para>Accepts the same key in [MACsecTransmitAssociation] section.</para>

<literal>FooOverUDP</literal> provides the simplest no frills model of UDP encapsulation, it simply

<para>Specifies the port number, where the IP encapsulation packets will arrive. Please take note

that the packets will arrive with the encapsulation will be removed. Then they will be manually fed

back into the network stack, and sent ahead for delivery to the real destination. This option is

mandatory.</para>