linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@access.unizh.ch>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Various typos and other litte errors in udev.8.in
Date: Mon, 06 Dec 2004 13:46:18 +0000	[thread overview]
Message-ID: <200412061446.19125.tklauser@access.unizh.ch> (raw)

Hi,

While crawling through the udev manpage I noticed some typos and other grammatical errors.
English is not my native languag, so I'm not sure if I fixed everything right. I would be
glad if any English-speaking person could check this patch before applying.

Thanks, Tobias


--- udev-046.orig/udev.8.in	2004-12-06 13:54:50.142504536 +0100
+++ udev-046/udev.8.in	2004-12-06 14:30:55.786276640 +0100
@@ -57,7 +57,7 @@
 All
 .B udev
 configuration files consist of a set of lines of text.  All empty
-lines and lines beginning with a '#' will be ignored.
+lines or lines beginning with '#' will be ignored.
 .P
 
 .B udev
@@ -90,22 +90,22 @@
 .IR /etc/udev/permissions.d/ .
 .TP
 .B udev_log
-The switch, if udev logs some information for every device handled.
+The switch to enable/disable logging of udev information
 The default value is
 .IR yes .
 .TP
 .B default_mode
-The default mode for all nodes not explicitely matching in the permissions
+The default mode for all nodes not explicitly matching in the permissions
 file. The default value is
 .IR 0666 .
 .TP
 .B default_owner
-The default owner for all nodes not explicitely matching in the permissions
+The default owner for all nodes not explicitly matching in the permissions
 file. The default value is
 .IR root .
 .TP
 .B default_group
-The default group for all nodes not explicitely matching in the permissions
+The default group for all nodes not explicitly matching in the permissions
 file. The default value is
 .IR root .
 .br
@@ -131,19 +131,19 @@
 udev_log="yes"
 
 # default_mode - set the default mode for all nodes not
-#                explicitely matching in the permissions file
+#                explicitly matching in the permissions file
 default_mode="0666"
 
 # default_owner - set the default owner for all nodes not
-#                 explicitely matching in the permissions file
+#                 explicitly matching in the permissions file
 default_owner="root"
 
 # default_group - set the default group for all nodes not
-#                 explicitely matching in the permissions file
+#                 explicitly matching in the permissions file
 default_group="root"
 .fi
 .P
-The rules for device naming, are read from the files located in the
+The rules for device naming are read from the files located in the
 .I /etc/udev/rules.d/
 directory, or at the location specified by the
 .I udev_rules
@@ -229,10 +229,10 @@
 specified by separating the names by the space character.
 .br
 If both the name and the symlink fields are omitted or its
-values empty, the device will be ignored and no node will be created.
+values are empty, the device will be ignored and no node will be created.
 .br
 If only the symlink field is given and the name field is omitted,
-the rule will not be applied immediatly, but the symlink field is added
+the rule will not be applied immediately, but the symlink field is added
 to the symlink list of the rule which will create the node.
 This makes it possible to specify additional symlinks in a possibly
 separate rules file, while the device nodes are maintained by the
@@ -243,7 +243,7 @@
 given in the permissions file.
 .P
 .RB "The " NAME " ," SYMLINK " and " PROGRAM
-fields support simple printf-like string substitution:
+fields support simple printf-like string substitutions:
 .TP
 .B %n
 The "kernel number" of the device.
@@ -262,7 +262,7 @@
 The bus id for the device.
 .TP
 .B %c
-The string returned from the execution of
+The string returned by the external program, specified in
 .B PROGRAM
 (This does not work within the
 .B PROGRAM
@@ -295,7 +295,7 @@
 .RI "A sample " udev.rules " might look like this:"
 .sp
 .nf
-# if /sbin/scsi_id returns "OEM 0815" device will be called disk1
+# if /sbin/scsi_id returns "OEM 0815", the device will be called disk1
 BUS="scsi", PROGRAM="/sbin/scsi_id", RESULT="OEM 0815", NAME="disk1"
 
 # USB printer to be called lp_color
@@ -325,7 +325,7 @@
 
 .fi
 .P
-The permissions and ownership of the created device file is read from
+The permissions and ownership of the created device file are read from
 the files located in the
 .I /etc/udev/permissions.d/
 directory, or at the location specified by the
@@ -362,15 +362,15 @@
 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 character not enclosed is matched.
+following the '[' is a '!', any characters not enclosed are matched.
 .P
 After device node creation, removal, or network device renaming,
 .B udev
 executes the programs in the directory tree under
 .IR /etc/dev.d/ .
-The name of a program must end with
+The name of a program must have the suffix
 .I .dev
-suffix, to be recognized.
+to be recognized.
 .br
 In addition to the hotplug environment variables,
 .B DEVNAME


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-12-06 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 13:46 Tobias Klauser [this message]
2004-12-07 14:10 ` [PATCH] Various typos and other litte errors in udev.8.in Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412061446.19125.tklauser@access.unizh.ch \
    --to=tklauser@access.unizh.ch \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).