The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] wizards test [was roff]
Date: Mon, 16 Sep 2019 21:38:19 -0400	[thread overview]
Message-ID: <FF982C0E-8477-4848-84AE-E140FF17CB43@ccc.com> (raw)
In-Reply-To: <1583C418-2F6E-45D8-93C2-B93032E6CFFC@ccc.com>

I should say you have a root shell on the broken system which why it killed every thing. 

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On Sep 16, 2019, at 9:36 PM, Clem cole <clemc@ccc.com> wrote:
> 
> 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@mcvoy.com> wrote:
>>> 
>>>> On Mon, Sep 16, 2019 at 09:11:17PM -0400, Arthur Krewat wrote:
>>>> 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.
>> 
>> 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.

  reply	other threads:[~2019-09-17  1:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 22:07 [TUHS] earliest Unix roff Doug McIlroy
2019-09-17  0:20 ` Steve Johnson
2019-09-17  1:11   ` Arthur Krewat
2019-09-17  1:17     ` Larry McVoy
2019-09-17  1:26       ` Clem cole
2019-09-17  1:33         ` Larry McVoy
2019-09-17 22:39           ` Dave Horsfall
2019-09-17  1:36         ` Richard Salz
2019-09-17  1:36       ` [TUHS] wizards test [was roff] Clem cole
2019-09-17  1:38         ` Clem cole [this message]
2019-09-17  2:34         ` Larry McVoy
2019-09-17  1:57       ` [TUHS] earliest Unix roff Bakul Shah
2019-09-17  1:11   ` [TUHS] Model 37's Ronald Natalie
2019-09-17  1:19   ` [TUHS] earliest Unix roff Bakul Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FF982C0E-8477-4848-84AE-E140FF17CB43@ccc.com \
    --to=clemc@ccc.com \
    --cc=lm@mcvoy.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).