Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!usenix!jsq
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.unix
Subject: Re: Standards Update, NIST Shell-and-Tools FIPS Workshop
Message-ID: <560@usenix.ORG>
Date: 28 Sep 90 19:27:10 GMT
References: <558@usenix.ORG>
Sender: jsq@usenix.ORG
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 20
Approved: jsq@usenix.org (Moderator, John Quarterman)
X-Submissions: std-unix@uunet.uu.net

Submitted-by: gwyn@smoke.brl.mil (Doug Gwyn)

In article <558@usenix.ORG> std-unix@uunet.uu.net writes:
>Standards let the government avoid vendor-specific requirements like
>UNIX or SVID.  ...
>The Government has a burning need for a standard, they find it
>politically unacceptable to use UNIX System V as that standard, ...

I have to challenge this often-heard (from DEC, for example, who don't
want truly open systems in the first place) rationale.  In fact there
have been more than one major (in the billion-dollar range) federal
acquisition where SVID conformance was specified, and that specification
was successfully upheld in appeals.  Thus the government's official
position would appear to be that SVID is an acceptable standard.

Note that SVID is not the same as AT&T UNIX System V implementation,
although there is clearly a relationship between them.  (But there
also is between UNIX System V and POSIX, ANSI C, etc.)

Volume-Number: Volume 21, Number 148