From: "H. Peter Anvin" <hpa@transmeta.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: bidirectional named pipe?
Date: Sat, 10 Feb 2001 17:38:40 -0800 [thread overview]
Message-ID: <3A85ED20.761E8240@transmeta.com> (raw)
In-Reply-To: <E14OxTz-0007yS-00@the-village.bc.nu> <3A81D5B4.9CBC9B0D@kasey.umkc.edu> <95v90g$ke6$1@cesium.transmeta.com> <20010210181246.C8934@metastasis.f00f.org>
Chris Wedgwood wrote:
>
> On Thu, Feb 08, 2001 at 03:10:08PM -0800, H. Peter Anvin wrote:
>
> I would really like it if open() on a socket would be the same
> thing to connect to a socket as a client. I don't think it's a
> good idea to do that for the server side, though, since it would
> have to know about accept() anyway.
>
> things like this (non-portable hacks) belong in libc surely?
>
Not if it makes more sense to implement in the kernel. I can't think of
a way to implement it in glibc without races, perhaps you can.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-11 1:39 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 [this message]
2001-02-10 0:31 ` David L. Nicol
2001-02-10 1:37 ` Doug McNaught
-- 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=3A85ED20.761E8240@transmeta.com \
--to=hpa@transmeta.com \
--cc=cw@f00f.org \
--cc=hpa@zytor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.