From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Ethernet in /dev (was Re: Were all of you.. Hippies?)
Date: Fri, 31 Mar 2017 00:11:25 +0200 [thread overview]
Message-ID: <58dd828d.WLrIXtDSHxyFDrfe%schily@schily.net> (raw)
In-Reply-To: <1490901886.27069.for-standards-violators@oclsc.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Norman Wilson <norman at oclsc.org> wrote:
> But is IP done that way in SVr4 (or at least in Solaris, its
> most-visible descendant)? I had the impression that the
> IP stack was more like the BSD one, with everything coupled
> together within the kernel and a fundamentally socket interface.
The code has been implemented in a way that mainly differs in that "ifconfig"
needs to be called with "ifconfig <ifname> plumb" before you can use the
interface.
In former times, sockets have been emulated in userland, but this prevents a
socket filedescriptor returned from a dup(sockfd) to work as expected. As a
result, POSIX later required sockets to be an integral part of the
implementation and sockets went into the kernel again.
BTW: there was a paper from Sun that explains that sockets are faster then
using the STREAMS based t_open() and friends.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/
next prev parent reply other threads:[~2017-03-30 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 19:24 Norman Wilson
2017-03-30 22:11 ` Joerg Schilling [this message]
2017-03-31 4:39 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2017-03-30 19:24 Norman Wilson
2017-03-30 15:55 Norman Wilson
2017-03-30 16:05 ` Ron Natalie
2017-03-30 16:14 ` ron minnich
2017-03-30 16:48 ` Joerg Schilling
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=58dd828d.WLrIXtDSHxyFDrfe%schily@schily.net \
--to=schily@schily.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).