From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] EOF on pipes?
Date: Sun, 25 Feb 2018 19:39:02 -0700 [thread overview]
Message-ID: <4d9279f8-e920-0f7a-ebac-1115d6fd68e2@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.1802251422190.96837@orthanc.ca>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On 02/25/2018 03:25 PM, Lyndon Nerenberg wrote:
> And this lived on in the IL network protocol. I've always thought that
> was one of the more elegant aspects of IL, but of course it didn't have
> a hope in hell of surviving outside the Plan 9 ecosystem.
"IL network protocol"? I've never heard of it.
…Quick web search ~> Wikipedia…
Interesting. #LearnSomethingEveryDay
I really should mess with Plan9 one of these days.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180225/c50d9796/attachment.bin>
next prev parent reply other threads:[~2018-02-26 2:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 0:53 Norman Wilson
2018-02-25 16:29 ` Paul Winalski
2018-02-25 22:25 ` Lyndon Nerenberg
2018-02-25 23:18 ` Bakul Shah
2018-02-26 2:39 ` Grant Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-27 5:04 Rudi Blom
2018-02-27 5:48 ` Dave Horsfall
2018-02-25 13:07 Doug McIlroy
2018-02-25 13:16 ` George Michaelson
2018-02-25 13:56 ` arnold
2018-02-24 21:33 Dave Horsfall
2018-02-24 23:13 ` Ron Natalie
2018-02-24 23:42 ` Bakul Shah
2018-02-24 23:46 ` Nelson H. F. Beebe
2018-02-24 23:46 ` Jon Steinhart
2018-02-26 16:03 ` Rudi Blom
2018-02-26 16:58 ` Ian Zimmerman
2018-02-26 17:19 ` Larry McVoy
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=4d9279f8-e920-0f7a-ebac-1115d6fd68e2@spamtrap.tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/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).