As the summary says, file/crypto-loop.initd uses several bashisms which make the file fail if e.g. /bin/sh is a symlink to dash. As usual, only small syntax changes are necessary to make it POSIX compliant. I attach a patch.
Created attachment 164719 [details, diff] Patch to make crypto-loop.initd POSIX compliant The patch in addition removes the redundant call of "ls" which might have produced a confusing error message if no /dev/loop[0-9] exists (and a new line was inserted to deal with that case).
Thanks for the cleanup patch, assigning to maintainers
changing [[ -n ${var} ]] to [ -n ${var} ] is broken ive fixed things up and committed it, thanks http://sources.gentoo.org/sys-apps/util-linux/files/crypto-loop.initd?r1=1.3&r2=1.4
