From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: setXid
Date: Mon, 20 Sep 2004 20:26:00 -0000 [thread overview]
Message-ID: <200409202026.i8KKQnRN032082@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Monday, 20 September 2004 13:18:49 -0700 <414F3B29.1040701@redhat.com>
> These extensions are honestly as well defined (or better) than the POSIX
> mandated behavior and they are necessary for people who actually want the
> behavior (at least for migration purposes).
Sorry, that is just totally wrong. Tell me right now exactly what they do,
I dare you. You can't, because we don't know. Like many parts of Linux,
this has always been a mess for the multithreaded cases and unclear what
many of the semantics are. People have been coping with it, yes. That
doesn't mean we want to say that this status quo is good enough. It's not.
> I see no problem at all. If another OS does not provide the
> functionality the functions can fail.
No other OS could provide the functionality, because noone knows what it is!
I demand a coherent specification for every API in glibc. Period.
Thanks,
Roland
prev parent reply other threads:[~2004-09-20 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 0:27 setXid Ulrich Drepper
2004-09-20 19:20 ` setXid Roland McGrath
2004-09-20 19:29 ` setXid Ulrich Drepper
2004-09-20 19:50 ` setXid Roland McGrath
2004-09-20 20:19 ` setXid Ulrich Drepper
2004-09-20 20:26 ` Roland McGrath [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=200409202026.i8KKQnRN032082@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).