The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: stewart@serissa.com (Lawrence Stewart)
Subject: [TUHS] PDP-11 questions
Date: Mon, 25 Jan 2016 08:38:46 -0500	[thread overview]
Message-ID: <03E1D761-B709-4C60-92C3-2604EEB3BE01@serissa.com> (raw)
In-Reply-To: <97567D49-FEE0-4F31-9FC5-CD63062E788D@ccc.com>

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

Regarding the 11/34.

We had one at the Stanford Information Systems Lab sometime in 78 or 79, running (I think) V7, and we certainly didn’t do the port ourselves!  We did put it on the Arpanet though, as SU-ISL.  This
was a pretty weird hookup.  The NCP ran on a front-end LSI-11 (or was it an 11/23?) and there was
a Very Distant Host interface home-built by Ron Crane that ran over a copper pair to the IMP at the medical school.  I did the driver work to connect the 11/34 to the smaller 11 running the NCP.

It is kind of funny to say “smaller” when the thing you are smaller than is an 11/34.

The other thing I remember about that system is that we had a version of “ed” with an added command
that was sort of like .-10,.+10p for displaying the local context.

By the time I graduated in 1981 we had an 11/70, which was just awesome.  With the split I and D space you could programs which were (or seemed to be!) enormous.

-L



  reply	other threads:[~2016-01-25 13:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 17:37 Mark Longridge
2016-01-24 18:06 ` [TUHS] [Bulk] " Mark Green
2016-01-24 18:49 ` [TUHS] " Clem Cole
2016-01-25  3:16   ` Dave Horsfall
2016-01-25  5:32     ` Warren Toomey
2016-01-25 12:27       ` Clem cole
2016-01-25 13:38         ` Lawrence Stewart [this message]
2016-01-25 14:15           ` Clem Cole
2016-01-26 19:52         ` Dave Horsfall
2016-01-26 20:41           ` Clem Cole
2016-01-24 18:01 Noel Chiappa
2016-01-24 18:30 Noel Chiappa
2016-01-24 18:36 ` Ronald Natalie
2016-01-24 21:10   ` John Cowan
2016-01-25  0:11 ` scj
2016-01-25  0:36   ` Clem cole
     [not found] <mailman.25.1453658502.15972.tuhs@minnie.tuhs.org>
2016-01-24 18:34 ` Johnny Billquist
2016-01-24 18:56 Noel Chiappa
2016-01-24 22:40 Norman Wilson
2016-01-25  0:23 ` Ronald Natalie
2016-01-24 22:40 Norman Wilson
2016-01-25  1:55 ` David Ritchie
2016-01-25  1:59   ` Ronald Natalie
2016-01-25  2:14   ` Clem cole
2016-01-25 11:29 ` Tony Finch
2016-01-25 13:25   ` Ronald Natalie
2016-01-25 16:18   ` Pete Turnbull
2016-01-25 19:37     ` Clem Cole
2016-01-25  1:11 Noel Chiappa
2016-01-25  1:30 ` Clem cole
     [not found] <mailman.29.1453684304.15972.tuhs@minnie.tuhs.org>
2016-01-25  3:07 ` Johnny Billquist
2016-01-25  3:09 ` Johnny Billquist
2016-01-25 12:54   ` John Cowan
2016-01-25 13:09     ` Johnny Billquist
2016-01-25 13:49     ` Johnny Billquist
2016-01-25 16:00       ` John Cowan
2016-01-25 16:17         ` Johnny Billquist
2016-01-25 16:43           ` John Cowan
2016-01-26 19:36 Doug McIlroy
2016-01-26 19:59 ` Warren Toomey
2016-01-26 20:07 Doug McIlroy
2016-01-26 20:44 ` Clem Cole

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=03E1D761-B709-4C60-92C3-2604EEB3BE01@serissa.com \
    --to=stewart@serissa.com \
    /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).