udev 003 release

Hi,

I've released the 003 version of udev. It can be found at:
kernel.org/pub/linux/utils/kernel/hotplug/udev-003.tar.gz

udev is a implementation of devfs in userspace using sysfs and /sbin/hotplug. It requires a 2.6 kernel to run properly.

There have been a number of major changes since the last release:
- works properly with the current 2.6 kernel (older versions of udev will not work with the current 2.6 kernel.)
- persistent database support has been added, but not fully integrated (tdb is database code, very nice stuff.)
- lots of documentation has been added.
- spec file has been added for building rpms.
- install and uninstall support added to Makefile to make it easier to install and test with.
- hard coded config file paths have been fixed.
- callout support has been added (allows other programs to be run to determine what to name a device.)
- cross compile bugs fixed.
- TODO list expanded for those who wish to help out.
- lots of other stuff fixed.

The full ChangeLog is below.

The new udev FAQ is included in this release, and can also be found at:
kernel.org/pub/linux/utils/kernel/hotplug/hotplug/udev-FAQ

Development of udev is done in a BitKeeper tree available at:
bk://kernel.bkbits.net/gregkh/udev/

If anyone ever wants a snapshot of the current tree, due to not using BitKeeper, or other reasons, is always available at any time by asking.

thanks,

greg k-h

Summary of changes from v0.2 to v003
======================

Daniel E. F. Stekloff:
o udevdb patch
o udevdb prototype

Greg Kroah-Hartman:
o update changelog for 003 release TAG: v003
o update the spec file for the new version and install process
o fix makefile release rule to not drop tdb.h file
o Add FAQ for udev
o removed AUTHORS and INSTALL files as they were pretty pointless
o copyright updates
o Add AUTHORS and INSTALL files
o TODO updates
o Updatd the README
o updated the TODO list
o add udev man page (basically just a place holder for now.)
o added uninstall support
o added install target for makefile so people don't have to do it by hand anymore
o add version to debug log on startup
o tell the user what mknod() we are trying to do
o add dbg_parse() to cut down on parse file debugging statements
o put config files and database in /etc/udev by default
o add ols 2003 udev paper to docs/
o clean up some debugging stuff in namedev.c
o do not build the tdb binary programs, only the objects
o merge tdb into the build process
o Added tdb code from latest cvs version in the samba tree
o added my name to the .spec file
o minor cleanups
o cleanup the mknod code a bit
o remove mknod callout
o handle new major:minor format of dev files that showed up in 2.6.0-test2-bk3 or so
o oops, everything was getting created as 000 mode, try to fix this up, but fail...
o more test stuff

Olaf Hering:
o print udev pid

Patrick Mansfield:
o add callout config type to udev

Paul Mundt:
o Fix TDB cross compilation
o udev spec file
o udev/libsysfs cross compile fixes

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

one hotplug too much it's just
ftp://kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ

- --
Clemens Schwaighofer - IT Engineer & System Administration
=============================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
=============================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/j4zqjBz/yQjBxz8RAjtiAJ9kQkj/vtjmWJshUc7lM82e0RV0lwCgvavU fzrvdDR+/FpmrSQ9SOvusr8A1
-----END PGP SIGNATURE-----

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

The new udev is nice, and it 'works', but Im still having two problems:
(1) Although the messages file shows that it is reading my /etc/udev/namedev.config file, the entries are being ignored. Ive tried both:
LABEL, BUS="usb", serial="0B0201420527B284", NAME="usb_disk"
and
LABEL, BUS="usb", vendor="DMI", NAME="usb_disk"

and all I get are /udev/ sda, sdb, sdc, sdd, ... as I plug and unplug.

