| 1 |
On Thu, 25 Jun 2009 00:16:51 -0400, John P. Burkett wrote: |
| 2 |
|
| 3 |
> The response included the following lines: |
| 4 |
> * Determining the location of the kernel source code |
| 5 |
> * Found kernel source directory: |
| 6 |
> * /usr/src/linux |
| 7 |
> * Found sources for kernel version: |
| 8 |
> * 2.6.20-gentoo-r6 |
| 9 |
> * Checking for suitable kernel configuration options... |
| 10 |
> * CONFIG_DM_CRYPT: is not set (required for cryptsetup) |
| 11 |
> * |
| 12 |
> * Please check to make sure these options are set correctly. |
| 13 |
> * Failure to do so may cause unexpected problems. |
| 14 |
> * Checking for suitable kernel configuration options... |
| 15 |
> * CONFIG_CRYPTO: is not set (required for cryptsetup) |
| 16 |
> * |
| 17 |
> * Please check to make sure these options are set correctly. |
| 18 |
> * Failure to do so may cause unexpected problems. |
| 19 |
> * Checking for suitable kernel configuration options... |
| 20 |
> * CONFIG_CRYPTO_CBC: is not set (required for kernel 2.6.19) |
| 21 |
> * |
| 22 |
> * Please check to make sure these options are set correctly. |
| 23 |
> * Failure to do so may cause unexpected problems. |
| 24 |
> |
| 25 |
> The references to kernel version 2.6.20 and 2.6.19 surprised me because |
| 26 |
> doing "uname -r" produces "2.6.17-gentoo-r4". Suggestions about how to |
| 27 |
> set CONFIG_DM_CRYPT and CONFIG_CRYPTO appropriately would be |
| 28 |
> appreciated. As a user of kernel 2.6.17, may I leave CONFIG_CRYPTO_CBC |
| 29 |
> unset? |
| 30 |
|
| 31 |
It's not checking the running kernel, but the sources pointed to by |
| 32 |
the /usr/src/linux symlink. I take it you have 2.6.20 installed. Change |
| 33 |
the symlink to point to the kernel in use. |
| 34 |
|
| 35 |
> In dmcrypt I find two references to LUKS. First, "the init-script which |
| 36 |
> reads this file detects whether your partition is LUKS or not. No mkfs |
| 37 |
> is run unless you specify a makefs" Second, |
| 38 |
> "# options='<opts>' == cryptsetup, for LUKS you can only use --readonly" |
| 39 |
> The meaning of these references is not clear to me. |
| 40 |
|
| 41 |
It's explained in the cryptsetup man page. |
| 42 |
|
| 43 |
> Then come the instruction: |
| 44 |
> * If you are using baselayout-2 then please do: |
| 45 |
> * rc-update add dmcrypt boot |
| 46 |
> |
| 47 |
> Doing "locate baselayout-2" produces |
| 48 |
> /var/cache/edb/dep/usr/portage/sys-apps/baselayout-2.0.0 |
| 49 |
> /usr/portage/metadata/cache/sys-apps/baselayout-2.0.0 |
| 50 |
> /usr/portage/metadata/cache/sys-apps/baselayout-2.0.1 |
| 51 |
> /usr/portage/sys-apps/baselayout/baselayout-2.0.0.ebuild |
| 52 |
> /usr/portage/sys-apps/baselayout/baselayout-2.0.1.ebuild |
| 53 |
> |
| 54 |
> Does the presence of those files indicate that my system is "using" |
| 55 |
> baselayout-2? |
| 56 |
|
| 57 |
No, those are just the files in your portage tree. Run emerge -p |
| 58 |
baselayout, or eix -e baselayout to see when you are running. |
| 59 |
|
| 60 |
|
| 61 |
-- |
| 62 |
Neil Bothwick |
| 63 |
|
| 64 |
Can you be a closet claustrophobic? |
Archives