From: Jim Meyering <jim@meyering.net>
To: Eric Blake <ebb9@byu.net>
Cc: bug-coreutils <bug-coreutils@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] new open flag O_NOSTD
Date: Sun, 30 Aug 2009 13:18:07 +0200 [thread overview]
Message-ID: <87vdk5wnww.fsf@meyering.net> (raw)
In-Reply-To: <c5df85930908300412lc2f334dle4502492b25827f5@mail.gmail.com> (James Youngman's message of "Sun, 30 Aug 2009 12:12:42 +0100")
James Youngman wrote:
> On Mon, Aug 24, 2009 at 1:22 PM, Eric Blake<ebb9@byu.net> wrote:
>> The name proposed in this mail is O_NOSTD (implying that a successful
>> result will not be any of the standard file descriptors); other ideas
>> mentioned on the bug-gnulib list were O_SAFER, O_NONSTD, O_NOSTDFD.
>> http://lists.gnu.org/archive/html/bug-gnulib/2009-08/msg00358.html
>>
>> Thoughts?
>
> Mostly yes, I like it.
>
> I'd like to explicitly vote against O_SAFER, because there may be (for
> some systems or in the future) some other way of making open(2) safer.
> I'd vote positively for O_NOSTDFD or O_NOSTD.
I like this addition, too.
However, I would prefer O_NOSTDFD,
since O_NOSTD evokes "non-standard".
prev parent reply other threads:[~2009-08-30 11:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 12:22 [RFC] new open flag O_NOSTD Eric Blake
2009-08-25 12:16 ` [PATCH] open: introduce O_NOSTD Eric Blake
2009-08-25 21:53 ` Davide Libenzi
2009-08-27 13:54 ` Eric Blake
2009-08-27 14:22 ` Ulrich Drepper
2009-08-28 12:28 ` Eric Blake
2009-08-27 14:35 ` Florian Weimer
2009-08-28 12:45 ` Eric Blake
2009-08-28 12:52 ` Florian Weimer
2009-08-28 12:58 ` Eric Blake
2009-08-28 13:04 ` Eric Blake
2009-08-27 22:55 ` Davide Libenzi
2009-08-27 23:11 ` Ulrich Drepper
2009-08-30 11:12 ` [RFC] new open flag O_NOSTD James Youngman
2009-08-30 11:18 ` Jim Meyering [this message]
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=87vdk5wnww.fsf@meyering.net \
--to=jim@meyering.net \
--cc=bug-coreutils@gnu.org \
--cc=ebb9@byu.net \
--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