summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@suse.de>2005-12-23 00:49:02 +0100
committerKay Sievers <kay.sievers@suse.de>2005-12-23 00:49:02 +0100
commitc082b99acbc4b25fd133a88bfabf68eee23d7b0b (patch)
tree5dd2afc1ece7f35f1665ee70dc6f8104c44ec6ae /docs
parentd69b2203c37d32bbfbd81153a1fc99b55b7b6cbb (diff)
remove %e from man page
Simple %e enumerations never worked reliably outside of udevstart and udevstart is no longer recommended to use. Signed-off-by: Kay Sievers <kay.sievers@suse.de>
Diffstat (limited to 'docs')
-rw-r--r--docs/udev.xml18
1 files changed, 2 insertions, 16 deletions
diff --git a/docs/udev.xml b/docs/udev.xml
index 3db66f8001..8c07f0e687 100644
--- a/docs/udev.xml
+++ b/docs/udev.xml
@@ -42,9 +42,7 @@
<para>Usually udev runs as <citerefentry><refentrytitle>udevd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> and receives uevents directly from the
- kernel if a device is added or removed form the system. The program
- <command>udev</command> itself may be used as an event handler in situations,
- where running the daemon is not appropriate, like in initramfs.</para>
+ kernel if a device is added or removed form the system.</para>
<para>If udev receives a device event, it matches its configured rules
against the available device attributes provided in sysfs to identify the device.
@@ -393,7 +391,7 @@
</varlistentry>
<varlistentry>
- <term><option>%e{<replaceable>key</replaceable>}</option>, <option>$env{<replaceable>key</replaceable>}</option></term>
+ <term><option>%E{<replaceable>key</replaceable>}</option>, <option>$env{<replaceable>key</replaceable>}</option></term>
<listitem>
<para>The value of an environment variable.</para>
</listitem>
@@ -425,18 +423,6 @@
</varlistentry>
<varlistentry>
- <term><option>%e</option>, <option>$enum</option></term>
- <listitem>
- <para>If a device node already exists with the name, the smallest next free
- number is used. This can be used to create compatibility symlinks and enumerate
- devices of the same type originating from different kernel subsystems.</para>
- <para>Note: The use of the enumeration facility is unreliable for events that
- request a number at the same time. The use of enumerations in todays setups
- where devices can come and go at any time is not recommended.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><option>%P</option>, <option>$parent</option></term>
<listitem>
<para>The node name of the parent device.</para>