I have just compiled the vanilla kernel 2.4.21 with the patches
loop-jari-2.4.21.0 and patch-int-2.4.21.0 and it will still not run when Twofish is compiled
as a module !?. Have you only tried it compiled as a module ?
Bo
----- Oprindelig meddelelse -----
Fra: "zentara"
On Mon, 26 May 2003 01:16:23 +0200 "Bo Jacobsen"
wrote: I don't understand. What do you meen by "manually load the loop module" ?. No matter if "loopback device support" is compiled into the kernel or not, as long as "Twofish encryption for loopback device" is compiles as a module everything works OK. I have not tried compiling the "loopback device support" as a module and the "Twofish encryption for loopback device" INTO the kernel, if that's what you meen.
When I build my vanilla kernels, I get an option to build loopback device into the kernel, as a module, or not. This is separate from the crypto selections under block devices. So what I'm suggestingis build loopback support INTO the kernel, not as a module. But maybe you can't do this with a suse patched kernel.
I havn't done what you are trying. You are asking why you can't use a suse kernel to build twofish encryption into the kernel. I am guessing at why you get "loop" errors.
I have stated that it can be done on vanilla kernels, if you build loop into the kernel, as well as the encryption patch. I have mine done like that.
I will say it again, the SuSE kernels are heavily patched, and biased toward using modules. So switch to a vanilla kernel to do what you want to do. If switching to a vanilla kernel is out of the question for you, then just live with twofish as a module. It is very hard to customize the patched SuSE kernels. Maybe some other patch has made it so the kernel expects the loop_fish2 code be a module, that seems to be happening. If you do build loopback into a suse patched kernel, and manage to get twofish to build into the kernel, it's highly likely you will get errors in another area of loopback; such is the nature of the suse patched kernel. It's getting more and more complex and intertwined as time moves forward.
Why do you care about twofish as a module, security reasons? I switched to the standard international patch to get AES encryption, as well as about 10 other algorithms.
-- use Perl; #powerful programmable prestidigitation
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com