| 1 |
Paul Hartman wrote: |
| 2 |
> On Tue, Jun 23, 2009 at 7:39 PM, John P. Burkett<burkett@×××.edu> wrote: |
| 3 |
>> !!! Couldn't download 'cryptsetup-1.0.6.tar.bz2'. Aborting. |
| 4 |
> |
| 5 |
> I don't know why your downloads are failing or the rest of your |
| 6 |
> problems, but you can download cryptsetup manually from here: |
| 7 |
> |
| 8 |
> http://code.google.com/p/cryptsetup/downloads/detail?name=cryptsetup-1.0.6.tar.bz2&can=2&q= |
| 9 |
> |
| 10 |
Paul, Thank you very much for this valuable tip. I downloaded |
| 11 |
cryptsetup-1.0.6.tar.bz2&can=2&q= to /usr/portage/distfiles/ and did |
| 12 |
"emerge cryptsetup" |
| 13 |
|
| 14 |
The response included the following lines: |
| 15 |
* Determining the location of the kernel source code |
| 16 |
* Found kernel source directory: |
| 17 |
* /usr/src/linux |
| 18 |
* Found sources for kernel version: |
| 19 |
* 2.6.20-gentoo-r6 |
| 20 |
* Checking for suitable kernel configuration options... |
| 21 |
* CONFIG_DM_CRYPT: is not set (required for cryptsetup) |
| 22 |
* |
| 23 |
* Please check to make sure these options are set correctly. |
| 24 |
* Failure to do so may cause unexpected problems. |
| 25 |
* Checking for suitable kernel configuration options... |
| 26 |
* CONFIG_CRYPTO: is not set (required for cryptsetup) |
| 27 |
* |
| 28 |
* Please check to make sure these options are set correctly. |
| 29 |
* Failure to do so may cause unexpected problems. |
| 30 |
* Checking for suitable kernel configuration options... |
| 31 |
* CONFIG_CRYPTO_CBC: is not set (required for kernel 2.6.19) |
| 32 |
* |
| 33 |
* Please check to make sure these options are set correctly. |
| 34 |
* Failure to do so may cause unexpected problems. |
| 35 |
|
| 36 |
The references to kernel version 2.6.20 and 2.6.19 surprised me because |
| 37 |
doing "uname -r" produces "2.6.17-gentoo-r4". Suggestions about how to |
| 38 |
set CONFIG_DM_CRYPT and CONFIG_CRYPTO appropriately would be |
| 39 |
appreciated. As a user of kernel 2.6.17, may I leave CONFIG_CRYPTO_CBC |
| 40 |
unset? |
| 41 |
|
| 42 |
Further down, the output included these lines: |
| 43 |
>>> Installing (1 of 1) sys-fs/cryptsetup-1.0.6-r2 |
| 44 |
* This ebuild introduces a new set of scripts and configuration |
| 45 |
* than the last version. If you are currently using /etc/conf.d/cryptfs |
| 46 |
* then you *MUST* copy your old file to: |
| 47 |
* /etc/conf.d/dmcrypt |
| 48 |
* Or your encrypted partitions will *NOT* work. |
| 49 |
|
| 50 |
In the directory /etc/conf.d there is no cryptfs and thus, I assume, |
| 51 |
nothing to be copied. |
| 52 |
|
| 53 |
The next two lines of output are |
| 54 |
* Please see the example for configuring a LUKS mountpoint |
| 55 |
* in /etc/conf.d/dmcrypt |
| 56 |
|
| 57 |
In dmcrypt I find two references to LUKS. First, "the init-script which |
| 58 |
reads this file detects whether your partition is LUKS or not. No mkfs |
| 59 |
is run unless you specify a makefs" Second, |
| 60 |
"# options='<opts>' == cryptsetup, for LUKS you can only use --readonly" |
| 61 |
The meaning of these references is not clear to me. |
| 62 |
|
| 63 |
Then come the instruction: |
| 64 |
* If you are using baselayout-2 then please do: |
| 65 |
* rc-update add dmcrypt boot |
| 66 |
|
| 67 |
Doing "locate baselayout-2" produces |
| 68 |
/var/cache/edb/dep/usr/portage/sys-apps/baselayout-2.0.0 |
| 69 |
/usr/portage/metadata/cache/sys-apps/baselayout-2.0.0 |
| 70 |
/usr/portage/metadata/cache/sys-apps/baselayout-2.0.1 |
| 71 |
/usr/portage/sys-apps/baselayout/baselayout-2.0.0.ebuild |
| 72 |
/usr/portage/sys-apps/baselayout/baselayout-2.0.1.ebuild |
| 73 |
|
| 74 |
Does the presence of those files indicate that my system is "using" |
| 75 |
baselayout-2? |
| 76 |
|
| 77 |
Best regards, |
| 78 |
John |
| 79 |
|
| 80 |
-- |
| 81 |
John P. Burkett |
| 82 |
Department of Economics |
| 83 |
University of Rhode Island |
| 84 |
Kingston, RI 02881-0808 |
| 85 |
USA |
| 86 |
|
| 87 |
phone (401) 874-9195 |
Archives