summaryrefslogtreecommitdiff
path: root/udev/Makefile.in
diff options
context:
space:
mode:
authorPeter Rajnoha <prajnoha@redhat.com>2012-02-24 09:53:12 +0000
committerPeter Rajnoha <prajnoha@redhat.com>2012-02-24 09:53:12 +0000
commit32c84c8f3de1b846c7c029a196d03fdf90219fd1 (patch)
tree3ebc0342b6497719388295bf7a0932fa4b6c6a6d /udev/Makefile.in
parentdc4a15bb69f6461dafdd55de7798733be68ce4f7 (diff)
downloadlvm2-32c84c8f3de1b846c7c029a196d03fdf90219fd1.tar.gz
Add skeleton for lvmetad udev rules - 69-dm-lvm-metad.rules.
Why using the order 69: - Storage processing in general happens in 60-persistent-storage.rules, including the blkid call that adds some usable information we can use for filtering and speedup (these rules are part of upstream udev and the order is preserved on most distros) - There's still some other storage-related processing done after 60-persistent-storage.rules in general. These might add some detailed storage-related information we might use to filter devices effectively (e.g. MD udev rules, ...). - We need lvmetad rules to be processed before any consumers can use the output - so the metadata cache is ready soon enough (e.g. udisks rules). - There's no official (upstream udev) document about assigning the order, so this number is chosen in best belief it will suit all scenarios.
Diffstat (limited to 'udev/Makefile.in')
-rw-r--r--udev/Makefile.in4
1 files changed, 4 insertions, 0 deletions
diff --git a/udev/Makefile.in b/udev/Makefile.in
index 44bdf114e..4ace9108e 100644
--- a/udev/Makefile.in
+++ b/udev/Makefile.in
@@ -19,6 +19,10 @@ DM_RULES=10-dm.rules 13-dm-disk.rules 95-dm-notify.rules
LVM_RULES=11-dm-lvm.rules
DM_DIR=$(shell grep "\#define DM_DIR" $(top_srcdir)/libdm/misc/dm-ioctl.h | awk '{print $$3}')
+ifeq ("@BUILD_LVMETAD@", "yes")
+LVM_RULES+=69-dm-lvm-metad.rules
+endif
+
ifeq ("@UDEV_HAS_BUILTIN_BLKID@", "yes")
BLKID_RULE=IMPORT{builtin}=\"blkid\"
else