<para>Device units are named after the
<filename>/sys</filename> and
<filename>/dev</filename> paths they control. Example:
<para>Device units are named after the
<filename>/sys</filename> and
<filename>/dev</filename> paths they control. Example:
in systemd as <filename>dev-sda5.device</filename>. For
details about the escaping logic used to convert a
file system path to a unit name see
in systemd as <filename>dev-sda5.device</filename>. For
details about the escaping logic used to convert a
file system path to a unit name see
available. Note that this and the
other tags are not taken into account
unless the device is tagged with the
available. Note that this and the
other tags are not taken into account
unless the device is tagged with the
the udev database, because otherwise
the device is not exposed as systemd
unit.</para></listitem>
the udev database, because otherwise
the device is not exposed as systemd
unit.</para></listitem>
to 1 the device will be considered
plugged the moment it shows up in the
udev tree. This property has no
to 1 the device will be considered
plugged the moment it shows up in the
udev tree. This property has no
device disappears from the udev
tree. This option is useful to support
devices that initially show up in an
device disappears from the udev
tree. This option is useful to support
devices that initially show up in an
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,