Hello, In my understanding this is not a bug in cryptsetup at all. Cryptsetup itself doesn't break the boot process in case that processing a dm-crypt devices fails, but instead mount and/or fsck fail due to the device not being available.
I thus suggest to reassign the bugreport to mount and initscripts, as these would be the proper packages to implement the requested feature. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
