From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robby Workman Date: Wed, 07 Jan 2009 21:43:38 +0000 Subject: Re: [PATCH] Install udev rules to /lib/udev/rules.d Message-Id: <20090107154338.1291d434@liberty.rlwhome.lan> MIME-Version: 1 Content-Type: multipart/mixed; boundary="Sig_/qaSOHifX9rlcO=pzrgUY8mR" List-Id: References: <1231350785.6840.91.camel@quest> In-Reply-To: <1231350785.6840.91.camel@quest> To: linux-hotplug@vger.kernel.org --Sig_/qaSOHifX9rlcO=pzrgUY8mR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 07 Jan 2009 20:51:48 +0100 Marcel Holtmann wrote: > > > udev now installs rules into /lib/udev/rules.d by default, > > > leaving /etc/udev/rules.d for user rules and overrides only. > > > > > > HAL should be updated to follow suit: > >=20 > > Applied. Also bumped the udev requirement and used @ for the > > abstract socket. >=20 > do you expect an application to install its rules in /lib/udev/rules.d > now. I was assuming this is for udev's own rules only? It's my understanding (and I say this with the hope/expectation that I'll be corrected if I'm wrong) that /lib/udev/rules.d/ is where *most* package rules should go -- basically, anything for which the sysadmin should have no reason to edit. /etc/udev/rules.d/ would be for system-specific rules and/or generated rules (e.g. persistent optical and network devices rules files, and other things that might change over the life of the system). -RW --Sig_/qaSOHifX9rlcO=pzrgUY8mR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkllIgsACgkQvGy9tf6lsvst1gCff1RqJYFKxnw/m22RakIt4ZJE v7wAoJvxxv+0mjKK32EDRj0yMcNcv68g =H3Rw -----END PGP SIGNATURE----- --Sig_/qaSOHifX9rlcO=pzrgUY8mR--