Erno: As I understand it this is because the kernel loop driver is replaced by loop-aes. Therefore you must be sure that the kernel does not build this competing module to the replacement module. Modules obviously need to be enabled so that loop-aes module can be a viable loadable module. I am sure Mr. Ruusu can give you a better explanation of this scenario. But it will not work unless you follow those instructions. Very Respectfully, Stuart Blake Tener, IT3 (E-4), USNR-R, N3GWG Beverly Hills, California VTU 1904G (Volunteer Training Unit) stuart@bh90210.net west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. Thursday, March 07, 2002 2:31 AM -----Original Message----- From: linux-crypto-bounce@nl.linux.org [mailto:linux-crypto-bounce@nl.linux.org] On Behalf Of Erno Kuusela Sent: Thursday, March 07, 2002 2:06 AM To: linux-crypto@nl.linux.org Subject: loop-aes vs stock loop hello, i'm curious: the installation instructions for loop-aes say: Before you attempt to build loop.o driver, you *must* configure, compile and install new kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n. so it's a no-no to have the stock loop driver is compiled as a module (but unused)? why is this? -- erno - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
