17 Sep
2019
17 Sep
'19
1:36 a.m.
Btw. This was some I used as a wizards test.
You have a working system next to a system that is still running so you have the console
and its shell but had the rm -fr / done to it. You have lost all of bin dev etc and lib
by the time he hit ^C. So you have some of /usr inc but much of /usr/bin is still there.
No compiler or assembler on the broken machine since that was in bin and lib.
It’s possible to fix it using the other system to help. Just don’t turn the damaged
system off 🍺
Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite.
On Sep 16, 2019, at 9:17 PM, Larry McVoy
<lm(a)mcvoy.com> wrote:
On Mon, Sep 16, 2019 at 09:11:17PM -0400, Arthur
Krewat wrote:
I think we have all been there. Something always goes wrong. I wrote
a paper about how to restore a Masscomp because I did rm -rf . in /.
I believe we had roots home as / because /usr was a different partition.
Clem, did Masscomp make roots home / or was that us? Anyway, I did a
cd something
and somehow deleted the something and then did rm -rf .
Much fun was had, I was up all night putting things back together.
This was probably around 1984 or 1985, I was pretty green. On 9/16/2019 8:20 PM, Steve Johnson wrote:
One day I had been furiously editing a long program file for about an hour
and a half when I was called away to lunch, and, being hungry, didn't save
my file.?? When I got back to the terminal an hour later, I discovered two
things -- the system had crashed, and our cat had decided that the pile of
paper
on the floor made a great litter box.?? After a few choice words, I sighed
and picked up my highliter...
This should be engraved on a plaque somewhere. Only because I had almost the
same thing happen to me, without the cat though. I had a printout of a
"mail" program I had written on TOPS-10 at high school. I had to retype the
entire thing after the file got corrupted.