On 30 March 2014 12:47, Paul Fertser <[email protected]> wrote: [...] >>>> - openocd ships with an udev file (contrib/openocd.udev), but its not >>>> installed into the required udev directory. Is there any reason for this? >>> >>> It's now called 99-openocd.rules, and yes, it's installed to >>> /usr/share/openocd/contrib by default. Do you know of a good way to >>> make autotools copy udev rules files in a distro-specific way? >> >> There is no distribution specific directory for udev rules. Just copy it >> to /usr/lib/udev/rules.d/. > > But that _does_ sound distro-specific. E.g. on my Gentoo the rules > files usually go to /etc/udev/rules.d instead. Can you please provide > any references to the official udev documentation or FHS or something > like that probably?
From official udev documentation[1]: The udev rules are read from the files located in the system rules directory /usr/lib/udev/rules.d, the volatile runtime directory /run/udev/rules.d and the local administration directory /etc/udev/rules.d. All rules files are collectively sorted and processed in lexical order, regardless of the directories in which they live. However, files with identical filenames replace each other. Files in /etc have the highest priority, files in /run take precedence over files with the same name in /usr/lib. This can be used to override a system-supplied rules file with a local file if needed; a symlink in/etc with the same name as a rules file in /usr/lib, pointing to /dev/null, disables the rules file entirely. Rule files must have the extension .rules; other extensions are ignored. [1] http://www.freedesktop.org/software/systemd/man/udev.html#Rules%20Files Best regards, Bjørn Forsman ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
