linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: [ANNOUNCE] udev 131 release
Date: Fri, 07 Nov 2008 06:27:49 +0000	[thread overview]
Message-ID: <1226039269.4100.0.camel@nga> (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.


             reply	other threads:[~2008-11-07  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  6:27 Kay Sievers [this message]
2008-11-07  9:39 ` [ANNOUNCE] udev 131 release Marco d'Itri
2008-11-07 12:59 ` Scott James Remnant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1226039269.4100.0.camel@nga \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).