ABCD <en.a...@gmail.com> writes: >> 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/ >> > [snip sandbox error] > > That actually is completely separate, and is due to a bad version of > sandbox (if I'm not mistaken) - you probably need to either upgrade or > downgrade sys-apps/sandbox to 1.6-r2 (1.7 appears to be broken in this > regard). If I'm right, then this probably is bug 264399.
Thanks for the tip.. I'm now running a downgrade of both sandbox and hal from latest to immediately prior versions: sandbox-7.1 => sandbox-1.6-r1 hal-0.5.12_rc1 => hal-0.5.11-r8 Then I'll see if glibc will compile AND hal troubles go away. ===== * ===== * ===== * ===== .. Soon as the downgrading finished, I restarted hald and YIPPEE hal started up and my console login has a keyboard now. There was a suggestion that I remove the `input' section of xorg.conf and migrate it to some kind of file under: /etc/hal/fdi/ >From emerge of hal [...] * X Input Hotplugging (if you build xorg-server with the HAL useflag) * reads user specific configuration from /etc/hal/fdi/policy/. * You should remove the Input sections from your xorg.conf once you have * migrated the rules to a HAL fdi file. Anyone here that has done that, who can offer some guidance? What filenames .. what format, for example. I guess I'll be chicken of ~86 on hal and sandbox for now. .... Haa... glibc installed without a hitch. off and running.... thanks
