Bug 80776 - Loop-aes 3.0b ebuild requires BLK_DEV_LOOP=y
Bug#: 80776 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: All Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: kernel@gentoo.org Reported By: wqy5jdh02@sneakemail.com
Component: Ebuilds
URL: 
Summary: Loop-aes 3.0b ebuild requires BLK_DEV_LOOP=y
Keywords:  
Status Whiteboard: 
Opened: 2005-02-04 14:06 0000
Description:   Opened: 2005-02-04 14:06 0000
Loop-aes 3.0b ebuild quits when the correct kernel options are present. 
Loop-aes requires BLK_DEV_LOOP=n which means unset.

Here is the error------------------------------------
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.9-gentoo-r13
 * Checking for suitable kernel configuration options
 *   CONFIG_BLK_DEV_LOOP:       should be set in the kernel configuration, but
isn't
 * Please check to make sure these options are set correctly.
 * Once you have satisfied these options, please try merging
 * this package again.


Here is what is set:
# cat /usr/src/linux/.config | grep BLK_DEV_LOOP
  # CONFIG_BLK_DEV_LOOP is not set




Loop-aes README which says BLK_DEV_LOOP should be 'n' ( unset )
3. Instructions for building loop.o driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you
*must* configure, compile and install new 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.
After building and installing your new kernel, do not attempt to clean
kernel tree, or rename path to kernel sources.

------- Comment #1 From Stefan Schweizer 2005-02-04 22:28:57 0000 -------
I thought I had that ebuild tested long enough in bug 71603 .. I wonder why
such bugs come up after that period ..

Nevertheless thanks for reporting, fixed in the tree.