The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chris Torek <torek@elf.torek.net>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Surprised about Unix System V in the 80's - so sparse!
Date: Fri, 19 Mar 2021 10:27:23 -0700 (PDT)	[thread overview]
Message-ID: <202103191727.12JHRNW3025393@elf.torek.net> (raw)
In-Reply-To: <0C0895E9-0C26-44C9-93D0-DBFCE673A023@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

>Oh, and btw, seismo wasn’t uunet.

Yes, I was being deliberately vague with "they" here. :-)

>The original uunet was a sequent 8 processor box ( I believe ).

I'm not sure what was *original* but they definitely had a
Sequent.

> On Mar 18, 2021, at 10:27 PM, Chris Torek <torek@elf.torek.net> wrote:
> 
> We used to say: "Seismo bangs everybody"

Okay, who stuck a BOM into my email?

Chris

  reply	other threads:[~2021-03-19 17:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:33 Josh Good
2021-03-17 20:57 ` Adam Thornton
2021-03-17 21:04 ` Al Kossow
2021-03-17 21:38   ` Larry McVoy
2021-03-17 21:08 ` Jim Capp
2021-03-17 21:26 ` Larry McVoy
2021-03-17 21:29 ` Henry Bent
2021-03-17 21:40   ` Larry McVoy
2021-03-17 21:42   ` Henry Bent
2021-03-18  5:10   ` Wesley Parish
2021-03-18  1:15 ` [TUHS] XENIX or UNIX? (was: Surprised about Unix System V in the 80's - so sparse!) Greg 'groggy' Lehey
2021-03-18  1:21   ` George Michaelson
2021-03-20  0:12     ` Tony Finch
2021-03-18 23:05 ` [TUHS] Surprised about Unix System V in the 80's - so sparse! Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-03-19  1:45   ` Richard Salz
2021-03-19  2:01     ` Larry McVoy
2021-03-19  2:06       ` Chris Torek
2021-03-19  2:59         ` Earl Baugh
2021-03-19 17:27           ` Chris Torek [this message]
2021-03-17 23:18 M Douglas McIlroy
2021-03-17 23:22 ` George Michaelson
2021-03-18  1:23 ` Richard Salz

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=202103191727.12JHRNW3025393@elf.torek.net \
    --to=torek@elf.torek.net \
    --cc=tuhs@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).