From: Rob Pike <robpike@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: segaloco <segaloco@protonmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: when did v8 or later get networking?
Date: Thu, 10 Aug 2023 13:18:36 +1000 [thread overview]
Message-ID: <CAKzdPgzmY6N8piPjnNwr3p2Rnz83Pdq=3yXYbz+x-H=bZ65Mrw@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfqj=j-0h1q4YN+S4bWfQbjYP5oRYWsnxp1283PpRVc55Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
STREAMS was the Unix support group's shouty adaptation. The V8 one that dmr
put together was the gentler dulcet-toned Streams.
Seriously, no one could figure out why they wanted to yell.
-rob
On Thu, Aug 10, 2023 at 12:46 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Wed, Aug 9, 2023, 8:38 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
>
>> > TCP/IP, not datakit.
>>
>> The V8 manual contains internet(3), tcp(3), and udp(3). In the copy I
>> have these are dated 8/7/85. Down in the kernel in /usr/sys/inet the
>> earliest files appear to be dated 3/22/85. I'm going to do a comparison
>> with the 4.1cBSD TCP/IP stuff because a casual glance reveals some overlap.
>>
>
> Yea, I thought it was 4.1bsd + later tcp code but with a STREAMS instead
> of Socket interface...
>
> Warner
>
> - Matt G.
>>
>
[-- Attachment #2: Type: text/html, Size: 2117 bytes --]
next prev parent reply other threads:[~2023-08-10 3:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:09 [TUHS] " Larry McVoy
2023-08-10 2:38 ` [TUHS] " segaloco via TUHS
2023-08-10 2:45 ` Warner Losh
2023-08-10 3:17 ` segaloco via TUHS
2023-08-10 3:18 ` Rob Pike [this message]
2023-08-10 5:44 ` John Cowan
2023-08-10 12:41 ` Douglas McIlroy
2023-08-10 14:00 ` Jonathan Gray
2023-08-11 9:05 Paul Ruizendaal
2023-08-12 5:08 ` Warner Losh
2023-08-12 5:41 ` George Michaelson
2023-08-12 9:06 ` Paul Ruizendaal
2023-08-12 10:29 ` Paul Ruizendaal
2023-08-12 15:20 ` Warner Losh
2023-08-12 15:24 ` Dan Cross
2023-08-12 16:12 ` Paul Ruizendaal
2023-08-12 15:05 Noel Chiappa
2023-08-12 18:00 ` 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='CAKzdPgzmY6N8piPjnNwr3p2Rnz83Pdq=3yXYbz+x-H=bZ65Mrw@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=imp@bsdimp.com \
--cc=segaloco@protonmail.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).