SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

man: spelling fixes

Browse Source 
Thanks to Robert P. J. Day.
This commit is contained in:
Kay Sievers
2007-03-08 13:59:28 +01:00
parent 5b7363c064
commit 7f7238062c
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
udev.7
+5 -5
View File
@@ -20,9 +20,9 @@ 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.
and receives uevents directly from the kernel if a device is added or removed from 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.
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"
.PP
All udev configuration files are placed in
@@ -61,7 +61,7 @@ directory or at the location specified value in the configuration file. Every li
.PP
A matching rule may specify the name of the device node, add a symlink pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used.
.PP
A rule may consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
A rule may consist of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
.PP
\fB==\fR
.RS 4
@@ -248,7 +248,7 @@ If no option is given, udev will choose between
\fBprogram\fR
and
\fBfile\fR
based on the executable bit of of the file permissions.
based on the executable bit of the file permissions.
.RE
.PP
\fBWAIT_FOR_SYSFS\fR
@@ -320,7 +320,7 @@ The value of an environment variable.
The kernel major number for the device.
.RE
.PP
\fB$minor\fR \fB%m\fR
\fB$minor\fR, \fB%m\fR
.RS 4
The kernel minor number for the device.
.RE
udev.xml
+5 -5
View File
@@ -30,11 +30,11 @@
<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.</para>
kernel if a device is added or removed from 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.
Rules that match, may provide additional device information or specify a 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.</para>
</refsect1>
@@ -90,7 +90,7 @@
pointing to the node, or run a specified program as part of the event handling.
If no matching rule is found, the default device node name is used.</para>
<para>A rule may consists of a list of one or more key value pairs separated by
<para>A rule may consist of a list of one or more key value pairs separated by
a comma. Each key has a distinct operation, depending on the used operator. Valid
operators are:</para>
<variablelist>
@@ -374,7 +374,7 @@
</varlistentry>
</variablelist>
<para>If no option is given, udev will choose between <option>program</option>
and <option>file</option> based on the executable bit of of the file
and <option>file</option> based on the executable bit of the file
permissions.</para>
</listitem>
</varlistentry>
@@ -468,7 +468,7 @@
</varlistentry>
<varlistentry>
<term><option>$minor</option> <option>%m</option></term>
<term><option>$minor</option>, <option>%m</option></term>
<listitem>
<para>The kernel minor number for the device.</para>
</listitem>