From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Mon, 20 Oct 2003 02:53:35 +0000 Subject: Re: [ANNOUNCE] udev 003 release MIME-Version: 1 Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND" Message-Id: List-Id: References: In-Reply-To: To: linux-hotplug@vger.kernel.org --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline; filename="udev.8.diff" --- /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 --d6Gm4EdcadzBjdND-- ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.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