Skip to contentSkip to conversation

udev 131 release

ANNOUNCE Kay Sievers 3 participants 3 messages Nov 7, 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 131
====
Bugfixes. (And maybe new bugs. :))

The rule matching engine got converted from a rule list to a token array which reduced the in-memory rules representation of a full featured distro with thousands of udev rules from 1.2MB to 0.12 MB. Limits like 5 ENV and ATTR matches, and one single instance for most other keys per rule are gone.

The NAME assignment is no longer special cased. If later rules assign a NAME value again, the former value will be overwritten. As usual for most other keys, the NAME value can be protected by doing a final assignment with NAME:="<value>".

All udev code now uses libudev, which is also exported. The library is still under development, marked as experimental, and its interface may change as long as the DeviceKit integration is not finished.

Many thanks to Alan Jenkins for his continuous help, and finding and optimizing some of the computing expensive parts.

#1 lore raw
Quoted 4 lines · Kay Sievers

The NAME assignment is no longer special cased. If later rules assign a NAME value again, the former value will be overwritten. As usual for most other keys, the NAME value can be protected by doing a final assignment with NAME:="<value>".

While I like the consistency, I see the potential for user and package-specific rules to break spectacularly...

Signature · 2 lines
ciao,
Marco
#2 lore raw
In reply to Kay Sievers
Quoted 9 lines · Marco d'Itri
Quoted 4 lines · Kay Sievers

The NAME assignment is no longer special cased. If later rules assign a NAME value again, the former value will be overwritten. As usual for most other keys, the NAME value can be protected by doing a final assignment with NAME:="<value>".

While I like the consistency, I see the potential for user and package-specific rules to break spectacularly...

In theory, the changes are largely backwards compatible.

I've already grepped through the Ubuntu source, and didn't find anything relying on the old behaviour.

In fact, I found a few things that will only work with the *new* behaviour ;)

Scott

Signature · 2 lines
Scott James Remnant
[email protected]