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 125 release
Date: Mon, 21 Jul 2008 08:02:14 +0000	[thread overview]
Message-ID: <1216627334.7816.12.camel@linux.site> (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 125
====
Bugfixes.

Default udev rules, which are not supposed to be edited by the user, should
be placed in /lib/udev/rules.d/ now, to make it clear that they are private to
the udev package and will be replaced with an update. Udev will pick up rule
files from:
  /lib/udev/rules.d/  - default installed rules
  /etc/udev/rules.d/  - user rules + on-the-fly generated rules
  /dev/.udev/rules.d/ - temporary non-persistent rules created after bootup
It does not matter in which directory a rule file lives, all files are sorted
in lexical order.

To help creating /dev/root, we have now:
  $ udevadm info --export --export-prefix="ROOT_" --device-id-of-file=/
  ROOT_MAJOR=8
  ROOT_MINOR=5
In case the current --device-id-of-file is already used, please switch to
the --export format version, it saves the output parsing and the old
format will be changed to use ':' as a separator, like the format in the
sysfs 'dev' file.



             reply	other threads:[~2008-07-21  8:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  8:02 Kay Sievers [this message]
2008-07-21  9:05 ` [ANNOUNCE] udev 125 release Marco d'Itri
2008-07-21 10:56 ` Matthias Schwarzott
2008-07-21 11:14 ` Kay Sievers
2008-07-21 11:19 ` Kay Sievers
2008-07-21 15:47 ` David Zeuthen
2008-07-22  0:06 ` David Zeuthen
2008-07-22  7:57 ` Kay Sievers
2008-07-22 13:15 ` Doug Goldstein
2008-07-28 23:08 ` David VomLehn
2008-07-28 23:32 ` Marco d'Itri
2008-07-29  1:53 ` David VomLehn
2008-07-29  2:10 ` Marco d'Itri

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=1216627334.7816.12.camel@linux.site \
    --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).