First off all, thank you all for gentoo, i really like it !
This morning (04/07/02) I tried to emerge KDE-3.0.2. After doing "emerge
--clean rsync" at 07:50 I did "emerge -u kde", and went to work. When I got
back from work my system had crashed. That crash wrecked my XFS partitions. By
using my portage install CD I used xfs_repair to get the partition working
again, however I lost some clusters and portage (2.0.9) got broken. my
/var/cache directory appears to be fine (found nothing in /lost+found).
So i used /usr/portage/sys-apps/portage/files/portage-rescue-1.8.19.tbz2 to get
portage working again. This worked (had to modify make.conf to work with
current mirror setup). However, when i tried to emerge portage-2.0.9 back,
emerge locked up. It was was sandbox that took 100% cpu usage and appeard to be
in an endless-loop. Removed /etc/ld.so.preload, touched it back. Found out I
had to change FEATURE="sandbox" to FEATURE="" in /etc/make.globals. Managed to
get portage 2.0.9 installed again. Copied the ._cfg make files to
/etc/make.conf and /etc/make.globals.
Tried emerge portage again (paranoia is good ;]), but again the sandbox locked
up. Disabled the FEATURE setting again and emerge works ... but i assume the
FEATURE="sandbox" should be implace, so ... any ideas ?
btw, been using gentoo since rc6 ... been upgrading weekly since then... how do
i find out what my current gentoo version is ?
fixed it ... removed /tmp/sandboxpids.tmp ... portage now works with
thanks anyway ;]