From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udev - man page update
Date: Sun, 29 Feb 2004 13:33:35 +0000 [thread overview]
Message-ID: <20040229133335.GA3031@vrfy.org> (raw)
In-Reply-To: <20040225002552.GA24875@vrfy.org>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
Here is a small change to the udev man page:
- clarify the use of the NAME{all_partitions} syntax
and add a example to udev.rules.example
- mention the empty NAME field to ignore the device
- prepare a SYMLINK field for the addition of Andrey's
"multiple symlinks" documentation :)
thanks,
Kay
[-- Attachment #2: 05-man-clarification.patch --]
[-- Type: text/plain, Size: 2257 bytes --]
===== udev.8 1.44 vs edited =====
--- 1.44/udev.8 Sat Feb 28 04:59:04 2004
+++ edited/udev.8 Sun Feb 29 14:08:36 2004
@@ -151,16 +151,15 @@
Every line in the rules file defines the mapping between device attributes
and the device file name. One ore more keys are specified to match a rule
with the current device. If all keys are matching, the rule will be applied
-and the name is used for the device node. One or more optional symlinks
-targeting the node may be specified.
+and the name is used for the device node.
.br
If no matching rule is found, the default kernel device name is used.
.P
-The line format is:
+Every rule consists of a list a comma separated fields:
.sp
-.I key,[key,...] name [, symlink]
+.IR "key " ,[ "key " ,...] " name " [, " symlink" ]
.sp
-where keys are:
+where possible fields are:
.TP
.B BUS
Match the bus type of the device.
@@ -196,13 +195,19 @@
call. This key may used in any following rule after a
.B PROGRAM
call.
-.P
-The
+.TP
.B NAME
-field given with the attribute
+The name of the node to be created. If the name field is omitted or its
+value is empty, the device will be ignored and no node will be created.
+.br
+If given with the attribute
.BR NAME{ all_partitions }
-will create all 15 partitions of a blockdevice.
+it will create all 15 partitions of a blockdevice.
This may be useful for removable media devices.
+.TP
+.B SYMLINK
+The name of a symlink targeting the node. Multiple symlinks may be
+specified by separating the names by the space character.
.P
.RB "The " NAME " ," SYMLINK " and " PROGRAM
fields support simple printf-like string substitution:
===== etc/udev/udev.rules.examples 1.2 vs edited =====
--- 1.2/etc/udev/udev.rules.examples Thu Feb 19 18:54:48 2004
+++ edited/etc/udev/udev.rules.examples Sun Feb 29 14:29:23 2004
@@ -51,6 +51,10 @@
# DRI devices always go into a subdirectory (as per the LSB spec)
KERNEL="card*", NAME="dri/card%n"
+# create all 15 partitions of a USB flash card reader
+# note the trailing spaces in the attribute, use udevinfo(8) to examine your device
+BUS="scsi", SYSFS{model}="CF/MD ", NAME{all_partitions}="compactflash"
+
# alsa devices
KERNEL="controlC[0-9]*", NAME="snd/%k"
KERNEL="hw[CD0-9]*", NAME="snd/%k"
next prev parent reply other threads:[~2004-02-29 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:25 [PATCH] udev - man page update Kay Sievers
2004-02-26 20:56 ` Greg KH
2004-02-29 13:33 ` Kay Sievers [this message]
2004-03-01 22:38 ` Greg KH
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=20040229133335.GA3031@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).