From: Kay Sievers <lkml001@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 003 release
Date: Mon, 20 Oct 2003 02:53:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106662164202863@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106637061520169@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Sun, Oct 19, 2003 at 02:01:57PM -0700, Greg KH wrote:
> On Sat, Oct 18, 2003 at 04:56:05PM +0200, Kay Sievers wrote:
> > A simple man page is attached.
>
> Thanks a lot for the patch. I've applied it. Hm, need to add some
> documentation about the new CALLOUT type of config entry too...
Hi Greg,
CALLOUT is comparing the string output of a program with "ID", right?
Please check the section, if i guess is right :)
thanks,
Kay
changes:
o CALLOUT method included
o required keys for every match method listed
o keywords changed to uppercase in EXAMPLE
[-- Attachment #2: udev.8.diff --]
[-- Type: text/plain, Size: 2241 bytes --]
--- /usr/src/udev/udev.8 2003-10-20 04:25:06.000000000 +0200
+++ udev.8 2003-10-20 04:34:40.000000000 +0200
@@ -29,38 +29,55 @@
The file consists of a set of lines. All empty lines and
lines beginning with a '#' will be ignored.
.br
-Every line defines the mapping between device attributes and the name of
-the device file. It starts with a keyword defining the method for
-overriding the default kernel naming scheme, followed by a list
-of keys and ends with the definition of the filename for the device.
+Every line defines the mapping between device attributes and the device file
+name. It starts with a keyword defining the method used to match, followed by
+one ore more keys to compare, optional ownwership and permission settings and
+the filename for the device. If no matching configuration is found,
+the default kernel device name is used.
+.P
+.I method, key,[key,...] [owner,] [group,] [mode,] name
.TP
.B LABEL
device label or serial number, like USB serial number, SCSI UUID or
file system label
+.br
+keys: \fBBUS\fP, sysfs_attr\fB=\fPvalue
.TP
.B NUMBER
device number on the bus, like PCI bus id
+.br
+keys: \fBBUS\fP, \fBID\fP
.TP
.B TOPOLOGY
device position on bus, like physical port of USB device
+.br
+keys: \fBBUS\fP, \fBPLACE\fP
.TP
.B REPLACE
string replacement of the kernel device name
-.P
-If no matching configuration is found, the default kernel device name is used.
+.br
+key: \fBKERNEL_NAME\fP
+.TP
+.B CALLOUT
+call external program, that returns a string to match
+.br
+keys: \fBBUS\fP, \fBPROGRAM\fP, \fBID\fP
.SH "EXAMPLE"
.nf
# USB printer to be called lp_color
LABEL, BUS="usb", serial="W09090207101241330", NAME="lp_color"
# sound card with PCI bus id 00:0b.0 to be called dsp
-NUMBER, BUS="pci", id="00:0b.0", NAME="dsp"
+NUMBER, BUS="pci", ID="00:0b.0", NAME="dsp"
# USB mouse at third port of the second hub to be called mouse1
-TOPOLOGY, BUS="usb", place="2.3", NAME="mouse1"
+TOPOLOGY, BUS="usb", PLACE="2.3", NAME="mouse1"
# ttyUSB1 should always be called pda
REPLACE, KERNEL="ttyUSB1", NAME="pda"
+
+# if /sbin/callout returns "V0815" device will be called dev0815
+CALLOUT, PROGRAM="/sbin/dev_id", BUS="pci", ID="V0815", NAME="dev0815"
.fi
.SH "FILES"
.nf
next prev parent reply other threads:[~2003-10-20 2:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 5:56 [ANNOUNCE] udev 003 release Greg KH
2003-10-17 6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19 ` Greg KH
2003-10-17 18:27 ` Greg KH
2003-10-18 14:56 ` Kay Sievers
2003-10-19 21:01 ` Greg KH
2003-10-20 2:53 ` Kay Sievers [this message]
2003-10-20 10:14 ` Kay Sievers
2003-10-20 22:35 ` Greg KH
2003-10-21 0:50 ` Greg KH
2003-10-21 2:43 ` Greg KH
2003-10-21 17:44 ` Greg KH
2003-10-21 20:56 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 5:56 Greg KH
2003-10-17 6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19 ` Greg KH
2003-10-17 18:27 ` Greg KH
2003-10-21 0:39 ` Martin Schlemmer
2003-10-21 0:50 ` Greg KH
2003-10-21 1:11 ` Martin Schlemmer
2003-10-21 2:43 ` Greg KH
2003-10-21 3:38 ` Martin Schlemmer
2003-10-21 17:44 ` Greg KH
2003-10-21 20:20 ` Martin Schlemmer
2003-10-21 20:56 ` 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=marc-linux-hotplug-106662164202863@msgid-missing \
--to=lkml001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.