The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Was curses ported to Seventh Edition Unix?
Date: Sat, 25 May 2024 12:21:17 -0400	[thread overview]
Message-ID: <CAC20D2M2jLFZNhNJQsJpSzKasSftTRafSscG_4SeT0pY0jbANg@mail.gmail.com> (raw)
In-Reply-To: <20240525161320.3jvozzlgvr6tfyxl@illithid>

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

On Sat, May 25, 2024 at 12:13 PM G. Branden Robinson <
g.branden.robinson@gmail.com> wrote:

> That does complicate my simplistic story.  Ing70 was, then, as you noted
> in a previous mail, an 11/70, but it _wasn't_ running Version 7 Unix,
> but rather something with various bits of BSD (also in active
> development, I reckon).
>
Mumble -- the kernel and 90% of the userspace on Ing70 was V7 -- it was
very similar to Teklabs which I ran.
It had all of 2BSD on it, but the kernel work that we think of as 'BSD" was
3.0BSD and later 4.0BSD and that was 100% on the Vax.

The point is it was a 16 bits system, the Johnson C compiler with some
fixes from the greater USENIX community including UCB.
There was >>no port<< needed.

This was its native tongue.

It was >>included<< in later BSD released which is how people came to know
it because 4.XBSD was became much more widely used than V7+2BSD.

The 2.9 work of Keith at al, started because the UCB Math Dept could not
afford a VAX.   DEC had released the  v7m code to support overlays, so
slowly
changed from the VAX made it back into the V7 based kernel - which took a
new life.

Clem




ᐧ

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

  reply	other threads:[~2024-05-25 16:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25  0:03 [TUHS] " G. Branden Robinson
2024-05-25  0:46 ` [TUHS] " Clem Cole
2024-05-25  0:57   ` G. Branden Robinson
2024-05-25 10:48 ` Jonathan Gray
2024-05-25 11:08   ` Arrigo Triulzi via TUHS
2024-05-25 12:16   ` Clem Cole
2024-05-25 23:06     ` Rob Pike
2024-05-25 15:06   ` [TUHS] " Douglas McIlroy
2024-05-25 15:11     ` [TUHS] " Rich Salz
2024-05-25 15:40       ` Clem Cole
2024-05-25 15:43         ` Clem Cole
2024-05-25 15:51         ` Clem Cole
2024-05-25 15:57         ` G. Branden Robinson
2024-05-25 16:06           ` Clem Cole
2024-05-25 16:13             ` G. Branden Robinson
2024-05-25 16:21               ` Clem Cole [this message]
2024-05-25 16:38                 ` G. Branden Robinson
2024-05-25 17:02                   ` Warner Losh
2024-05-25 16:14             ` Clem Cole
2024-05-25 16:25               ` G. Branden Robinson
2024-05-25 18:07               ` Adam Sampson
2024-05-27 18:31                 ` Mary Ann Horton
2024-05-25 15:28     ` G. Branden Robinson
2024-05-25 17:24 Steve Simon

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=CAC20D2M2jLFZNhNJQsJpSzKasSftTRafSscG_4SeT0pY0jbANg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=g.branden.robinson@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).