(2) This worked in -0.2, but not -0.3: When a device is created in /udev, I now get just /udev/sda . Previously (0.2) I got both sda and sda1 . Needless to say, a mount attempt on /udev/sda1 now fails. [[ and if I tell it NAME="usb_disk" what should I expect for the name of the first partition???

Am I missing something???

                                        Reg.Clemens
                                        [email protected]




-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

If you turn on debugging for the parser in namedev.c by uncommenting the comment at the top of the file:
/* define this to enable parsing debugging */
/* #define DEBUG_PARSER */

to look like:

/* define this to enable parsing debugging */
#define DEBUG_PARSER

It will give you a lot of information about what the parser is reading, and trying to match up with your device. If you could send me the system debug log from when you plug in your device with the DEBUG_PARSER define enabled, I'd be glad to look into it.

No, I think I broke the partition logic somewhere. I think the name of the first partition in this case should be "usb_disk1". Yeah, it's a hack for now, hopefully some new libsysfs changes in regards to the block sysfs tree will help out with this (it's really hard to determine the partition is different from the main block device right now in udev.)

Ah, yeah, udev seg faults right now for partitions. Let me try to track down the bug, give me a bit of time...

thanks for letting me know,

greg k-h

-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Here's a patch that fixes the partition logic for me. Sorry about this, I need to make sure to test partitions more next time.

thanks again for testing this.

greg k-h

# fix segfaults when dealing with partitions.

diff -Nru a/udev-add.c b/udev-add.c
@@ -169,13 +169,13 @@
 	}
 	memset(&dbdev, 0, sizeof(dbdev));
 	strncpy(dbdev.name, attr.name, NAME_SIZE);
-	strncpy(dbdev.sysfs_path, class_dev->sysdevice->directory->path,
-		PATH_SIZE);
+	if (class_dev->sysdevice) {
+		strncpy(dbdev.sysfs_path, class_dev->sysdevice->directory->path, PATH_SIZE);
+		strncpy(dbdev.bus_id, class_dev->sysdevice->bus_id, ID_SIZE);
+	}
 	strncpy(dbdev.class_dev_name, class_dev->name, NAME_SIZE);
-	if ((sysfs_get_name_from_path(subsystem, dbdev.class_name, NAME_SIZE))
-	    != 0)
+	if ((sysfs_get_name_from_path(subsystem, dbdev.class_name, NAME_SIZE)) != 0)
 		strcpy(dbdev.class_name, "unkown");
-	strncpy(dbdev.bus_id, class_dev->sysdevice->bus_id, ID_SIZE);
 	strcpy(dbdev.bus_name, "unknown");
 	if (class_dev->driver != NULL)
 		strncpy(dbdev.driver, class_dev->driver->name, NAME_SIZE);

-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Hi,
wouldn't it be better to put udevdb.tdb in /var/lib, to comply with FHS?

TODO - it seems, that custom device file removal is now working?

A simple man page is attached.

thanks,

Kay

.TH UDEV 8 "October 2003" "" "Linux Administrator's Manual"
.SH NAME
udev \- Linux configurable dynamic device naming support
.SH SYNOPSIS
.B udev
.SH "DESCRIPTION"
.B udev
creates or removes device node files usually located in the /dev directory. As part of the
.B hotplug
subsystem,
.B udev
is exectuted if a kernel device is added or removed from the system. .P
On device creation,
.B udev
reads the sysfs directory of the given device, to collect device attributes like label, serial number or bus device number.
These attributes are passed as a key to the namedev subsystem
to receive a unique name for device file creation.
namedev maintains a database for devices present on the system. .P
On device removal,
.B udev
queries the namedev database for the name of the device file to delete. .P
namedev expects its configuration at
.I /etc/udev/namedev.config.
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. .TP
.B LABEL
device label or serial number, like USB serial number, SCSI UUID or file system label
.TP
.B NUMBER
device number on the bus, like PCI bus id
.TP
.B TOPOLOGY
device position on bus, like physical port of USB device
.TP
.B REPLACE
string replacement of the kernel device name
.P
If no matching configuration is found, the default kernel device name is used. .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"

# USB mouse at third port of the second hub to be called mouse1 TOPOLOGY, BUS="usb", place="2.3", NAME="mouse1"

# ttyUSB1 should always be called pda
REPLACE, KERNEL="ttyUSB1", NAME="pda"
.fi
.SH "FILES"
.nf
.ft B
.ft

