The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [pups] PDP-9?
Date: Sun, 01 Sep 2002 21:54:57 -0400	[thread overview]
Message-ID: <200209020155.g821tUD64136@minnie.tuhs.org> (raw)

Dave Horsfall:

  AFAIK, Unix never ran on the 11/20 (no MM unit); did you mean a DEC-20?

I don't know if it was called an 11/20 at the time (I seem to recall
some model-number upheaval in the early days of the -11), but the first
PDP-11 UNIX system was certainly one without memory management:

  By the beginning of 1970, PDP-7 UNIX was a going concern ... In early
  1970 we proposed acquisition of a PDP-11, which had just been introduced
  by Digital ... to create a system specifically designed for editing and
  formatting text, what might today be called a `word-processing system.'
  ... During the last half of 1971, we supported three typists from the
  Patent Department, who spent the day busily typing, editing, and formatting
  patent applications, and meanwhile tried to carry on our own work.  UNIX
  has a reputation for supplying interesting services on modest hardware,
  and this period may mark a high point in the benefit/equipment ratio;
  on a machine with no memory protection and a single 0.5-MB disk, every
  test of a new program required care and boldness, because it could easily
  crash the system, and every few hours' work by the typists meant pushing
  out more information onto DECtape, because of the very small disk.

  The experiment was trying but successful.  Not only did the Patent
  Department adopt UNIX, and thus become the first of many groups at the
  Laboratories to ratify our work, but we achieved sufficient credibility
  to convince our own management to acquire one of the first PDP-11/45
  systems made.

Dennis M. Ritchie, Evolution of the UNIX Time-Sharing System; AT&T Bell
Labs Technical Journal, Vol. 63 No. 8 Part 2, October 1984.

Maybe Dennis will chime in with further memories.

Certainly there's nothing odd about UNIX running without memory protection,
though, especially in that era.  The PDP-7 had none.  The trick was that
every context switch was also a swap.  The scheme was revived in the late
1970s for the early, no-memory-map versions of the LSI-11 (called LSX and
later Mini-UNIX; paper by Lycklama et al in the 1978 all-UNIX BLTJ, I believe).

I suppose next some whippersnapper will express disbelief that UNIX
could have run on a system with no Ethernet interface.  You mean there
was life before 10BaseT, spam, and pornographic web sites?

(Not, to be fair, that Dave Horsfall is a whippersnapper.)

Norman Wilson
Toronto ON
(Still on the shelf, but crawling toward the edge)



             reply	other threads:[~2002-09-02  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  1:54 Norman Wilson [this message]
2002-09-07  1:49 ` Greg Lehey
  -- strict thread matches above, loose matches on Subject: below --
2002-09-02  7:13 Fred N. van Kempen
2002-09-02  8:00 ` Warren Toomey
     [not found] <Pine.BSI.4.44.0209021059540.21824-100000@eram.esi.com.au>
2002-09-02  1:38 ` Johnny Billquist
2002-08-18  9:43 Lars Buitinck
2002-08-18 18:04 ` Johnny Billquist

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=200209020155.g821tUD64136@minnie.tuhs.org \
    --to=norman@nose.cs.utoronto.ca \
    /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).