From: Clem Cole <clemc@ccc.com>
To: Adam Thornton <athornton@gmail.com>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Sat, 18 Jun 2022 12:58:02 -0400 [thread overview]
Message-ID: <CAC20D2PxpdV8qObnyq9Esoru0qPAu0AwjY5+vRfVZZFS+_xA6w@mail.gmail.com> (raw)
In-Reply-To: <33F19BA1-6F43-4B0A-AC9F-D57FBB30675E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
TUHS Source Archive BTL Research Distributions
<https://streaklinks.com/BF0jaowo6HdJanOkuwoN8MED/https%3A%2F%2Fwww.tuhs.org%2FArchive%2FDistributions%2FResearch%2F>
you should find them all.
ᐧ
On Sat, Jun 18, 2022 at 1:13 AM Adam Thornton <athornton@gmail.com> wrote:
> Could users outside Bell Labs actually get their hands on post-v7 Research
> Unixes?
>
> It was always my impression that The Thing You Could Get From The Phone
> Company, after v7, was System III or System V. Obviously it's not
> surprising that Research Unix features from later versions ended up in
> SysV, but did anyone actually learn about them from v8-v10, or just by way
> of SysV ?
>
> Was there some (legal) mechanism for the post-v7 Unixes to get out into
> people's hands?
>
> Adam
[-- Attachment #2: Type: text/html, Size: 1454 bytes --]
next prev parent reply other threads:[~2022-06-18 16:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-06-18 17:18 ` Warner Losh
2022-06-18 17:57 ` Clem Cole
2022-06-19 20:46 ` [TUHS] RFS (was Re: Re: forgotten versions) Derek Fawcus
2022-06-19 23:07 ` [TUHS] " Larry McVoy
2022-06-19 23:19 ` Brad Spencer
2022-06-20 5:03 ` Arno Griffioen via TUHS
2022-06-20 6:53 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2022-06-24 6:47 [TUHS] Re: forgotten versions 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-22 12:06 Noel Chiappa
2022-06-23 0:02 ` Dan Cross
2022-06-18 19:55 Paul Ruizendaal
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=CAC20D2PxpdV8qObnyq9Esoru0qPAu0AwjY5+vRfVZZFS+_xA6w@mail.gmail.com \
--to=clemc@ccc.com \
--cc=athornton@gmail.com \
--cc=douglas.mcilroy@dartmouth.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).