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>

diff --git a/docs/udev.xml b/docs/udev.xml
index 3db66f80016d4ea2ad55bf81e03359101a8b72df..8c07f0e68746ca3884c9c0cadf3c5d0f228d889e 100644 (file)
--- 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>
@@ -424,18 +422,6 @@
               </listitem>
             </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>

diff --git a/udev.8 b/udev.8
index 2ea58120924ec85f22053f69d5922413c973e9f1..c6ab83e8056ed96792603c1cff6f1c3588a8956c 100644 (file)
--- a/udev.8
+++ b/udev.8
@@ -17,9 +17,7 @@ directory, or it renames network interfaces.
 .PP
 Usually udev runs as 
 \fBudevd\fR(8) 
-and receives uevents directly from the kernel if a device is added or removed form the system. The program 
-\fBudev\fR 
-itself may be used as an event handler in situations, where running the daemon is not appropriate, like in initramfs.
+and receives uevents directly from the kernel if a device is added or removed form the system.
 .PP
 If udev receives a device event, it matches its configured rules against the available device attributes provided in sysfs to identify the device. Rules that match, may provide additional device information or specify a device node name and multiple symlink names and instruct udev to run additional programs as part of the device event handling.
 .SH "CONFIGURATION"
@@ -182,7 +180,7 @@ The devpath of the device.
 \fB%s{\fR\fB\fIfile\fR\fR\fB}\fR, \fB$sysfs{\fR\fB\fIfile\fR\fR\fB}\fR
 The content of a sysfs attribute.
 .TP
-\fB%e{\fR\fB\fIkey\fR\fR\fB}\fR, \fB$env{\fR\fB\fIkey\fR\fR\fB}\fR
+\fB%E{\fR\fB\fIkey\fR\fR\fB}\fR, \fB$env{\fR\fB\fIkey\fR\fR\fB}\fR
 The value of an environment variable.
 .TP
 \fB%m\fR, \fB$major\fR
@@ -196,11 +194,6 @@ The string returned by the external program requested with PROGRAM. A single par
 \fB%c{N}\fR. If the number is followed by the '+' char this part plus all remaining parts of the result string are substituted: 
 \fB%c{N+}\fR
 .TP
-\fB%e\fR, \fB$enum\fR
-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.
-
-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.
-.TP
 \fB%P\fR, \fB$parent\fR
 The node name of the parent device.
 .TP