Actually, this wouldn't really even be all that big of a problem in general. If you think about all the things that could have been deleted that would have been a lot harder to fix, you'll see that there's a lot worse that could happen. It's certainly a unique problem though.
if i never try anything, i never learn anything..
if i never take a risk, i stay where i am..
resolved by doing an installation on an other partition and after the bootstrap, I build the binutils package and installed it on the main installation......
Yeah, yeah, I thought it was funny too. The way it happened is I added a cron entry to delete a file every Thursday (... thu rm /home/file) and I edited it immediately after, wanting to give the entry the full path of rm (... thu /usr/bin/rm /home/file) but ended up inserting the command with path and accidentally left in the original rm (... thu rm /usr/bin/rm /home/file).
Needless to say, rm was deleted the first time cron ran the task. Put it down as a stupid user trick, but you can bet I won't do that again!
Thanks for the tip on the file-to-package search, AutoBot.
For everybodies info, the emerge of sys-apps/fileutils failed to restore rm - emerge crapped out because it needs rm to complete it's task! I had to copy an rm file from a Suse machine, and then ran the emerge again as a sanity check and everything is happy again. Sheesh, nice experience.