From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] V8, V9 and V10 now in the "Unix Tree"
Date: Sat, 11 Apr 2020 11:24:03 -0400 (EDT) [thread overview]
Message-ID: <20200411152403.5CB384422F@lignose.oclsc.org> (raw)
Doug McIlroy:
The v8 manual was printed in 1985, but the system was
not "released" in the ordinary sense until a couple of
years ago. Some v8 features made it out into the world
via USG; some were described in open literature or
Usenix presentations, but I believe none were formally
shipped out of the company.
I'm surprised; I thought copies of the V8 manual existed
when I arrived at the Labs in mid-1984, but the date on
the title page is indeed February 1985.
There was no general release of V8 like those for earlier
Research systems, but there was a quasi-official V8 tape
sent to a handful of universities under a special letter
agreement. I remember working on that with Dennis,
checking that everything compiled and worked properly
in a chroot environment before the tape was written.
I think that happened in the summer of 1985.
I don't remember our doing that work, to make a single
coherent consistency-checked release tape, for any
subsequent system; just one-off caveat-emptor snapshots.
Norman Wilson
Toronto ON
next reply other threads:[~2020-04-11 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:24 Norman Wilson [this message]
2020-04-11 18:49 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2020-04-12 9:30 Paul Ruizendaal
2020-04-12 10:00 ` Rob Pike
2020-04-12 9:26 Paul Ruizendaal
2020-04-11 15:38 Norman Wilson
2020-04-11 15:44 ` Larry McVoy
2020-04-11 18:52 ` arnold
2020-04-11 14:47 Doug McIlroy
2020-04-10 15:34 Paul Ruizendaal
2020-04-10 20:50 ` Rob Pike
2020-04-12 8:51 ` Paul Ruizendaal
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=20200411152403.5CB384422F@lignose.oclsc.org \
--to=norman@oclsc.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).