Larry,
I had to laugh when I read that because what you don't know is it was part of my old Unix wizards test which was left over from a the day when one of our hackers (whom I think you would later get to know so I'll not name him) accidentally typed: rm -rf . as root from his / on his workstation.
Because /bin/rmdir had been lost, he started getting errors when rmdir was forked. So he hit ^C, but he had already lost: /bin, /dev, /etc, /lib, most of /usr. He was a developer in the networking group so he was working on network code which we could not trust would not panic (in fact we disconnected the node from the ethernet immediately just in case). But we did have pretty much everything in /usr/bin/[s-z]* -- that is we think it was deleting files in /usr/bin when he stopped it.
We obviously had another working Masscomp box just like it. And of course the shell was working on the machine that was in trouble. We recovered the system as it was. Hint the key item is you have to start by putting /dev back together and the solution to that problem has had been discussed on this list.
Clem