I see the latest dmsetup has fixed this in a different way. It always creates the device node in /dev/mapper, so cryptsetup should be fine with that (I haven't tried it though).
The latest version doesn't run vol_id for read-only devices, as before Is that right, I wonder? At least the cryptsetup problem is fixed now, I think. -- udev rules don't create device nodes for readonly devices https://bugs.launchpad.net/bugs/117089 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
