From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [OT] domain socket support in open(2) on unix
Date: Tue, 20 May 2003 15:55:46 -0700 [thread overview]
Message-ID: <5302036b5e864aaa7241e70547b87609@collyer.net> (raw)
In-Reply-To: <20030520220305.GA28447@wilbur.25thandClement.com>
It seems obvious that it should be possible to open existing
Unix-domain sockets like any other file. They appear in the
file-system namespace, after all. Other systems call them named pipes
or mounted streams. It should be a trivial change to creat to create
Unix-domain sockets.
Of course, the whole range of socket-related system calls could be
replaced with /net, dial and cs, and this would eliminate arcane and
often buggy socket code from ordinary programs, allowing them to adapt
without recompilation to, for example, IP V6.
next prev parent reply other threads:[~2003-05-20 22:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 22:03 William Ahern
2003-05-20 22:42 ` boyd, rounin
2003-05-20 23:27 ` ron minnich
2003-05-20 23:32 ` boyd, rounin
2003-05-20 23:35 ` Russ Cox
2003-05-20 23:42 ` boyd, rounin
2003-05-21 0:08 ` Dan Cross
2003-05-21 0:40 ` northern snowfall
2003-05-20 23:38 ` andrey mirtchovski
2003-05-21 0:46 ` [9fans] Re: [Way OT] " Jim Choate
2003-05-21 1:08 ` [9fans] [OT] " okamoto
2003-05-21 1:23 ` andrey mirtchovski
2003-05-21 1:33 ` ron minnich
2003-05-21 1:33 ` Geoff Collyer
2003-05-21 2:38 ` okamoto
2003-05-21 3:47 ` [9fans] The Future of OS's & P9 (was: Re: [OT] domain socket support in open(2) on unix) Jim Choate
2003-05-21 4:47 ` Lucio De Re
2003-05-21 10:59 ` boyd, rounin
2003-05-21 11:27 ` Jim Choate
2003-05-21 16:46 ` Lucio De Re
2003-05-21 16:50 ` boyd, rounin
2003-05-20 22:55 ` Geoff Collyer [this message]
2003-06-08 16:02 ` [9fans] [OT] domain socket support in open(2) on unix Russ Cox
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=5302036b5e864aaa7241e70547b87609@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).