From: Guest section DW <dwguest@win.tue.nl>
To: Jeff Garzik <jgarzik@mandrakesoft.com>, Steven_Snyder@3com.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: State of Posix compliance in v2.2/v2.4 kernel?
Date: Mon, 13 Nov 2000 17:40:11 +0100 [thread overview]
Message-ID: <20001113174011.A880@win.tue.nl> (raw)
In-Reply-To: <88256996.00577D9E.00@hqoutbound.ops.3com.com> <3A101009.5F05DA18@mandrakesoft.com>
In-Reply-To: <3A101009.5F05DA18@mandrakesoft.com>; from Jeff Garzik on Mon, Nov 13, 2000 at 11:00:09AM -0500
On Mon, Nov 13, 2000 at 11:00:09AM -0500, Jeff Garzik wrote:
> Also, from what I've seen lately on IRC and lkml, the Single Unix
> Specification ("SuS") is generally held in higher regard than POSIX; and
> when spec questions arise, kernel developers tend to check SuS before
> POSIX (if POSIX is checked at all).
POSIX is the law, but many things are not covered.
SUSv2 is a large collection of random stuff.
The Austin group now prepares a joint revision of POSIX.1 and POSIX.2 and SUSv2.
This is to be the next version of all standards involved.
See also http://www.opengroup.org/austin/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-13 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 15:54 State of Posix compliance in v2.2/v2.4 kernel? Steven_Snyder
2000-11-13 16:00 ` Jeff Garzik
2000-11-13 16:13 ` Jakub Jelinek
2000-11-13 16:17 ` Jeff Garzik
2000-11-13 18:31 ` Gary Lawrence Murphy
2000-11-19 10:24 ` GOTO Masanori
2000-11-19 13:30 ` POSIX message queue passing (was Re: State of Posix compliance in v2.2/v2.4 kernel?) Jakub Jelinek
2000-11-13 16:40 ` Guest section DW [this message]
2000-11-13 20:28 ` State of Posix compliance in v2.2/v2.4 kernel? Ingo Oeser
-- strict thread matches above, loose matches on Subject: below --
2000-11-13 16:09 Dunlap, Randy
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=20001113174011.A880@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=Steven_Snyder@3com.com \
--cc=jgarzik@mandrakesoft.com \
--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