From: Theodore Tso <tytso@mit.edu>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux should define ENOTSUP
Date: Thu, 7 Dec 2006 08:49:14 -0500 [thread overview]
Message-ID: <20061207134914.GB31773@thunk.org> (raw)
In-Reply-To: <20061206143159.GP3927@implementation.labri.fr>
On Wed, Dec 06, 2006 at 03:31:59PM +0100, Samuel Thibault wrote:
>
> Ok, so Linux will never be fully posix compliant.
?
Can you please quote chapter and verse (in POSIX) where it states that
ENOTSUP and EOPNOTSUP have to be numerically distinct? If you are
reading Unix 98 you might be able to make a claim that there is an
implication that they be assigned unique error numbers, but it's at
best an implication, not an explicitly specified requirement in any of
the standards documents that I'm aware of.
To folks who are participating in the committee doing work on the
upcoming POSIX revisions (which might make this a requirement to be
imposed on us in a year or two) --- will that likely impose such a
requirement? In that case we might want to start thinking about
separating the two, but it really is a question of is the benefits are
worth the effort.
- Ted
next prev parent reply other threads:[~2006-12-07 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 13:51 Linux should define ENOTSUP Samuel Thibault
2006-12-06 14:25 ` Arjan van de Ven
2006-12-06 14:31 ` Samuel Thibault
2006-12-06 15:17 ` H. Peter Anvin
2006-12-06 20:10 ` Ulrich Drepper
2006-12-06 21:11 ` H. Peter Anvin
2006-12-06 22:34 ` Ulrich Drepper
2006-12-07 13:49 ` Theodore Tso [this message]
2006-12-07 13:59 ` Andreas Schwab
2006-12-07 14:15 ` Theodore Tso
2006-12-07 14:30 ` Andreas Schwab
2006-12-07 15:33 ` Ulrich Drepper
2006-12-06 15:16 ` H. Peter Anvin
2006-12-06 15:25 ` Samuel Thibault
2006-12-06 15:26 ` H. Peter Anvin
2006-12-06 15:34 ` Samuel Thibault
2006-12-06 15:35 ` H. Peter Anvin
2006-12-06 16:14 ` Samuel Thibault
2006-12-06 16:44 ` H. Peter Anvin
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=20061207134914.GB31773@thunk.org \
--to=tytso@mit.edu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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