[arch-general] Timing issues when decrypting a USB drive during boot (/etc/crypttab)

[Julius Adorf]

Thanks for your efforts.

> systemd was created specifically to avoid these kind of problems, so maybe
> you do want to use it only for this.

As far as I am concerned, I'll leave the workaround on my local work
station as it is for now. I was just wondering whether I overlooked
something obvious; as soon as the situation asks for a more robust and
reliable solution, I will give systemd+cryptsetup a try.

> I prefer not to do this in initsrcipts itself (as it is a bit too ugly for my liking)

I have noticed that the symbolic link for the USB drive in
/dev/disk/by-uuid has already been created at the time crypttab is
processed in rc.sysinit; still the drive can only accessed and
decrypted after some delay. I have only very superficial understanding
of the initscripts. Yet, I think that inserting logic just to avoid
such specific problems is probably no good, especially when it is
dealing with asynchronous behaviour.

Regards,
Julius