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: Re: [ANNOUNCE] udev 125 release
Date: Mon, 21 Jul 2008 11:19:16 +0000	[thread overview]
Message-ID: <1216639156.7816.24.camel@linux.site> (raw)
In-Reply-To: <1216627334.7816.12.camel@linux.site>

On Mon, 2008-07-21 at 12:56 +0200, Matthias Schwarzott wrote:
> On Montag, 21. Juli 2008, Kay Sievers wrote:
> > 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/
> >
> Well, it is not yet there.

Should be there now. Sorry, forgot to copy it.

> > 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=Change
> >Log
> >
> >
> > 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.
> >
> 
> And I wanted to ask the same question as Marco: Do distributions need to move 
> these rules to /lib/udev/rules.d/ ?

No, but it's suggested that /etc will only contain stuff that can be
edited by users/admins. But everything will work the same way as before
if /lib/udev/rules.d/ is not used.

> We on gentoo do use /lib64/udev to be strict on systems using 32 and 64 bit 
> libraries, so the rules end in /lib64/udev/rules.d if we choose this way.

/lib/udev/ is udev's private directory on _every_ system, as LSB
defines. There is no single library in /lib/udev/, the translation to
/lib64/udev/ is broken in exactly the same way you would introduce
/sbin64/udevd. I suggest you fix that, instead of trying to work around
the problems it creates.

Thanks,
Kay


  parent reply	other threads:[~2008-07-21 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  8:02 [ANNOUNCE] udev 125 release Kay Sievers
2008-07-21  9:05 ` Marco d'Itri
2008-07-21 10:56 ` Matthias Schwarzott
2008-07-21 11:14 ` Kay Sievers
2008-07-21 11:19 ` Kay Sievers [this message]
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=1216639156.7816.24.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).