From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Sockets and the true UNIX
Date: Fri, 22 Sep 2017 09:26:49 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.1709220924160.89458@aneurin.horsfall.org> (raw)
In-Reply-To: <201709211613.v8LGDcuN015299@darkstar.fourwinds.com>
On Thu, 21 Sep 2017, Jon Steinhart wrote:
> In particular, I have often thought that it would have been a better and
> more consistent with the philosophy to have it implemented as
> open("/dev/tcp") and so on. Granted that networking added some new
> functionality that justified some of the system calls, just not
> socket().
An old Unix manual referred to preferring "/dev/net" but that would've
been a 9-track even parity tape drive under the nomenclature at the
time...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next prev parent reply other threads:[~2017-09-21 23:26 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
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 [this message]
[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=alpine.BSF.2.21.1709220924160.89458@aneurin.horsfall.org \
--to=dave@horsfall.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).