The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Wed, 22 Jun 2022 20:02:55 -0400	[thread overview]
Message-ID: <CAEoi9W4pTJf-stA56pwN_FKDkz=CJivF7isjmeUiunUf1GCZCg@mail.gmail.com> (raw)
In-Reply-To: <20220622120623.A856A18C08D@mercury.lcs.mit.edu>

On Wed, Jun 22, 2022 at 8:06 AM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>     > From: Paul Ruizendaal
>
>     > [c]  Fifth Edition UNIX     PDP-11/40   June     1974
>     > [d]  Sixth Edition UNIX     PDP-11/45   May      1975
>     > [e]  Seventh Edition UNIX   PDP-11/70   January  1979
>
> This table gives an erroneous impression of which versions supported which
> PDP-11 models. 4th Edition supported only the /45; 5th Edition added support
> for the /40; and the /70 appeared in 6th edition.

I believe that's actually a menu, and that selecting from it will connect you to
an (emulated) machine of the given type running that version of the OS.
Stephen Jones and LCM+L set that up for the Unix 50th anniversary.

        - Dan C.

  reply	other threads:[~2022-06-23  0:03 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 12:06 Noel Chiappa
2022-06-23  0:02 ` Dan Cross [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-24  6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45   ` Paul Ruizendaal
2022-06-27  0:57     ` Kevin Bowling
2022-06-23  2:18 Noel Chiappa
2022-06-18 19:55 Paul Ruizendaal
2022-06-18  0:35 Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-18  5:13   ` Adam Thornton
2022-06-18 16:58     ` Clem Cole
2022-06-18 17:18       ` Warner Losh
2022-06-18 17:57         ` Clem Cole
2022-06-17 14:50 Paul Ruizendaal
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44   ` George Michaelson
2022-06-17  0:10     ` Larry McVoy
2022-06-17  7:20 ` Diomidis Spinellis
2022-06-17  7:33   ` Rob Pike
2022-06-17  8:34   ` arnold
2022-06-17 10:52 ` arnold
2022-06-18  7:05 ` Angelo Papenhoff
2022-06-19  7:50   ` Rob Pike
2022-06-19  8:17     ` Angelo Papenhoff
2022-06-19  8:53       ` Rob Pike
2022-06-19  9:02         ` Angelo Papenhoff
2022-06-19  9:14           ` arnold
2022-06-19  9:19             ` Angelo Papenhoff
2022-06-19  9:23               ` arnold
2022-06-19 11:37                 ` Matthias Bruestle
2022-06-19 14:47         ` Kenneth Goodwin
2022-06-19 16:27           ` Al Kossow
2022-06-19 18:32           ` Theodore Ts'o
2022-06-19 18:38             ` Dan Cross
2022-06-21 23:56               ` Jacob Moody
2022-06-22  0:13                 ` Larry McVoy
2022-06-22  0:48                   ` Rob Pike
2022-06-22  1:55                     ` George Michaelson
2022-06-22  2:10                       ` Bakul Shah
2022-06-22  2:14                       ` Jon Steinhart
2022-06-22  2:19                         ` Andrew Hume
2022-06-22  2:58                           ` Rob Pike
2022-06-22  3:09                             ` George Michaelson
2022-06-22  2:16                   ` Andrew Hume
2022-06-22  2:55                   ` Brad Spencer

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='CAEoi9W4pTJf-stA56pwN_FKDkz=CJivF7isjmeUiunUf1GCZCg@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).