From: David VomLehn <dvomlehn@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 125 release
Date: Mon, 28 Jul 2008 23:08:13 +0000 [thread overview]
Message-ID: <488E515D.6000309@cisco.com> (raw)
In-Reply-To: <1216627334.7816.12.camel@linux.site>
> 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:
...
> /etc/udev/rules.d/ - user rules + on-the-fly generated rules
...
I think there is a problem. The Filesystem Hierarchy Standard states (See
http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION):
> The /etc hierarchy contains configuration files. A "configuration file" is a
> local file used to control the operation of a program; it must be static...
If I understand what is meant by "on-the-fly generated rules", these are not
static and so don't belong under /etc. I think an FHS-conforming place for these
would be under /var somewhere, such as /var/lib/udev. Placing them under /etc can
be an issue for embedded systems where /etc is frequently read-only.
- - - - - Cisco - - - - -
This e-mail and any attachments may contain information which is confidential,
proprietary, privileged or otherwise protected by law. The information is solely
intended for the named addressee (or a person responsible for delivering it to
the addressee). If you are not the intended recipient of this message, you are
not authorized to read, print, retain, copy or disseminate this message or any
part of it. If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete it from your computer.
next prev parent reply other threads:[~2008-07-28 23:08 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
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 [this message]
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=488E515D.6000309@cisco.com \
--to=dvomlehn@cisco.com \
--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).