Something similar happened a place I worked somewhere between 10 and 20 years ago.
Service technician did not see the . in the command
rm -rf ./bin
so he proceeded to run
rm -rf /bin
When that didn't work he did what everyone who knows a little bit Linux does and added sudo in front.
I was on a terminal from the other side of the globe when the server suddenly started acting weird.
We were able to use scp or rsync (one of then was in sbin or something) to get back the bits from an identical server, which saved me from three days of tedious work :-)
In hindsight of course we should have written the docs in a way that would prevent this exact situation but in the beginning it was just the output of the history command after I had done it, dumped into a document with some explanations.
Service technician did not see the . in the command
so he proceeded to run When that didn't work he did what everyone who knows a little bit Linux does and added sudo in front.I was on a terminal from the other side of the globe when the server suddenly started acting weird.
We were able to use scp or rsync (one of then was in sbin or something) to get back the bits from an identical server, which saved me from three days of tedious work :-)
In hindsight of course we should have written the docs in a way that would prevent this exact situation but in the beginning it was just the output of the history command after I had done it, dumped into a document with some explanations.