From mboxrd@z Thu Jan 1 00:00:00 1970 From: David VomLehn Date: Mon, 28 Jul 2008 23:08:13 +0000 Subject: Re: [ANNOUNCE] udev 125 release Message-Id: <488E515D.6000309@cisco.com> List-Id: References: <1216627334.7816.12.camel@linux.site> In-Reply-To: <1216627334.7816.12.camel@linux.site> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org > 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.