The udev conundrum (3)

udev implemented a policy of using these legacy names in a flat namespace under /dev and making other nodes symbolic links to these. Not all userspace tools were updated accordingly and this led to numerous problems on people's systems with dynamic names like /dev/dm-3 appearing in /etc/fstab, initrd, 'mount' output etc.
udev needs to create entries in /dev/<vgname>/<lvname> for visible Logical Volumes, but not for encrypted devices created with 'cryptsetup'. In other words, different rules need to run according to which userspace tool created each device.

udev needs to create entries in /dev/<vgname>/<lvname> for visible Logical Volumes, but not for encrypted devices created with 'cryptsetup'. In other words, different rules need to run according to which userspace tool created each device.