From: dme@dme.org (David Edmondson)
Subject: [TUHS] Sockets and the true UNIX
Date: Thu, 21 Sep 2017 17:20:03 +0100 [thread overview]
Message-ID: <m2y3p8hvm4.fsf@dme.org> (raw)
In-Reply-To: <20170921161040.GC25650@mcvoy.com>
On Thursday, 2017-09-21 at 09:10:40 -0700, Larry McVoy wrote:
> I'm pretty sure the two main System V based TCP/IP stacks were STREAMS
> based: the Lachman one (which I ported to the ETA-10 and to SCO Unix)
> and the Mentat one that was done for Sun. The socket API was sort of
> bolted on top of the STREAMS stuff, you could get to the STREAMS stuff
> directly (I think, it's been a long time).
You could pop the socket module to get to the stream underneath, but
lots of streams functionality still works with it present.
dme.
--
Modern people tend to dance.
next prev parent reply other threads:[~2017-09-21 16:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 16:01 Ian Zimmerman
2017-09-21 16:07 ` Chet Ramey
2017-09-21 16:10 ` Larry McVoy
2017-09-21 16:20 ` David Edmondson [this message]
2017-09-21 16:25 ` Clem Cole
2017-09-21 16:27 ` Larry McVoy
2017-09-21 16:37 ` [TUHS] Sockets and the true UNIX [ actually carping about streams ] Jon Steinhart
2017-09-21 18:26 ` [TUHS] Sockets and the true UNIX Chet Ramey
2017-09-21 16:13 ` Jon Steinhart
2017-09-21 16:17 ` Larry McVoy
2017-09-21 20:36 ` Chris Torek
2017-09-21 18:56 ` Bakul Shah
2017-09-21 19:13 ` Steve Simon
2017-09-21 19:31 ` Bakul Shah
2017-09-21 20:15 ` ron minnich
2017-09-21 20:34 ` Clem Cole
2017-09-21 23:26 ` Dave Horsfall
[not found] <mailman.1105.1506026200.3779.tuhs@minnie.tuhs.org>
2017-09-22 10:36 ` Paul Ruizendaal
2017-09-22 14:32 ` Clem Cole
2017-09-22 14:42 ` Chet Ramey
2017-09-22 14:47 ` Chet Ramey
2017-09-22 14:52 ` Lars Brinkhoff
2017-09-22 14:49 ` Larry McVoy
2017-09-22 14:57 ` Chet Ramey
2017-09-22 18:14 ` Chris Torek
2017-09-22 18:43 ` Clem Cole
2017-09-22 19:08 ` Chet Ramey
2017-09-22 20:57 ` Chris Torek
2017-09-24 18:04 ` Chet Ramey
2017-09-22 18:00 ` Chris Torek
2017-09-25 17:57 Norman Wilson
2017-09-25 18:55 ` Clem Cole
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=m2y3p8hvm4.fsf@dme.org \
--to=dme@dme.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).