From: jon@fourwinds.com (Jon Steinhart)
Subject: [TUHS] Sockets and the true UNIX
Date: Thu, 21 Sep 2017 09:13:38 -0700 [thread overview]
Message-ID: <201709211613.v8LGDcuN015299@darkstar.fourwinds.com> (raw)
In-Reply-To: <20170921160112.ctpv4a52t5rjcqzg@matica.foolinux.mooo.com>
Ian Zimmerman writes:
> This question is motivated by the posters for whom FreeBSD is not Unix
> enough :-)
>
> Probably the best known contribution of the Berkeley branch of Unix is
> the sockets API for IP networking. But today, if for no other reason
> than the X/Open group of standards, sockets are the preferred networking
> API everywhere, even on true AT&T derived UNIX variants. So they must
> have been merged back at some point, or reimplemented. My question is,
> when and how did that happen?
>
> And if there isn't a simple answer because it happened at different
> times and in different ways for each variant, all the better :-)
Maybe this is naive of me, but I have never liked parts of the sockets
interface. I understand that at some level it was a political/legal
keeping the networking code independent of the rest of the kernel.
From a technical and historical standpoint, I view it as the tip of
the iceberg bloating the number of system calls.
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().
Comments?
Jon
next prev parent reply other threads:[~2017-09-21 16:13 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 [this message]
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=201709211613.v8LGDcuN015299@darkstar.fourwinds.com \
--to=jon@fourwinds.com \
/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).