From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MJkBf-00041b-Tk for garchives@archives.gentoo.org; Thu, 25 Jun 2009 08:20:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5E830E041A; Thu, 25 Jun 2009 08:20:02 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id D7434E041A for ; Thu, 25 Jun 2009 08:20:01 +0000 (UTC) Received: from zaphod.digimed.co.uk (zaphod.digimed.co.uk [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 4C3C319FB77 for ; Thu, 25 Jun 2009 09:20:01 +0100 (BST) Date: Thu, 25 Jun 2009 09:20:00 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] udev, cryptsetup, and ensuing problems Message-ID: <20090625092000.5e0b47ba@zaphod.digimed.co.uk> In-Reply-To: <4A42FA33.5000600@uri.edu> References: <4A4175C5.7030005@uri.edu> <58965d8a0906240730r291749fbl532ed5b923f41eaa@mail.gmail.com> <4A42FA33.5000600@uri.edu> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.1cvs78 (GTK+ 2.16.1; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/NDNftEe/nsJjAJs+az1WSA/"; protocol="application/pgp-signature" X-Archives-Salt: 1b681b58-2f5f-44b8-8125-c288e9df50ff X-Archives-Hash: 7f2b070d8642bb31631dd040bc017ab4 --Sig_/NDNftEe/nsJjAJs+az1WSA/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 25 Jun 2009 00:16:51 -0400, John P. Burkett wrote: > 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. >=20 > 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? It's not checking the running kernel, but the sources pointed to by the /usr/src/linux symlink. I take it you have 2.6.20 installed. Change the symlink to point to the kernel in use. > 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=3D'' =3D=3D cryptsetup, for LUKS you can only use --read= only" > The meaning of these references is not clear to me. It's explained in the cryptsetup man page. > Then come the instruction: > * If you are using baselayout-2 then please do: > * rc-update add dmcrypt boot >=20 > 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 >=20 > Does the presence of those files indicate that my system is "using" > baselayout-2? No, those are just the files in your portage tree. Run emerge -p baselayout, or eix -e baselayout to see when you are running. --=20 Neil Bothwick Can you be a closet claustrophobic? --Sig_/NDNftEe/nsJjAJs+az1WSA/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkpDMzAACgkQum4al0N1GQPGTgCgvcEftogzy9TOnBhx47d7mBjD XxUAoKMMRODBaokrjupz6ktmBbaTwbYk =1cWK -----END PGP SIGNATURE----- --Sig_/NDNftEe/nsJjAJs+az1WSA/--