after doing a "emerge -e world" more than once I found it would stop after bash. Then I would get the error on "sh" missing. Sure enough it was gone from "/bin" so I created a new symlink. I restarted "emerge -e world" and after bash again the link disappeared preventing it from doing the "emerge -e world" past bash. Realizing I wasn't going to get far I had to manually remerge my world file as some things seemed to be missing after using the "emerge -e world" command. Also the odd thing wouldn't compile after the "emerge -e world" failure.(luckily most of those things that wouldn't seem to still be installed) Reproducible: Always Steps to Reproduce: 1. emerge -e world 2. or maybe trying just a bash recompile(I've not attempted this only the prior command) 3. Actual Results: After "emerge -e world" things stop after the bash emerge is complete with a "/bin/sh" missing error. Expected Results: "emerge -e world" should of just recompiled all existing packages in my world file and thier dependancies and installed them all.
what portage version?
please paste #emerge info
It was the one r9 I believe. I've solved the problem now by doing the following: emerge rsync && emerge portage && etc-update updatedb && emerge -e world Since doing that I've not had the same problem. I'm not sure what caused the glitch as the last portage update I had prior I did do etc-update and accept the new globals.make keeping my original make.conf.
closing
