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