Skip to contentSkip to conversation

udev 126 release

ANNOUNCE Kay Sievers 4 participants 13 messages Aug 4, 2008 – Aug 9, 2008

lore
Share & tools
lore
#0 lore raw

Here comes a new udev version. Thanks to all who have contributed to this release.

The tarball can be found here:
ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/

The development repository can be found here:
http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=summary

The ChangeLog can be found here:
http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=ChangeLog

udev 126
====
We use ./configure now. See INSTALL for details. Current options are:
--prefix "/usr" - prefix for man pages, include files
--exec-prefix "" - the root filesystem, prefix for libs and binaries
--sysconfdir "/etc"
--with-libdir-name "lib" - directory name for libraries, not a path name
multilib 64bit systems may use "lib64" instead of "lib"
--enable-debug
compile-in verbose debug messages
--disable-logging
disable all logging and compile-out all log strings
--with-selinux
link against SELInux libraries, to set the expected context for created files

In the default rules, the group "disk" gets permissions 0660 instead of 0640. One small step closer to unify distro rules. Some day, all distros hopefully end up with the same set of rules.

No symlinks to udevadm are installed anymore, if they are still needed, they should be provided by the package.

#1 lore raw
Quoted 3 lines · Kay Sievers

udev 126
====
We use ./configure now. See INSTALL for details. Current

Finally. Thanks :-)

Karel

Signature · 1 line
 Karel Zak  <[email protected]>
#2 lore raw
In reply to Kay Sievers

* Kay Sievers <[email protected]>:

| Here comes a new udev version. Thanks to all who have contributed to | this release.

gcc -g -O2 -o test-udev test-udev.o udev_config.o udev_db.o udev_device.o udev_node.o udev_rules.o udev_rules_parse.o udev_sysdeps.o udev_sysfs.o udev_utils.o udev_utils_file.o udev_utils_string.o
gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\""/etc"\" -DUDEV_PREFIX=\""/usr"\" -g -O2 -MT udevd.o -MD -MP -MF
.deps/udevd.Tpo -c -o udevd.o udevd.c
udevd.c: In function 'init_uevent_netlink_sock':
udevd.c:909: error: 'NETLINK_KOBJECT_UEVENT' undeclared (first use in this function) udevd.c:909: error: (Each undeclared identifier is reported only once udevd.c:909: error: for each function it appears in.)
udevd.c:916: error: 'SO_RCVBUFFORCE' undeclared (first use in this function) udevd.c: In function 'main':
udevd.c:1152: error: 'IN_CREATE' undeclared (first use in this function) udevd.c:1152: error: 'IN_DELETE' undeclared (first use in this function) udevd.c:1152: error: 'IN_MOVE' undeclared (first use in this function) udevd.c:1152: error: 'IN_CLOSE_WRITE' undeclared (first use in this function) make[2]: *** [udevd.o] Error 1

[kernel]
Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux

[glibc]
GNU C Library stable release version 2.3.6, by Roland McGrath et al. Compiled by GNU CC version 4.1.2.
Compiled on a Linux 2.4.34-gzp1 system on 2007-04-04.

[gcc]
gcc (GCC) 4.2.4

[binutils]
GNU ld (Linux/GNU Binutils) 2.18.50.0.8.20080709

[autoconf]
autoconf (GNU Autoconf) 2.62

[automake]
automake (GNU automake) 1.10.1

[libtool]
ltmain.sh (GNU libtool) 1.5.26 (1.1220.2.492 2008/01/30 06:40:56)

#3 lore raw
In reply to Kay Sievers
Quoted 22 lines · Gabor Z. Papp

* Kay Sievers <[email protected]>:

| Here comes a new udev version. Thanks to all who have contributed to | this release.

