From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jim Rees <rees@umich.edu>
Cc: DENIEL Philippe <philippe.deniel@cea.fr>, linux-nfs@vger.kernel.org
Subject: Re: POSIX's "tables of the law"
Date: Tue, 12 Oct 2010 13:48:10 -0400 [thread overview]
Message-ID: <20101012174810.GF22495@fieldses.org> (raw)
In-Reply-To: <20101012115026.GB2577@merit.edu>
On Tue, Oct 12, 2010 at 07:50:26AM -0400, Jim Rees wrote:
> DENIEL Philippe wrote:
>
> on many aspects, knowing the POSIX standard and behavior is quite
> important when working on implementing something like NFSv4. There a
> problem occur : if I need information on NFS (whatever version) or
> any "related" protocol (RPCSEC_GSS, ONCRPC, ...) I can easily find a
> document that is the absolute reference to use. But what about POSIX
> ? I must have missed something but I never see such a reference. Do
> you have book references to provide me with about this subject ?
>
> The posix spec situation is confused because there are many different specs
> published at different times, and the ones that are most important (like
> acls) were never ratified as far as I know, so are still in draft form.
> Originally they were ISO specs, which cost big money, which is why you won't
> find them on the web. More recently I think the Open Group has been working
> on them, maybe you'll find copies there: www.opengroup.org
I think you want:
http://www.unix.org/single_unix_specification/
You have to fill out a form but there's no charge.
Of course you can also write little test programs and such to find out
what other filesystems or platforms do. No spec is perfect, alas.
--b.
prev parent reply other threads:[~2010-10-12 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 11:18 POSIX's "tables of the law" DENIEL Philippe
2010-10-12 11:50 ` Jim Rees
2010-10-12 17:48 ` J. Bruce Fields [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=20101012174810.GF22495@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=philippe.deniel@cea.fr \
--cc=rees@umich.edu \
/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 NNTP newsgroup(s).