From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 2.9bsd with networking on 18-bit possible?
Date: Tue, 11 Dec 2018 13:51:35 -0500 [thread overview]
Message-ID: <CAC20D2N8MMzMR+tBfu4MMh+wPY4CMbqG4NEys6xdvnxPEzC=Tg@mail.gmail.com> (raw)
In-Reply-To: <20181211184316.014E618C089@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
On Tue, Dec 11, 2018 at 1:43 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
>
> > Named Piped were definiately a Rand-ism (they were originally called
> 'Rand Pipes')
>
> Well, _RAND_ called them 'ports':
>
> https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/doc/ipc/ports
>
> Absolutely right... Rand Ports ... I stand corrected. Ports/Pipes -- same
thing ...
ᐧ
[-- Attachment #2: Type: text/html, Size: 1278 bytes --]
next prev parent reply other threads:[~2018-12-11 18:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 18:43 Noel Chiappa
2018-12-11 18:51 ` Clem Cole [this message]
2018-12-12 1:20 ` Jacob Ritorto
-- strict thread matches above, loose matches on Subject: below --
2018-12-15 1:54 Paul Ruizendaal
2018-12-12 17:55 Paul Ruizendaal
2018-12-12 14:38 Noel Chiappa
2018-12-12 14:14 Noel Chiappa
2018-12-12 10:29 Paul Ruizendaal
2018-12-11 16:57 Noel Chiappa
2018-12-11 17:01 ` Jon Forrest
2018-12-11 18:03 ` Clem Cole
2018-12-11 16:16 Noel Chiappa
2018-12-11 16:26 ` Clem Cole
2018-12-11 4:42 Noel Chiappa
2018-12-11 2:11 Noel Chiappa
2018-12-11 2:36 ` Grant Taylor via TUHS
2018-12-11 3:28 ` Warner Losh
2018-12-10 22:05 Jacob Ritorto
2018-12-11 1:21 ` Clem cole
2018-12-11 1:55 ` Grant Taylor via TUHS
2018-12-11 7:22 ` Lars Brinkhoff
2018-12-11 15:28 ` Clem Cole
2018-12-11 17:21 ` Lars Brinkhoff
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='CAC20D2N8MMzMR+tBfu4MMh+wPY4CMbqG4NEys6xdvnxPEzC=Tg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.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).