Hello list, I'm wearying of this chroot operation, and I must be sounding like a tyro.
The other day emerge started hanging at the end of compilation, thus: # emerge -1 apache-tools [,,,] make[1]: Leaving directory `/var/tmp/portage/app-admin/apache- tools-2.2.25/work/httpd-2.2.25/support' >>> Source compiled. * Skipping make test/check due to ebuild restriction. >>> Test phase [disabled because of RESTRICT=test]: app-admin/apache- tools-2.2.25 >>> Install apache-tools-2.2.25 into /var/tmp/portage/app-admin/apache- tools-2.2.25/image/ category app-admin make[1]: Entering directory `/var/tmp/portage/app-admin/apache- tools-2.2.25/work/httpd-2.2.25/support' mkdir /var/tmp/portage/app-admin/apache-tools-2.2.25/image/usr mkdir /var/tmp/portage/app-admin/apache-tools-2.2.25/image/usr/sbin make[1]: Leaving directory `/var/tmp/portage/app-admin/apache- tools-2.2.25/work/httpd-2.2.25/support' >>> Completed installing apache-tools-2.2.25 into /var/tmp/portage/app- admin/apache-tools-2.2.25/image/ strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version usr/sbin/htpasswd usr/sbin/ab usr/sbin/rotatelogs usr/sbin/logresolve usr/sbin/htdigest usr/sbin/htdbm usr/sbin/htcacheclean usr/sbin/httxt2dbm usr/sbin/checkgid >>> Done. It never comes back from there, not even with a CTRL-C; I have to "kill -9" from another Konsole. Grepping ps for emerge (before the kill!) shows: 20749 pts/1 DN+ 0:03 /usr/bin/python3 /usr/bin/emerge --nospinner -1 apache-tools Man ps says that the D means "uninterruptible sleep (usually IO)" So far I've done these things: 1. Wiped the whole system and restored from backup (heavy overkill, but I wanted everything to be in the same, consistent state). 2. Run bad-blocks tests on all partitions (though all but / and /boot are in logical volumes - I don't know to what extent that will have affected the results). 3. Remerged portage. 4. Recompiled the kernel, 3.12.13. 5. Booted previous good kernel,3.10.32. 6. Emerged natively on the Atom box for which the chroot is a build host. At various stages I got bizarreness like the kernel panicking at boot on a previously good kernel config, before it even switched to the frame buffer; or, during shutdown, "exiting from KVM" or some such, even though I've never used KVM. Portage works fine outside the chroot and is at the same version, 2.2.8-r1. It has python3 set in package.use in both cases, so I also tried: 7. Removed python3 USE flag from sys-apps/portage. Is my hardware dying? Or maybe I am. Time to seek intelligent conversation down the pub. :-( -- Regards Peter
