I found my box prompting "init-2.05a" on bootup. Almost everything runs fine, but init did not work. /sbin/init did not even exist! emerge baselayout and rebooting fixed this.
you're gonna have to give more information on what happened before we can help
Did you have "build" in your USE at some stage ?
I'm sorry - I don't *have* more information. The bootstapping process didn't print any obvious errors, although it clearly failed. There is no 'build' in $USE, and there never has been.
could you describe what you did then ?
Any more info ? I am sorry, but we will need more info, or how to recreate it, as I have done many bootstraps to test in the last few months, and have not run into this once.
With qpkg on another box, I found out that 'baselayout' contains init. Re-mounting rw allowed me to emerge baselayout, which fixed not only this, but also some other (unreported, because they seemed unimportant) oddities. Note that the bootstrapping process was done unattended (movies are great), and that the final 80x25 screen did not show any error.
I experienced a simular problem over this weekend. Steps to repro: $ emerge -u system # after not updating for a while $ shutdown -r now Notes: I fixed the problem checking all my files /etc/init.d/._cfg????* I was getting lazy and not checking my ._cfg* files and it appears that there was quite a few files that were moved from /sbin/ to /usr/sbin or something simular.
Not enouth info; cannot recreate.