gcc -g -O2 -o test-udev test-udev.o udev_config.o udev_db.o udev_device.o udev_node.o udev_rules.o udev_rules_parse.o udev_sysdeps.o udev_sysfs.o udev_utils.o udev_utils_file.o udev_utils_string.o
gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\""/etc"\" -DUDEV_PREFIX=\""/usr"\" -g -O2 -MT udevd.o -MD -MP -MF
.deps/udevd.Tpo -c -o udevd.o udevd.c
udevd.c: In function 'init_uevent_netlink_sock':
udevd.c:909: error: 'NETLINK_KOBJECT_UEVENT' undeclared (first use in this function) udevd.c:909: error: (Each undeclared identifier is reported only once udevd.c:909: error: for each function it appears in.)
udevd.c:916: error: 'SO_RCVBUFFORCE' undeclared (first use in this function) udevd.c: In function 'main':
udevd.c:1152: error: 'IN_CREATE' undeclared (first use in this function) udevd.c:1152: error: 'IN_DELETE' undeclared (first use in this function) udevd.c:1152: error: 'IN_MOVE' undeclared (first use in this function) udevd.c:1152: error: 'IN_CLOSE_WRITE' undeclared (first use in this function) make[2]: *** [udevd.o] Error 1

Quoted 2 lines

[kernel]
Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux

Udev depends on a 2.6 kernel. :) The udev build depends on kernel-headers, which contain the features udev uses.

Older udev versions used to work around missing pieces, but all of the needed features like netlink uevent, inotify are mainstream for several years now, and therefore no longer provided by the udev source code.

Kay

#4 lore raw
In reply to Kay Sievers

* Kay Sievers <[email protected]>:

| > Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux

| Udev depends on a 2.6 kernel. :) The udev build depends on | kernel-headers, which contain the features udev uses.

okay. v125 built fine on 2.4

#5 lore raw
In reply to Kay Sievers

* "Gabor Z. Papp" <[email protected]>:

| | > Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux

| | Udev depends on a 2.6 kernel. :) The udev build depends on
| | kernel-headers, which contain the features udev uses. 

| okay. v125 built fine on 2.4

Building on 2.6.26.2:

make all-recursive
make[1]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126' Making all in udev
make[2]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126/udev'
gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\""/usr/etc"\" -DUDEV_PREFIX=\""/usr"\" -g -O2 -MT udevd.o -MD -MP -MF .deps/udevd.Tpo -c -o udevd.o udevd.c
udevd.c: In function `main':
udevd.c:1152: error: IN_CREATE' undeclared (first use in this function) udevd.c:1152: error: (Each undeclared identifier is reported only once udevd.c:1152: error: for each function it appears in.) udevd.c:1152: error: IN_DELETE' undeclared (first use in this function) udevd.c:1152: error: IN_MOVE' undeclared (first use in this function) udevd.c:1152: error: IN_CLOSE_WRITE' undeclared (first use in this function) make[2]: *** [udevd.o] Error 1
make[2]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126/udev' make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126'
make: *** [all] Error 2

#6 lore raw
In reply to Kay Sievers
Quoted 20 lines · Gabor Z. Papp

* "Gabor Z. Papp" <[email protected]>:

| | > Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux

| | Udev depends on a 2.6 kernel. :) The udev build depends on
| | kernel-headers, which contain the features udev uses. 

| okay. v125 built fine on 2.4

Building on 2.6.26.2:

make all-recursive
make[1]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126' Making all in udev
make[2]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126/udev'
gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\""/usr/etc"\" -DUDEV_PREFIX=\""/usr"\" -g -O2 -MT udevd.o -MD -MP -MF .deps/udevd.Tpo -c -o udevd.o udevd.c
udevd.c: In function `main':
udevd.c:1152: error: `IN_CREATE' undeclared (first use in this function) udevd.c:1152: error: (Each undeclared identifier is reported only once udevd.c:1152: error: for each function it appears in.)

Quoted 8 lines

udevd.c:1152: error: IN_DELETE' undeclared (first use in this function) udevd.c:1152: error: IN_MOVE' undeclared (first use in this function) udevd.c:1152: error: `IN_CLOSE_WRITE' undeclared (first use in this function) make[2]: *** [udevd.o] Error 1
make[2]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126/udev' make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126'
make: *** [all] Error 2

What does:
grep IN_ /usr/include/sys/inotify.h
print?

And:
grep INOTIFY config.h
in the udev source tree print?

I guess Inotify is not available on your system, and the udev build tries to disable it, but we need a few more ifdef's to make it compile without it.

