[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: loop-aes vs stock loop

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 07 March 2002 11:06, Erno Kuusela wrote:
<snip>
> 	CONFIG_MODULES=y

That's so you can actually use loadable modules.

> and CONFIG_BLK_DEV_LOOP=n.

This should probably read =m. I can't think of a reason why the stock 
loop driver shouldn't be compiled, since you can always decide what 
loop driver to load t modprobe time.

> so it's a no-no to have the stock loop driver is compiled as a module
> (but unused)? why is this?
<snip>

If this were correct, Jari's claim that loop-AES works with distributor 
kernels wouldn't hold, since they all compile loop.o as module (they 
compile _everything_ as modules ;-).

Marc

- -- 
Marc Mutz <mutz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8h0z73oWD+L2/6DgRAtswAKDft6F+YV8C1ck2U5nRm/f5im1RgwCeOpoD
aIuL5j/GCG9fQAGPbVqDw9s=
=Qo7m
-----END PGP SIGNATURE-----

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/