Re: [gentoo-user] udev, cryptsetup, and ensuing problems

["John P. Burkett" <burkett@uri.edu>]

Paul Hartman wrote:
> On Tue, Jun 23, 2009 at 7:39 PM, John P. Burkett<burkett@uri.edu> wrote:
>> !!! Couldn't download 'cryptsetup-1.0.6.tar.bz2'. Aborting.
> 
> I don't know why your downloads are failing or the rest of your
> problems, but you can download cryptsetup manually from here:
> 
> http://code.google.com/p/cryptsetup/downloads/detail?name=cryptsetup-1.0.6.tar.bz2&can=2&q=
> 
Paul, Thank you very much for this valuable tip. I downloaded
cryptsetup-1.0.6.tar.bz2&can=2&q= to  /usr/portage/distfiles/ and did
"emerge cryptsetup"

The response included the following lines:
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.20-gentoo-r6
 * Checking for suitable kernel configuration options...
 *   CONFIG_DM_CRYPT:	is not set (required for cryptsetup)
 *
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * Checking for suitable kernel configuration options...
 *   CONFIG_CRYPTO:	is not set (required for cryptsetup)
 *
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * Checking for suitable kernel configuration options...
 *   CONFIG_CRYPTO_CBC:	is not set (required for kernel 2.6.19)
 *
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.

The references to kernel version 2.6.20 and 2.6.19 surprised me because
doing "uname -r" produces "2.6.17-gentoo-r4". Suggestions about how to
set CONFIG_DM_CRYPT and CONFIG_CRYPTO appropriately would be
appreciated.  As a user of kernel 2.6.17, may I leave CONFIG_CRYPTO_CBC
unset?

Further down, the output included these lines:
>>> Installing (1 of 1) sys-fs/cryptsetup-1.0.6-r2
 * This ebuild introduces a new set of scripts and configuration
 * than the last version. If you are currently using /etc/conf.d/cryptfs
 * then you *MUST* copy your old file to:
 * /etc/conf.d/dmcrypt
 * Or your encrypted partitions will *NOT* work.

In the directory /etc/conf.d there is no cryptfs and thus, I assume,
nothing to be copied.

The next two lines of output are
 * Please see the example for configuring a LUKS mountpoint
 * in /etc/conf.d/dmcrypt

In dmcrypt I find two references to LUKS.  First, "the init-script which
reads this file detects whether your partition is LUKS or not. No mkfs
is run unless you specify a makefs"  Second,
"# options='<opts>' == cryptsetup, for LUKS you can only use --readonly"
The meaning of these references is not clear to me.

Then come the instruction:
 * If you are using baselayout-2 then please do:
 * rc-update add dmcrypt boot

Doing "locate baselayout-2" produces
/var/cache/edb/dep/usr/portage/sys-apps/baselayout-2.0.0
/usr/portage/metadata/cache/sys-apps/baselayout-2.0.0
/usr/portage/metadata/cache/sys-apps/baselayout-2.0.1
/usr/portage/sys-apps/baselayout/baselayout-2.0.0.ebuild
/usr/portage/sys-apps/baselayout/baselayout-2.0.1.ebuild

Does the presence of those files indicate that my system is "using"
baselayout-2?

Best regards,
John

-- 
John P. Burkett
Department of Economics
University of Rhode Island
Kingston, RI 02881-0808
USA

phone (401) 874-9195