From: David Newall <davidn@davidnewall.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
Albert ARIBAUD <albert.aribaud@free.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Amerigo Wang <xiyou.wangcong@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: PROPOSAL: extend pipe() to support NULL argument.
Date: Wed, 08 Jul 2009 06:07:22 +0930 [thread overview]
Message-ID: <4A53B202.9080505@davidnewall.com> (raw)
In-Reply-To: <412e6f7f0907070045o6a17fb10x557108ffde0da11@mail.gmail.com>
Changli Gao wrote:
> mkfifo(name);
> open(name, O_RDWR);
> unlink(name);
>
> Is it a trick?
This does beg the question, why is it necessary to "extend" pipe() in
this way?
next prev parent reply other threads:[~2009-07-07 20:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 7:36 PROPOSAL: extend pipe() to support NULL argument Changli Gao
2009-07-02 9:13 ` Amerigo Wang
2009-07-02 9:18 ` Changli Gao
2009-07-02 9:46 ` Amerigo Wang
2009-07-02 10:04 ` Changli Gao
2009-07-02 10:21 ` Amerigo Wang
2009-07-03 0:43 ` Changli Gao
2009-07-03 1:55 ` Amerigo Wang
2009-07-03 2:10 ` Changli Gao
2009-07-03 3:00 ` Amerigo Wang
2009-07-03 4:08 ` Changli Gao
2009-07-03 5:19 ` Amerigo Wang
2009-07-03 5:42 ` Changli Gao
2009-07-03 7:15 ` Amerigo Wang
2009-07-03 7:40 ` Changli Gao
2009-07-03 8:16 ` Amerigo Wang
2009-07-03 8:27 ` Changli Gao
2009-07-03 9:42 ` Amerigo Wang
2009-07-03 9:59 ` Changli Gao
2009-07-03 10:23 ` Amerigo Wang
2009-07-03 10:28 ` Albert ARIBAUD
2009-07-06 1:12 ` Changli Gao
2009-07-06 6:15 ` Albert ARIBAUD
2009-07-06 6:23 ` Changli Gao
2009-07-06 6:30 ` Albert ARIBAUD
2009-07-07 4:43 ` Denys Vlasenko
2009-07-07 7:45 ` Changli Gao
2009-07-07 20:37 ` David Newall [this message]
2009-07-07 21:02 ` Zan Lynx
2009-07-08 4:41 ` Changli Gao
2009-07-08 4:43 ` David Newall
2009-07-02 10:42 ` Alan Cox
2009-07-03 0:45 ` Changli Gao
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=4A53B202.9080505@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=albert.aribaud@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
--cc=xiaosuo@gmail.com \
--cc=xiyou.wangcong@gmail.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