On Thu, Apr 23, 2009 at 11:22 AM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Tobias Powalowski wrote:
Am Mittwoch 22 April 2009 schrieb Damjan Georgievski:
What is the policy for Udev rules in ArchLinux?
There are 2 places where udev rules can be placed, /lib/udev/rules.d/ and /etc/udev/rules.d/. Now, I think the /lib/ directory should be only for the rules coming from upstream udev, and the /etc/ directory is for rules coming from ArchLinux packages.
If this is the policy everyone agrees on - and as far as I remember, udev devs recommends it too - maybe namcap can check that too?
ps. the KVM package now has rules in /lib/ , so I'll open a bug report if that's not supposed to be like that. Normally udev rules should go to /lib that the user can override them with /etc rule file.
greetings tpowa
Looking at my openSuSE install, that seems to be the way it is done there:
/lib/udev /lib/udev/ata_id /lib/udev/bluetooth.sh /lib/udev/bluetooth_serial /lib/udev/cdrom_id /lib/udev/collect /lib/udev/create_floppy_devices /lib/udev/devices /lib/udev/devices/console /lib/udev/devices/core <snip>
and then:
/etc/udev /etc/udev/rules.d /etc/udev/rules.d/40-alsa.rules /etc/udev/rules.d/40-bluetooth.rules /etc/udev/rules.d/40-suse.rules /etc/udev/rules.d/40-zaptel.rules <snip> /etc/udev/udev.conf
Actually, that's not the same. I have a suspicion suse's udev is far older, but the dir we're looking at should be /lib/udev/rules.d vs /etc/udev/rules.d