04-udev.8-tweak-numeric-id-text.diff
o change "return value" to "returned string"
o add textual owner/group example for udev.permissions
o mention klibc compile as special case for udev.permissions
o remove duplicated numeric owner clause
the bus id for the device
.TP
.B %c
the bus id for the device
.TP
.B %c
-the CALLOUT program return value (this does not work within the PROGRAM field for the obvious reason.)
+the CALLOUT program returned string
+(this does not work within the PROGRAM field for the obvious reason.)
.RE
.P
A sample \fIudev.conf\fP might look like this:
.RE
.P
A sample \fIudev.conf\fP might look like this:
The file consists of a set of lines. All empty lines and
lines beginning with a '#' will be ignored.
.br
The file consists of a set of lines. All empty lines and
lines beginning with a '#' will be ignored.
.br
-Every line lists a device name followed by numeric owner, group and permission
+Every line lists a device name followed by owner, group and permission
mode. All values are separated by colons. The name field may end with a
wildcard to apply the values to a whole class of devices.
.br
mode. All values are separated by colons. The name field may end with a
wildcard to apply the values to a whole class of devices.
.br
-If udev was built using glibc, string owner and group names may be used.
+If
+.B udev
+was built using klibc or is used before the user database is accessible (e.g.
+.B initrd
+), only numeric owner and group values may be used.
.sp
A sample \fIudev.permissions\fP might look like this:
.sp
.nf
#name:user:group:mode
.sp
A sample \fIudev.permissions\fP might look like this:
.sp
.nf
#name:user:group:mode
-.P
-If
-.B
-udev
-was built using glibc, string owner and group names may be used.
-