The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Ed Bradford <egbegb2@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] PC Unix (had been How to Kill a Technical Conference
Date: Sat, 10 Apr 2021 11:12:51 -0400	[thread overview]
Message-ID: <CAC20D2OezDnq=Pg+vVyMb5bbJSFWOVS_G4TVYQU3dJBMZiZ3Ww@mail.gmail.com> (raw)
In-Reply-To: <CAHTagfGgBTgbaXNNe1AnAfARppnzBp=0HPiW2Sdku7W_qpLP=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]

On Fri, Apr 9, 2021 at 11:34 PM Ed Bradford <egbegb2@gmail.com> wrote:

> Why did a Ph.D., an academic, and a computer scientist not know about UNIX
> in 1974 or so? 1976? In 1976, some (many?) universities had source code.
>

Some knowns/givens at the time ...
1.) He was a language/compiler type person -- he had created PL/M and that
was really what he was originally trying to show off.  As I understand it
and has been reported in other interviews, originally CP/M was an attempt
to show off what you could do with PL/M.
2.) The 8080/Z80 S-100 style machines we quite limited, they had very
little memory, no MMU, and extremely limited storage in the 8" floppies
3.) He was familiar with RT/11 and DOS-11, many Universities had it on
smaller PDP-11s as they ran on an 11/20 without an MMU also with limited
memory, and often used simple (primarily tape) storage (DECtape and
Cassette's) as the default 'laboratory' system, replacing the earlier PDP-8
for the same job which primarily ran DOS-8 in those settings.
4.) Fifth and Sixth Edition of Unix was $150 for university but to run it,
it took a larger at least 11/40 or 45, with a minimum of 64Kbytes to boot
and really need the full 256Kbytes to run acceptably and the cost of a 2.5M
byte RK05 disk was much greater per byte than tape -- thus the base system
it took to run it was at least $60K (in 1975 dollars) and typically cost
about two to four times that in practice.   Remember the cost of
acquisition of the HW dominated many (most) choices.

*I**'ll take a guess, but it is only that.*  I *suspect* he saw the S-100
system as closer to a PDP-11/20 'lab' system than as a small
timesharing machine.  He set out with CP/M to duplication the functionality
from RT/11.  He even the naming of the commands was the same as what DEC
used (*e.g.* PIP) and used the basic DEC style command syntax and parsing
rules.




>
> Bill Joy, where are you?
>
Some of us, know how to find him.  I know that at least at one time,
was made aware of this mailing list and have been invited to join it.  It
is his choice to not be a part.
ᐧ

[-- Attachment #2: Type: text/html, Size: 4830 bytes --]

  reply	other threads:[~2021-04-10 15:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 15:35 M Douglas McIlroy
2021-04-06 17:09 ` Clem Cole
2021-04-06 17:32   ` Charles H Sauer
2021-04-06 20:11     ` Josh Good
2021-04-06 20:26       ` Jim Capp
2021-04-06 20:47         ` Charles H Sauer
2021-04-07 16:42           ` Josh Good
2021-04-07 18:04             ` Charles H. Sauer
2021-04-07  2:49         ` Dave Horsfall
2021-04-07  6:04         ` arnold
2021-04-07 16:01           ` heinz
2021-04-06 21:06       ` Clem Cole
2021-04-07  0:58     ` heinz
2021-04-07  1:37       ` Warner Losh
2021-04-07  3:38         ` Dave Horsfall
2021-04-07  2:30     ` Ed Bradford
2021-04-07  2:44       ` Charles H. Sauer
2021-04-06 20:20   ` Boyd Lynn Gerber
2021-04-06 22:41 ` Dave Horsfall
2021-04-07  1:10   ` Jon Steinhart
2021-04-07  1:47     ` Greg 'groggy' Lehey
2021-04-07  1:49       ` Jon Steinhart
2021-04-07  1:58         ` Larry McVoy
2021-04-07  2:31           ` Serge Burjak
2021-04-09 21:24   ` Michael Parson
2021-04-10  3:33     ` Ed Bradford
2021-04-10 15:12       ` Clem Cole [this message]
2021-04-10 15:41         ` Larry McVoy
2021-04-07  0:59 Jason Stevens
2021-04-10 18:12 Paul Ruizendaal via TUHS

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='CAC20D2OezDnq=Pg+vVyMb5bbJSFWOVS_G4TVYQU3dJBMZiZ3Ww@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=egbegb2@gmail.com \
    --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).