/lib/rcscripts/addons/dm-crypt-start.sh should have a default timeout value if something unexpected happens. If your machine is unattended it shouldn't wait forever, but try to continue without mapping your encrypted devices. As I use an external device as key storage formatted with vfat, I ran into case conversion problems without having a clue, why my box is hanging now, since I have no monitor attached to it. So I couldn't even remotely get a clue of all these troubles. Of course the timeout should be long, so that it only applies to unattended boxes.
Created attachment 108823 [details, diff] dm-crypt.patch My proposition
I am perfectly fine with the current state. Since I would need to plug in my USB thumb drive within your proposed 60 seconds, I would be forced to watch the boot process. Perhaps we couĺd make a config option out of this?
I agree totally. I'd prefer to introduce a bootparam, as this will allow us to also handle bug 162962 with the same param. As this is right before mounting root, there is no easy way to configure it in a file, what makes me opt for the bootparam. We could introduce key_timeout=[secs to wait] and use this value each time we don't detect our device. Value of zero will mean wait forever.
Created attachment 121362 [details, diff] dm-crypt.patch Voila, here a first example...
Created attachment 121473 [details, diff] dm-crypt.patch Sorry, I just forgot to merge that length function... here it is and works fine on my 2 boxes.
thanks for patch. Some mods and in cvs.