/sbin/udev                           udev program
/etc/udev/*                          udev config and database files
/etc/hotplug.d/default/udev.hotplug  hotplug symlink to udev program

.fi
.LP
.SH "SEE ALSO"
.B hotplug (8)
.PP
The
.I http://linux-hotplug.sourceforge.net/
web site.
.SH AUTHORS
udev was developed by Greg Kroah-Hartman <[email protected]> with much help from Dan Stekloff <[email protected]> and many others.

@@ -1,11 +1,67 @@
-.TH UDEV 8 "October 2003" "" "Linux Programmer's Manual"
+.TH UDEV 8 "October 2003" "" "Linux Administrator's Manual"
 .SH NAME
-udev \- Linux dynamic device naming support
+udev \- Linux configurable dynamic device naming support
 .SH SYNOPSIS
 .B udev
 .SH "DESCRIPTION"
 .B udev
-is a wonderful program whose man page has not been written yet.
+creates or removes device node files usually located in the /dev directory.
+As part of the
+.B hotplug
+subsystem,
+.B udev
+is exectuted if a kernel device is added or removed from the system.
+.P
+On device creation,
+.B udev
+reads the sysfs directory of the given device, to collect device attributes
+like label, serial number or bus device number.
+These attributes are passed as a key to the namedev subsystem
+to receive a unique name for device file creation.
+namedev maintains a database for devices present on the system.
+.P
+On device removal,
+.B udev
+queries the namedev database for the name of the device file to delete.
+.P
+namedev expects its configuration at
+.I /etc/udev/namedev.config.
+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.
+.TP
+.B LABEL
+device label or serial number, like USB serial number, SCSI UUID or
+file system label
+.TP
+.B NUMBER
+device number on the bus, like PCI bus id
+.TP
+.B TOPOLOGY
+device position on bus, like physical port of USB device
+.TP
+.B REPLACE
+string replacement of the kernel device name
+.P
+If no matching configuration is found, the default kernel device name is used.
+.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"
+
+# USB mouse at third port of the second hub to be called mouse1
+TOPOLOGY, BUS="usb", place="2.3", NAME="mouse1"
+
+# ttyUSB1 should always be called pda
+REPLACE, KERNEL="ttyUSB1", NAME="pda"
+.fi
 .SH "FILES"
 .nf
 .ft B

@@ -16,7 +72,7 @@
 .fi
 .LP
 .SH "SEE ALSO"
-.BR hotplug "(8)"
+.B hotplug (8)
 .PP
 The
 .I http://linux-hotplug.sourceforge.net/

Hm, I didn't realize that. I think the on-disk database will soon be going away, to live only in memory, but until then, I guess we should move it. I'll work on that, as I've been working on a lot of other database related changes in udev the past few days.

It is in the current bk tree, but not in the 003 release.

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...

thanks again,

greg k-h

-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

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

@@ -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

I corrected a typo in the previous patch.

thanks,
Kay

changes:
o CALLOUT method included
o required keys for every match method listed
o keywords changed to uppercase in EXAMPLE

@@ -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, \fIsysfs_attribute\fP
 .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
+calling 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/dev_id returns "V0815" device will be called dev0815
+CALLOUT, PROGRAM="/sbin/dev_id", BUS="pci", ID="V0815", NAME="dev0815"
 .fi
 .SH "FILES"
 .nf

Thanks a lot, I've applied this.

greg k-h

-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Great!

The naming will be consistant from now on. Next release will be 004, followed by 005, and so on. Remember, version numbers mean nothing :)

As there is no installed base before 003, I don't think this will really be a problem, do you?

It's older, I think.

I just got a patch today from Dan that merged the latest version of libsysfs into udev. It's in the udev bk tree already. libsysfs will always be a copy in the udev tree, as udev links statically, and it keeps the build process and debug process much easier.

sysfsutils can still be its own package, other programs are starting to use libsysfs already.

Yes, I would love to support that. Care to send a patch? :)

Of course you need a kernel patch for the sound class that is only available in my kernel tree right now for sound devices to work with udev...

thanks,

greg k-h

-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Exactly, switching this early is fine by all of the package managers I've looked at. Does this mean you have a udev gentoo package somewhere?

I need to get these class patches out sometime soon, been too busy lately...

greg k-h

-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Do you also have the latest hotplug scripts in gentoo?

Nice. Be sure to let me know if you do hear any.

Remember, gentoo needs to wean itself off of devfs for 2.6...

initramfs is in the kernel, you use it to boot already :)

thanks,

greg k-h

-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Other than the source in the kernel, no, sorry.

greg k-h

-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel