Peter Rajnoha f3645e3f4b Fix udev rules to support udev database content generated by older rules. ... This can happen with older rules (without support for synthesized events) that are still part of initrd while using new udev rules in the system itself. The consequence was that new udev rules incorrectly assumed that not having DM_UDEV_PRIMARY_SOURCE_FLAG set always means the uevent is synthesized and inappropriate (device is still not properly activated) and so it should be ignored. However, initrd is not updated automatically while updating the libdevmapper/udev rules in the system and so we end up with the rules not detecting and setting crucial parts in the initrd environment and the rules in the system that rely on the information that should have been stored in udev db (which is incorrect in this configuration, of course). The overall consequence is that the update of libdevmapper/lvm2 without regenerating the initrd could end up with a boot failure! Ignoring the event means removing any existing symlinks in /dev! To fix this, increase udev rules version to make a difference. So from now on, mark rules without proper support for synthesized events as DM_UDEV_RULES_VSN="1" and 2 (or higher) if that support is included.		2010-08-12 13:41:18 +00:00
..
10-dm.rules.in	Fix udev rules to support udev database content generated by older rules.	2010-08-12 13:41:18 +00:00
11-dm-lvm.rules	Use "nowatch" udev rule for known inappropriate devices.	2010-07-07 11:22:46 +00:00
12-dm-permissions.rules	add copyright lines	2009-10-26 22:42:07 +00:00
13-dm-disk.rules	Remove 'last_rule' from udev rules.	2009-11-13 12:33:27 +00:00
95-dm-notify.rules	More cleanup in udev rules:	2009-11-01 18:01:31 +00:00
Makefile.in	Update install rules for udev.	2010-04-09 21:44:28 +00:00