From: Ulrich Drepper <drepper@redhat.com>
To: James A Griffin <agriffin@cpcug.org>
Cc: Ramsey Wally Contr AFRL/IFEB <Wally.Ramsey@rl.af.mil>,
"'NSA SELinux Mailing List'" <selinux@tycho.nsa.gov>
Subject: Re: Linux and Posix compliance
Date: 16 Jul 2001 13:10:43 -0700 [thread overview]
Message-ID: <m3hewcprcs.fsf@otr.mynet> (raw)
In-Reply-To: James A Griffin's message of "Mon, 16 Jul 2001 14:49:23 -0400"
James A Griffin <agriffin@cpcug.org> writes:
> One thing that I have noticed for years is the boot time message "POSIX
> conformance testing by UNIFIX". The message appears just after the CPU
> testing and before the PCI: Probe. UNIFIX is a UK company, IIRC. What
> the results of the "conformance testing" are, I do not know.
I think (and hope) they've finally removed this output. It never was
true and is anyway completely outdated.
There hasn't been any formal POSIX testing done. The reason is
simple: who'd pay this? POSIX testing is done by the certification
labs which charge enormous amounts of money for this.
The kernel people has done tests based on available standard tests
occasionally. I've done for the C library quite some testing and
wrote many tests myself. This still does not guarantee compliance,
though.
As for use in government and military. The current route seems to be
to get for Linux the same kind of exception which exists for NT. NT
does not conform to POSIX either and can be used. You might want to
check your appropriate standardization bureau about the status of
this.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2001-07-16 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 18:02 Linux and Posix compliance Ramsey Wally Contr AFRL/IFEB
2001-07-16 18:49 ` James A Griffin
2001-07-16 20:10 ` Ulrich Drepper [this message]
2001-07-16 22:11 ` James A Griffin
2001-07-16 22:30 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 21:02 Weaver, Mike D (N-CSC)
2001-07-16 21:14 ` Ulrich Drepper
[not found] <5.0.2.1.2.20010717000846.01f728e0@mail00708.popserver.pop.net>
2001-07-17 8:12 ` Andrew Josey
[not found] <5.0.2.1.2.20010717000931.01f74680@mail00708.popserver.pop.net>
2001-07-17 8:26 ` Andrew Josey
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=m3hewcprcs.fsf@otr.mynet \
--to=drepper@redhat.com \
--cc=Wally.Ramsey@rl.af.mil \
--cc=agriffin@cpcug.org \
--cc=drepper@cygnus.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.