Volker Armin Hemmann <volkerar...@googlemail.com> writes: >> >> On next boot, the problem with hal daemon reported above started. > > and you did etc-update/cfg-update after the update? Have you read the > messages > with elogv? Same hal versions here - no problems at all.
I've completed the cfg-update -u and there was only one file really changed. sshd_config which I left alone. However I did remember to make sure the package I had trouble with `glibc' did get installed. It did not and will not. Ending with this stuff below... I'm not at all sure what to make of it. Is it related to hal daemon problem? emerge -vuD glibc [...] usr/lib/libc_nonshared.a >>> Completed installing glibc-2.9_p20081201-r2 into >>> /var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE "/var/log/sandbox/sandbox-15179.log" VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /etc/ld.so.cache~ A: /etc/ld.so.cache~ R: /etc/ld.so.cache~ C: /var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/work/build-default-i686-pc-linux-gnu-nptl/elf/ldconfig -r /var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/image /lib /usr/lib -------------------------------------------------------------------------------- >>> Failed to emerge sys-libs/glibc-2.9_p20081201-r2, Log file: >>> '/var/tmp/portage/sys-libs/glibc-2.9_p20081201-r2/temp/build.log'
