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 1MJpUw-0004FX-UI for garchives@archives.gentoo.org; Thu, 25 Jun 2009 14:00:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4C5F9E049F; Thu, 25 Jun 2009 14:00:17 +0000 (UTC) Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 365EDE0491 for ; Thu, 25 Jun 2009 14:00:17 +0000 (UTC) Received: from [192.168.1.20] ([96.233.148.239]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KLS00GMQS7QQSP2@vms173005.mailsrvcs.net> for gentoo-user@lists.gentoo.org; Thu, 25 Jun 2009 08:59:51 -0500 (CDT) Message-id: <4A4382D6.4020802@uri.edu> Date: Thu, 25 Jun 2009 09:59:50 -0400 From: "John P. Burkett" User-Agent: Thunderbird 2.0.0.21 (X11/20090608) 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] udev, cryptsetup, and ensuing problems References: <4A4175C5.7030005@uri.edu> <58965d8a0906240730r291749fbl532ed5b923f41eaa@mail.gmail.com> <4A42FA33.5000600@uri.edu> <20090625092000.5e0b47ba@zaphod.digimed.co.uk> In-reply-to: <20090625092000.5e0b47ba@zaphod.digimed.co.uk> X-Enigmail-Version: 0.95.7 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Archives-Salt: ec52e187-f6fe-4b1b-a91e-4600330fd0d2 X-Archives-Hash: b4c86c44e92b0837adc2ba2125732895 Neil Bothwick wrote: > 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. >> >> 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. Thank you, Neil, for your clear explanation. I've now changed the symlink. > >> 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='' == cryptsetup, for LUKS you can only use --readonly" >> The meaning of these references is not clear to me. > > It's explained in the cryptsetup man page. Thanks for the pointer. As far as I can tell from the man page, no action is required by me now regarding LUKS. > >> 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? > > No, those are just the files in your portage tree. Run emerge -p > baselayout, or eix -e baselayout to see when you are running. Thanks again. Doing "eix -e baselayout" indicates that I'm using version 1.12.11.1. Hence there seems to be no need to do "rcupdate add dmcrypt boot" Best regards, John > > -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195