From: Doug McNaught <doug@wireboard.com>
To: "David L. Nicol" <dnicol@cstp.umkc.edu>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Miller, Brendan" <Brendan.Miller@Dialogic.com>
Subject: Re: bidirectional named pipe?
Date: 09 Feb 2001 20:37:44 -0500 [thread overview]
Message-ID: <m3vgqjz5av.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <E14OxTz-0007yS-00@the-village.bc.nu> <3A81D5B4.9CBC9B0D@kasey.umkc.edu> <3A848BFF.C7C0E258@cstp.umkc.edu>
In-Reply-To: "David L. Nicol"'s message of "Fri, 09 Feb 2001 18:31:59 -0600"
"David L. Nicol" <dnicol@cstp.umkc.edu> writes:
> According to the Understanding the Linux Kernel book I
> plowed through yesterday afternoon the EXT2 file system
> has a defined file type "socket," distinct from fifo.
>
> How does one set up a named socket in a file system? Is it
> a legacy constant that has never been supported or what?
>
Call bind() on an AF_LOCAL (aka AF_UNIX) socket.
About as far from legacy as you can get...
-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-10 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 0:33 bidirectional named pipe? Miller, Brendan
2001-02-03 0:47 ` J . A . Magallon
2001-02-03 2:41 ` Wakko Warner
2001-02-03 7:51 ` Alan Cox
2001-02-03 14:28 ` Jamie Lokier
2001-02-07 23:09 ` David L. Nicol
2001-02-08 23:10 ` H. Peter Anvin
2001-02-10 5:12 ` Chris Wedgwood
2001-02-11 1:38 ` H. Peter Anvin
2001-02-10 0:31 ` David L. Nicol
2001-02-10 1:37 ` Doug McNaught [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-03 0:49 Miller, Brendan
2001-02-03 4:55 Miller, Brendan
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=m3vgqjz5av.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=Brendan.Miller@Dialogic.com \
--cc=dnicol@cstp.umkc.edu \
--cc=linux-kernel@vger.kernel.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