There was no device check loop/timeout in Hardy. Just a single udevsettle and a -e test which would immediately fail if the device was missing. The intrepid changes are certain much better, but the use of "vol_id" is not valid.
The diff in the description for bug 164044 shows the changes pretty well (i.e. replacing a single -e test with a loop using -e and vol_id). It is basically just a think-o when doing the copy/paste from local's version of this loop. -- [regression] cryptsetup does not work on raw encrypted drives https://bugs.launchpad.net/bugs/291752 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
