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 143 ======== Bugfixes. The configure options have changed because another library needs to be installed in a different location. Instead of exec_prefix and udev_prefix, libdir, rootlibdir and libexecdir are used. The Details are explained in the README file. Event processes now get re-used after they handled an event. This reduces the number of forks and the pressure on the CPU significantly, because cloned event processes no longer cause page faults in the main daemon. After the events have settled, a few worker processes stay around for future events, all others get cleaned up. To be able to use signalfd(), udev depends on kernel version 2.6.25 now. Also inotify support is mandatory now to run udev. The format of the queue exported by the udev damon has changed. There is no longer a /dev/.udev/queue/ directory. The current event queue can be accessed with udevadm settle and libudedv. Libudev does not have the unstable API header anymore. From now on, incompatible changes will be handled by bumping the library major version. To build udev from the git tree gtk-doc is needed now. The tarballs will build without it, and contain the pre-built documentation. An online copy is available here: http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/ http://www.kernel.org/pub/linux/utils/kernel/hotplug/gudev/ The tools from the udev-extras repository have been merged into the main udev repository. Some of the extras have larger external dependencies, and they can be disabled with the configure switch --disable-extras if needed. -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