Kay

#7 lore raw
In reply to Kay Sievers

* Kay Sievers <[email protected]>:

| What does:
|   grep IN_ /usr/include/sys/inotify.h
| print?

Its glibc 2.3.6, there is no sys/inotify.h

| And:
|   grep INOTIFY config.h
| in the udev source tree print?

/* #undef HAVE_INOTIFY */

| I guess Inotify is not available on your system, and the udev build
| tries to disable it, but we need a few more ifdef's to make it compile
| without it.

Additional question: udev_rules_parse.c line 745,
is that normal, that udevd prints a big WARNING/ERROR at start if UDEV_PREFIX "/lib/udev/rules.d" directory doesnt exist?

#8 lore raw
In reply to Kay Sievers
Quoted 12 lines · Gabor Z. Papp

* Kay Sievers <[email protected]>:

| What does:
|   grep IN_ /usr/include/sys/inotify.h
| print?

Its glibc 2.3.6, there is no sys/inotify.h

| And:
|   grep INOTIFY config.h
| in the udev source tree print?
Quoted 5 lines

/* #undef HAVE_INOTIFY */

| I guess Inotify is not available on your system, and the udev build
| tries to disable it, but we need a few more ifdef's to make it compile
| without it.

I pushed out a fix for this:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;hk8c150e12dba22e600da918828b9e648c10018e
I hope it compiles now, if inotify is not available. Thanks for the help.

Quoted 3 lines

Additional question: udev_rules_parse.c line 745,
is that normal, that udevd prints a big WARNING/ERROR at start if UDEV_PREFIX "/lib/udev/rules.d" directory doesnt exist?

Packages can drop rules to that directory, and just expect it to be there. The daemon also likes to monitor the directory with inotify to re-parse the rules if needed, so it should exist, yes.

Thanks,
Kay

#9 lore raw
In reply to Kay Sievers
Quoted 6 lines · Kay Sievers
Quoted 3 lines

Additional question: udev_rules_parse.c line 745,
is that normal, that udevd prints a big WARNING/ERROR at start if UDEV_PREFIX "/lib/udev/rules.d" directory doesnt exist?

Packages can drop rules to that directory, and just expect it to be there. The daemon also likes to monitor the directory with inotify to re-parse the rules if needed, so it should exist, yes.

I just patched away the warning, since we decided that there is no point for Debian and Ubuntu to move the files.

Signature · 2 lines
ciao,
Marco
#10 lore raw
In reply to Kay Sievers
Quoted 10 lines · Marco d'Itri
Quoted 6 lines · Kay Sievers
Quoted 3 lines

Additional question: udev_rules_parse.c line 745,
is that normal, that udevd prints a big WARNING/ERROR at start if UDEV_PREFIX "/lib/udev/rules.d" directory doesnt exist?

Packages can drop rules to that directory, and just expect it to be there. The daemon also likes to monitor the directory with inotify to re-parse the rules if needed, so it should exist, yes.

I just patched away the warning, since we decided that there is no point for Debian and Ubuntu to move the files.

New packages will drop files here, so you will need to patch all these apps too. Good luck!

Kay

#11 lore raw
In reply to Kay Sievers

* "Kay Sievers" <[email protected]>:

| > I just patched away the warning, since we decided that there is no point | > for Debian and Ubuntu to move the files.

| New packages will drop files here, so you will need to patch all these | apps too. Good luck!

What packages? I have no packages.

#12 lore raw
In reply to Kay Sievers
Quoted 9 lines · Gabor Z. Papp

* "Kay Sievers" <[email protected]>:

| > I just patched away the warning, since we decided that there is no point | > for Debian and Ubuntu to move the files.

| New packages will drop files here, so you will need to patch all these | apps too. Good luck!

What packages? I have no packages.

Sure, not today, it was just added only a few weeks ago. But we will move stuff over over time, and recent packages which depend on a new udev version, like all the upcoming DeviceKit stuff, can expect the directory to be there. and can expect udevd to automatically recognize rule changes with inotify.
All that will break, if you try to needlessly "optimize" things. Just create the directory, even when it's empty today, it's an official udev ABI.

Kay