1
1
mirror of https://github.com/systemd/systemd-stable.git synced 2024-10-29 21:55:25 +03:00

man pages: fix typos

This commit is contained in:
Michał Bartoszkiewicz 2006-08-17 00:58:37 +02:00 committed by Kay Sievers
parent dbd16d2684
commit 33a570f38b
4 changed files with 9 additions and 9 deletions

6
udev.7
View File

@ -52,7 +52,7 @@ and
.PP .PP
The udev rules are read from the files located in the The udev rules are read from the files located in the
\fI/etc/udev/rules.d\fR \fI/etc/udev/rules.d\fR
directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. 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. directory or at the location specified value in the configuration file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignment keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. 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 .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 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:
.TP 3n .TP 3n
@ -119,7 +119,7 @@ Matches zero, or any number of characters.
Matches any single character. Matches any single character.
.TP 3n .TP 3n
\fB[]\fR \fB[]\fR
Matches any single character specified within the brackets. example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched. Matches any single character specified within the brackets. For example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched.
.PP .PP
The following keys can get values assigned: The following keys can get values assigned:
.TP 3n .TP 3n
@ -149,7 +149,7 @@ Import the printed result or the value of a file in environment key format into
\fBprogram\fR \fBprogram\fR
will execute an external program and read its output. will execute an external program and read its output.
\fBfile\fR \fBfile\fR
will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions. will import a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.
.TP 3n .TP 3n
\fBWAIT_FOR_SYSFS\fR \fBWAIT_FOR_SYSFS\fR
Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues. Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.

View File

@ -81,8 +81,8 @@
<refsect2><title>Rules files</title> <refsect2><title>Rules files</title>
<para>The udev rules are read from the files located in the <para>The udev rules are read from the files located in the
<filename>/etc/udev/rules.d</filename> directory or at the location specified <filename>/etc/udev/rules.d</filename> directory or at the location specified
value in the configuraton file. Every line in the rules file contains at least value in the configuration file. Every line in the rules file contains at least
one key value pair. There are two kind of keys, match and assignement keys. one key value pair. There are two kind of keys, match and assignment keys.
If all match keys are matching against its value, the rule gets applied and the If all match keys are matching against its value, the rule gets applied and the
assign keys get the specified value assigned. A matching rule may specify the assign keys get the specified value assigned. A matching rule may specify the
name of the device node, add a symlink pointing to the node, or run a specified name of the device node, add a symlink pointing to the node, or run a specified
@ -238,7 +238,7 @@
<varlistentry> <varlistentry>
<term><option>[]</option></term> <term><option>[]</option></term>
<listitem> <listitem>
<para>Matches any single character specified within the brackets. <para>Matches any single character specified within the brackets. For
example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'.
Ranges are also supported within this match with the '-' character. Ranges are also supported within this match with the '-' character.
For example, to match on the range of all digits, the pattern [0-9] would For example, to match on the range of all digits, the pattern [0-9] would
@ -315,7 +315,7 @@
<listitem> <listitem>
<para>Import the printed result or the value of a file in environment key <para>Import the printed result or the value of a file in environment key
format into the event environment. <option>program</option> will execute an format into the event environment. <option>program</option> will execute an
external program and read its output. <option>file</option> will inport a external program and read its output. <option>file</option> will import a
text file. If no option is given, udev will determine it from the executable text file. If no option is given, udev will determine it from the executable
bit of of the file permissions.</para> bit of of the file permissions.</para>
</listitem> </listitem>

View File

@ -17,7 +17,7 @@ udevtest \- simulate a udev run and print the action to the console
\fBudevtest \fR\fB\fIdevice\-path\fR\fR \fBudevtest \fR\fB\fIdevice\-path\fR\fR
.SH "DESCRIPTION" .SH "DESCRIPTION"
.PP .PP
udevtest simulates a udev run for the given device and prints out the name of the node udev would have created, or the name of the network interface, that would have been renamend. udevtest simulates a udev run for the given device and prints out the name of the node udev would have created, or the name of the network interface, that would have been renamed.
.SH "AUTHOR" .SH "AUTHOR"
.PP .PP
Written by Greg Kroah\-Hartman Written by Greg Kroah\-Hartman

View File

@ -32,7 +32,7 @@
<refsect1><title>DESCRIPTION</title> <refsect1><title>DESCRIPTION</title>
<para>udevtest simulates a udev run for the given device and prints out the <para>udevtest simulates a udev run for the given device and prints out the
name of the node udev would have created, or the name of the network interface, name of the node udev would have created, or the name of the network interface,
that would have been renamend.</para> that would have been renamed.</para>
</refsect1> </refsect1>
<refsect1><title>AUTHOR</title> <refsect1><title>AUTHOR</title>