Let me begin by mentioning Ive already found a workaround for this problem. Twice in the last week, during an --update world the kernel has cored on me, thats not the problem though. When I hit reset to restart the box, very earlu in the boot process boot fails with a message stating that it cant load libsandbox.so. It seems to happen close to / getting mounted read-only on the first pass. The solution to this is to rename or delete /etc/ld.so.preload which contains the path to libsandbox.so while emerge is running. Then the box will reboot normally. this is probably happening because I have /usr mounted on its own partition. So maybe /usr isnt avail at that point in the boot process. Is this a bug? Shouldn't files that are required at boottime reside somewhere on /. or maybe shouldnt the init script thats loading libsandbox.so wait till after everything in fstab is mounted? BTW Gentoo is great! Im almost ready to give up FreeBSD on my other box. ;)
Geert: I think we may need a fix for this problem in our boot-scripts (detect and remove ld.so.preload) -- What do you think? Please work this out with Azarah :)
Az, If I remember right, this got sorted out a while ago. Punting to you to make sure.
Daniel still needs to merge in all the bits of the changes I did for this to work properly.
Ok, these two things have been done to fix: 1) libsandbox.so was moved to /lib 2) Fine grained calling of the sandbox, with detection if its running or not in the exception handler, with the then appropriate deleting of /etc/ld.so.preload (if no other sandbox running) was added to portage. These should fix both the boot problems, as well as portage sometimes just dieing due to a missing /etc/ld.so.preload.
