The kernel version bug in previous versions of busybox which inspired the /sbin/modprobe bash script have been fixed in the latest releases of busybox. I suggest that the initrd be upgraded to use the latest BusyBox (maybe cvs) that is concidered stable.
Steps to Reproduce:
The initrd creation is totally done by genkernel, so I am reassigning to them.
Do we have a upstream busybox that now supports mounting cryptoloop on 2.6 using the new 2.6 API and mounting plain loops on 2.4?
As of the current CVS snapshot of busybox losetup util does not support enabling encryption upon its loops.
Hrm, well we need a busybox that can do 2.6 and 2.4 loop mounting, and since the CVS ones don't provide this, I don't think it is worth the effort of getting the support into a new busybox - the current method works without any problems anyway...
Closing as WONTFIX; comment #4.