The loop-aes README is quite unambiguous about the need to ensure that the kernel against which the loop.o driver is built has been compiled "...so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n". (The usual with downloaded precompiled debian kernels would be CONFIG_BLK_DEV_LOOP=m). (As I have been attempting to do) But the following online guides to building loop-aes on debian (using the .deb source packages not the sourceforge tarballs) don't mention this at all, which seems (?) to imply a kernel rebuild is not necessary for their approaches, in fact it looks like they simply rmmod the existing loop.o before loading the new module with modprobe loop. http://www.debian-administration.org/?article=81 http://deb.riseup.net/storage/encryption/loop-aes/ Is that the case, and, if so, why/how is it so ...? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
