From: dfevans@sekrit.eu (David Evans)
Subject: [TUHS] AT&T Blit terminal plus terminal OS
Date: Mon, 15 Oct 2012 07:53:49 +0100 [thread overview]
Message-ID: <CAA2FD31-B6F9-4AA8-923B-AC06FB5D945C@sekrit.eu> (raw)
In-Reply-To: <5782C16A7C920E469B74E11B5608B8E723B14598@Kriegler.ntdom.cupdx>
On 14 Oct 2012, at 21:21, Benjamin Huntsman <BHuntsman at mail2.cu-portland.edu> wrote:
> Like this: http://www.flickr.com/photos/87479714 at N05/8087576305/
>
Alas those of us who came along 8 or so years later had only the DEC VSXXX to enjoy.
next prev parent reply other threads:[~2012-10-15 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 9:58 Wesley Parish
2012-10-14 10:32 ` Wilko Bulte
2012-10-14 10:48 ` arnold
2012-10-14 10:54 ` arnold
2012-10-14 18:16 ` Brian Zick
2012-10-14 18:47 ` Brantley Coile
2012-10-14 20:21 ` Benjamin Huntsman
2012-10-14 23:00 ` scj
2012-10-15 0:24 ` Larry McVoy
2012-10-15 1:08 ` Gregg Levine
2012-10-15 9:10 ` Peter Jeremy
2012-10-14 23:14 ` Brian Zick
2012-10-15 6:53 ` David Evans [this message]
2012-10-15 6:46 ` [TUHS] AT&T video : the UNIX system (1982) Pierre DAVID
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=CAA2FD31-B6F9-4AA8-923B-AC06FB5D945C@sekrit.eu \
--to=dfevans@sekrit.eu \
/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).