The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Berkeley 11/70 (was Re: Strange Reference on Usenix_77 tape)
Date: Thu, 22 Sep 2022 13:49:44 -0400	[thread overview]
Message-ID: <CAEoi9W6kmVnVHnOqJ=thhkt8JcG3DMq2Nqp6=L4HV7m1YKzMGQ@mail.gmail.com> (raw)
In-Reply-To: <7wczbnwdih.fsf@junk.nocrew.org>

On Thu, Sep 22, 2022 at 1:00 PM Lars Brinkhoff <lars@nocrew.org> wrote:
> Warner Losh wrote:
> >  > For those of us not involved with Unix in 1977, what was the
> >  > HRSTS system?
> >
> >  ‘The Harvard/Radcliffe Student Time-sharing System Terminal Users Guide,
> >   1st edition, September 10, 1974, Center for Research in Computing
> >   Technology, Harvard University’.
> >
> > These are the same folks that also did the LISP that appeared in
> > various 2BSD distributions as well.  There's a special C compiler.
>
> I found a description in a Usenix paper[1], and it really seems to be a
> lot of "Harvard specials" in there.  MACRO-11, LINK-11, DDT, TECO,
> FILCOM, shell with TENEX file completion, even ECL[2].  To me it looks
> like a layer of PDP-10 on top of Unix.
>
> [1] https://www.usenix.org/system/files/login/articles/login_june_11_unix_news.pdf
> [2] https://github.com/PDP-10/harvard-ecl

Thanks, that was very interesting. Indeed, it sounds like at attempt
to bring a TENEX-style user experience to Unix.

Also interesting was the short article about, "the Berkeley 11/70 System"
with notes from Ken.  The description of the UID scheme to separate
students from "regular" users and the note that "the group concept is
about to disappear" were particularly intriguing; clearly an evolutionary
dead end, but striking in that this must have yielded a much greater
level of isolation. Also, the note about per-directory quotas (as opposed
to per-user/group quotas) was interesting.

I wonder what other early attempts at hardening the system for
educational environments were made that similarly didn't make it
in the long haul, and to what extent such efforts have survived?

        - Dan C.

  reply	other threads:[~2022-09-22 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  8:26 [TUHS] Strange Reference on Usenix_77 tape Warner Losh
2022-09-22  8:42 ` [TUHS] " arnold
2022-09-22  9:00   ` Ralph Corderoy
2022-09-22 16:13     ` Warner Losh
2022-09-22 17:00       ` Lars Brinkhoff
2022-09-22 17:49         ` Dan Cross [this message]
2022-09-22 20:38         ` Clem Cole
2022-09-24  3:54           ` Warner Losh

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='CAEoi9W6kmVnVHnOqJ=thhkt8JcG3DMq2Nqp6=L4HV7m1YKzMGQ@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=lars@nocrew.org \
    --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).