From: Larry McVoy <lm@mcvoy.com>
To: George Michaelson <ggm@algebras.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Thu, 16 Jun 2022 17:10:34 -0700 [thread overview]
Message-ID: <20220617001034.GA27651@mcvoy.com> (raw)
In-Reply-To: <CAKr6gn1sOmfBu6v1SQSh=xOCD8XOt54=kVdEt4aD2zB5houS8A@mail.gmail.com>
On Fri, Jun 17, 2022 at 09:44:02AM +1000, George Michaelson wrote:
> v7 exploded into the world, and made BSD and SunOS happen.
>
> v8 and 9 and 10 had to work harder to get mindshare because something
> was already there.
I think this is spot on. v7 was pretty easy to find in src form, I know
I've seen some of v{8,9,10} in Shannon's treasure trove of Unix source
at Sun but they were less common.
> things like rc were too "confrontational" to a mind attuned to bourne
> shell. Sockets (which btw, totally SUCK PUS) were coded into things
> and even (YECHH) made POSIX and IETF spec status. Streams didn't stand
> a chance.
There was streams (from Dennis) and STREAMS from Sys whatever. I don't
know how great streams was, I read the paper and it seemed fine for a tty
driver, networking I dunno. And having seen an SGI SMP machine brought
to it's knees by racks and racks of modems, I'm not sure streams is even
a good idea for ttys; it's fine for a personal system, I've never seen
that sort of layered design perform well at scale. I have seen what a
networking stack in STREAMS did, it was awful, absolutely awful.
Sun bought the STREAMS networking stack from Lachman, same one that
I ported to the ETA 10 and SCO Unix, it sucked hard. Sun threw it out,
hired Mentat to give them a performant STREAMS stack, I'm not sure
that ever worked. I know they put back the socket interface, as much
as people don't like it, it's a non-starter to have an OS without it.
next prev parent reply other threads:[~2022-06-17 0:10 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 [this message]
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
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=20220617001034.GA27651@mcvoy.com \
--to=lm@mcvoy.com \
--cc=ggm@algebras.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).