Re: [gentoo-user] udev, cryptsetup, and ensuing problems
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. 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='opts' == 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. 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. -- Neil Bothwick Can you be a closet claustrophobic? signature.asc Description: PGP signature
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
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='opts' == 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
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
On Wednesday 24 June 2009 02:39:33 John P. Burkett wrote: At that point I had the impression that the machine was not up-to-date but nonetheless functional. However, the next morning I noticed that the computer would not print to my local printer. Using the CUPS menu did not rectify the problem. When I rebooted, the machine wouldn't start X and the mouse wouldn't work. Rebooting again, I used the Grub menu to select an old reliable configuration which allowed me to login at a command line interface but did allow me to start X. This has been dealt with ad-nauseam on this list over the last few weeks, with many many threads covering these issues (they are very common) Please check the mail archives for the full story in all it's excruciating detail. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
Alan McKinnon wrote: On Wednesday 24 June 2009 02:39:33 John P. Burkett wrote: At that point I had the impression that the machine was not up-to-date but nonetheless functional. However, the next morning I noticed that the computer would not print to my local printer. Using the CUPS menu did not rectify the problem. When I rebooted, the machine wouldn't start X and the mouse wouldn't work. Rebooting again, I used the Grub menu to select an old reliable configuration which allowed me to login at a command line interface but did allow me to start X. This has been dealt with ad-nauseam on this list over the last few weeks, with many many threads covering these issues (they are very common) Please check the mail archives for the full story in all it's excruciating detail. Thank you, Alan, for the pointer. Going to http://archives.gentoo.org/gentoo-user/ and using Firefox's find facility, I searched for each of the following expressions: udev, cryptsetup, host address, distrfiles.shea, filesize, printer, startx, mouse. I have not found the threads to which you refer. If you could point out a relevant starting point in the archives, I would be very grateful. John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
On Wednesday 24 June 2009 15:47:44 John P. Burkett wrote: Alan McKinnon wrote: On Wednesday 24 June 2009 02:39:33 John P. Burkett wrote: At that point I had the impression that the machine was not up-to-date but nonetheless functional. However, the next morning I noticed that the computer would not print to my local printer. Using the CUPS menu did not rectify the problem. When I rebooted, the machine wouldn't start X and the mouse wouldn't work. Rebooting again, I used the Grub menu to select an old reliable configuration which allowed me to login at a command line interface but did allow me to start X. This has been dealt with ad-nauseam on this list over the last few weeks, with many many threads covering these issues (they are very common) Please check the mail archives for the full story in all it's excruciating detail. Thank you, Alan, for the pointer. Going to http://archives.gentoo.org/gentoo-user/ and using Firefox's find facility, I searched for each of the following expressions: udev, cryptsetup, host address, distrfiles.shea, filesize, printer, startx, mouse. I have not found the threads to which you refer. If you could point out a relevant starting point in the archives, I would be very grateful. Try looking for threads started by user Dale and working from there. He's not alone in his woes, but he's certainly the most vocal. His threads also tend to stay on-topic, leading to answers instead of natter. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
On Tue, Jun 23, 2009 at 7:39 PM, John P. Burkettburk...@uri.edu wrote: !!! Couldn't download 'cryptsetup-1.0.6.tar.bz2'. Aborting. I don't know why your downloads are failing or the rest of your problems, but you can download cryptsetup manually from here: http://code.google.com/p/cryptsetup/downloads/detail?name=cryptsetup-1.0.6.tar.bz2can=2q=
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
Alan McKinnon wrote: On Wednesday 24 June 2009 15:47:44 John P. Burkett wrote: Alan McKinnon wrote: On Wednesday 24 June 2009 02:39:33 John P. Burkett wrote: At that point I had the impression that the machine was not up-to-date but nonetheless functional. However, the next morning I noticed that the computer would not print to my local printer. Using the CUPS menu did not rectify the problem. When I rebooted, the machine wouldn't start X and the mouse wouldn't work. Rebooting again, I used the Grub menu to select an old reliable configuration which allowed me to login at a command line interface but did allow me to start X. This has been dealt with ad-nauseam on this list over the last few weeks, with many many threads covering these issues (they are very common) Please check the mail archives for the full story in all it's excruciating detail. Thank you, Alan, for the pointer. Going to http://archives.gentoo.org/gentoo-user/ and using Firefox's find facility, I searched for each of the following expressions: udev, cryptsetup, host address, distrfiles.shea, filesize, printer, startx, mouse. I have not found the threads to which you refer. If you could point out a relevant starting point in the archives, I would be very grateful. Try looking for threads started by user Dale and working from there. He's not alone in his woes, but he's certainly the most vocal. His threads also tend to stay on-topic, leading to answers instead of natter. Alan, thanks for calling Dale's contributions to my attention. Going to http://archives.gentoo.org/gentoo-user/ and using Firefox's find facility, I searched for Dale on the first 10 pages sorted by thread and the first 10 pages sorted by date. The later goes back to May 31. So far I have not found a thread started by Dale that deals with problems similar to mine. If you could identify a specific thread, I would appreciate it. -John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
Alan McKinnon wrote: On Wednesday 24 June 2009 15:47:44 John P. Burkett wrote: Alan McKinnon wrote: On Wednesday 24 June 2009 02:39:33 John P. Burkett wrote: At that point I had the impression that the machine was not up-to-date but nonetheless functional. However, the next morning I noticed that the computer would not print to my local printer. Using the CUPS menu did not rectify the problem. When I rebooted, the machine wouldn't start X and the mouse wouldn't work. Rebooting again, I used the Grub menu to select an old reliable configuration which allowed me to login at a command line interface but did allow me to start X. This has been dealt with ad-nauseam on this list over the last few weeks, with many many threads covering these issues (they are very common) Please check the mail archives for the full story in all it's excruciating detail. Thank you, Alan, for the pointer. Going to http://archives.gentoo.org/gentoo-user/ and using Firefox's find facility, I searched for each of the following expressions: udev, cryptsetup, host address, distrfiles.shea, filesize, printer, startx, mouse. I have not found the threads to which you refer. If you could point out a relevant starting point in the archives, I would be very grateful. Try looking for threads started by user Dale and working from there. He's not alone in his woes, but he's certainly the most vocal. His threads also tend to stay on-topic, leading to answers instead of natter. I was always told that I talk a lot. LOL Can he search by my email address too? That should narrow down the search a lot. Dale :-) :-)
Re: [gentoo-user] udev, cryptsetup, and ensuing problems
Paul Hartman wrote: On Tue, Jun 23, 2009 at 7:39 PM, John P. Burkettburk...@uri.edu wrote: !!! Couldn't download 'cryptsetup-1.0.6.tar.bz2'. Aborting. I don't know why your downloads are failing or the rest of your problems, but you can download cryptsetup manually from here: http://code.google.com/p/cryptsetup/downloads/detail?name=cryptsetup-1.0.6.tar.bz2can=2q= Paul, Thank you very much for this valuable tip. I downloaded cryptsetup-1.0.6.tar.bz2can=2q= to /usr/portage/distfiles/ and did emerge cryptsetup 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? Further down, the output included these lines: Installing (1 of 1) sys-fs/cryptsetup-1.0.6-r2 * This ebuild introduces a new set of scripts and configuration * than the last version. If you are currently using /etc/conf.d/cryptfs * then you *MUST* copy your old file to: * /etc/conf.d/dmcrypt * Or your encrypted partitions will *NOT* work. In the directory /etc/conf.d there is no cryptfs and thus, I assume, nothing to be copied. The next two lines of output are * Please see the example for configuring a LUKS mountpoint * in /etc/conf.d/dmcrypt 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='opts' == cryptsetup, for LUKS you can only use --readonly The meaning of these references is not clear to me. 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? Best regards, John -- John P. Burkett Department of Economics University of Rhode Island Kingston, RI 02881-0808 USA phone (401) 874-9195
[gentoo-user] udev, cryptsetup, and ensuing problems
On an x86 machine with kernel 2.6.17-gentoo-r4, I did eix-sync and
emerge -NauvD system and received a response including the following line:
[blocks B ] =sys-fs/udev-126 (=sys-fs/udev-126 is blocking
sys-fs/cryptsetup-1.0.5-r1)
Doing emerge -p -C udev elicited the following lines:
!!! 'sys-fs/udev' is part of your system profile.
!!! Unmerging it may be damaging to your system.
Looking for a safer fix for the blockage, I did emerge -C cryptsetup.
Repeating emerge -NauvD system, produced output including the following:
Emerging (1 of 2) sys-libs/db-4.6.21_p4
* patch.4.6.21.1 RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
* db-4.6.21.tar.gz RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
* patch.4.6.21.2 RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
Downloading 'http://distfiles.oshean.org/distfiles/patch.4.6.21.3'
--2009-06-20 12:42:25--
http://distfiles.oshean.org/distfiles/patch.4.6.21.3
Resolving distfiles.oshean.org... failed: Name or service not known.
wget: unable to resolve host address `distfiles.oshean.org'
Downloading
'http://open-systems.ufl.edu/mirrors/gentoo/distfiles/patch.4.6.21.3'
--2009-06-20 12:42:25--
http://open-systems.ufl.edu/mirrors/gentoo/distfiles/patch.4.6.21.3
Resolving open-systems.ufl.edu... 128.227.74.33
Connecting to open-systems.ufl.edu|128.227.74.33|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2009-06-20 12:42:25 ERROR 403: Forbidden.
Downloading
'http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/patch.4.6.21.3'
--2009-06-20 12:42:25--
http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/patch.4.6.21.3
Resolving www.oracle.com... 141.146.9.91
Connecting to www.oracle.com|141.146.9.91|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1911 (1.9K) [application/octet-stream]
Saving to: `/usr/portage/distfiles/patch.4.6.21.3'
100%[==] 1,911 --.-K/s in
0s
2009-06-20 12:42:25 (203 MB/s) - `/usr/portage/distfiles/patch.4.6.21.3'
saved [1911/1911]
('Filesize does not match recorded size', 1911L, 1517)
!!! Fetched file: patch.4.6.21.3 VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 1911
!!! Expected: 1517
Refetching... File renamed to
'/usr/portage/distfiles/patch.4.6.21.3._checksum_failure_.wsiPuJ'
!!! Couldn't download 'patch.4.6.21.3'. Aborting.
* Fetch failed for 'sys-libs/db-4.6.21_p4', Log file:
* '/var/tmp/portage/sys-libs/db-4.6.21_p4/temp/build.log'
Failed to emerge sys-libs/db-4.6.21_p4, Log file:
'/var/tmp/portage/sys-libs/db-4.6.21_p4/temp/build.log'
* Messages for package sys-libs/db-4.6.21_p4:
* Fetch failed for 'sys-libs/db-4.6.21_p4', Log file:
* '/var/tmp/portage/sys-libs/db-4.6.21_p4/temp/build.log'
Doing emerge --resume --skip-first yielded output including the following:
* Updating persistent-net rules file
*
* restarting udevd now.
*
* persistent-net does assigning fixed names to network devices.
* If you have problems with the persistent-net rules,
* just delete the rules file
* rm /etc/udev/rules.d/70-persistent-net.rules
* and then reboot.
*
* This may however number your devices in a different way than they are
now.
*
* If you build an initramfs including udev, then please
* make sure that the /sbin/udevadm binary gets included,
* and your scripts changed to use it,as it replaces the
* old helper apps udevinfo, udevtrigger, ...
*
* mount options for directory /dev are no longer
* set in /etc/udev/udev.conf, but in /etc/fstab
* as for other directories.
*
* For more information on udev on Gentoo, writing udev rules, and
* fixing known issues visit:
* http://www.gentoo.org/doc/en/udev-guide.xml
Regenerating /etc/ld.so.cache...
* Messages for package sys-fs/udev-141:
* If you want to use udev reliable you should update
* to at least kernel version 2.6.22!
*
* Moving //etc/modprobe.d//pnp-aliases to pnp-aliases.conf
* Moving //etc/modprobe.d//blacklist to blacklist.conf
*
* Updating persistent-net rules file
*
* restarting udevd now.
*
* persistent-net does assigning fixed names to network devices.
* If you have problems with the persistent-net rules,
* just delete the rules file
* rm /etc/udev/rules.d/70-persistent-net.rules
* and then reboot.
*
* This may however number your devices in a different way than they are
now.
*
* If you build an initramfs including udev, then please
* make sure that the /sbin/udevadm binary gets included,
* and your scripts changed to use it,as it replaces the
* old helper apps udevinfo, udevtrigger, ...
*
* mount options for directory /dev are no longer
* set in /etc/udev/udev.conf, but in /etc/fstab
* as for other directories.
*
* For more information on udev on Gentoo, writing udev rules, and
* fixing known issues visit:
* http://www.gentoo.org/doc/en/udev-guide.xml
Auto-cleaning packages...
No outdated packages were found on your system.
* GNU
