From: arnold@skeeve.com
To: tuhs@tuhs.org, robpike@gmail.com
Subject: [TUHS] Re: forgotten versions
Date: Fri, 17 Jun 2022 04:52:51 -0600 [thread overview]
Message-ID: <202206171052.25HAqpsm023417@freefriends.org> (raw)
In-Reply-To: <CAKzdPgytk74NekqE1gj2jjDAiKfRSONjuad3gSrZToQCwHmE3g@mail.gmail.com>
Rob Pike <robpike@gmail.com> wrote:
> Excited as I was to see this history of Unix code in a single repository:
>
> https://github.com/dspinellis/unix-history-repo
>
> it continues the long-standing tradition of ignoring all the work done at
> Bell Labs after v7. I consider v8 v9 v10 to be worth of attention, even
> influential,
I can think of at least 4 things, some big, some small, where post-V7
Research Unix was influential:
- Streams (as STREAMS in S5R3 & greater)
- The filesystem switch (in S5R3, replaced by Sun vnodes in S5R4)
- /proc ! This lives on in most Unixes and in Linux
- /dev/{stdin,stdout,stderr}, /dev/fd/N - Minor but a nice generalization
The influence was less from code and more from published papers, but
there certainly was a notable influence.
I was lucky enough in the late 80s and 90s to have an inside friend
in the labs (BWK), who was kind enough to obtain for me a real printed
Eighth Edition manual. Later he put me in touch with Doug who at first
wasn't sure, but found out that the could, sell me a Ninth Edition
manual. ($50 IIRC). I bought the published Tenth Edition manuals as well.
It was great to read those things, even if at the time I couldn't
get to the code.
For whatever it's worth,
Arnold
next prev parent reply other threads:[~2022-06-17 10:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
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 16:23 ` [TUHS] Sockets vs Streams (was " Bakul Shah
2022-06-17 17:43 ` [TUHS] " Paul Winalski
2022-06-17 22:52 ` Dan Stromberg
2022-06-17 7:20 ` [TUHS] " Diomidis Spinellis
2022-06-17 7:33 ` Rob Pike
2022-06-17 8:34 ` arnold
2022-06-17 10:52 ` arnold [this message]
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
2022-06-17 14:50 Paul Ruizendaal
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
2022-06-18 17:18 ` Warner Losh
2022-06-18 17:57 ` Clem Cole
2022-06-18 19:55 Paul Ruizendaal
2022-06-22 12:06 Noel Chiappa
2022-06-23 0:02 ` Dan Cross
2022-06-23 2:18 Noel Chiappa
2022-06-24 6:47 Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45 ` Paul Ruizendaal
2022-06-27 0:57 ` Kevin Bowling
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=202206171052.25HAqpsm023417@freefriends.org \
--to=arnold@skeeve.com \
--cc=robpike@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).