Re: README confusing in loop-AES-v1.2d

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

 



On 9 July 2001, Tim R. Young <try@xxxxxxxxx> wrote:
> Before you attempt to build replacement loop.o driver, you *must* configure
> and compile your kernel so that CONFIG_MODULES=y and CONFIG_BLK_DEV_LOOP=n.
> Also, CONFIG_KMOD=y is recommended but not required (kernel 2.0 doesn't have
> CONFIG_KMOD, set CONFIG_KERNELD=y instead). Configuring your kernel so that
> loop driver is built-in (CONFIG_BLK_DEV_LOOP=y) or module
> (CONFIG_BLK_DEV_LOOP=m) will *not* work.
> 
> Do I need to set
> CONFIG_BLK_DEV_LOOP=n
> or
> CONFIG_BLK_DEV_LOOP=y
> ?
> 
> I guess it should be CONFIG_BLK_DEV_LOOP=m?
> 
> The first and last sentences are conflicting.

CONFIG_BLK_DEV_LOOP=n

I guess for some people even if you use '*' to underline the 'not' word
is not enough.

-- 
								Regards,
								Emil
--
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself.  Therefore all progress
depends on the unreasonable man."				   - Shaw

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


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux