Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: SVR3 SVID compliance clause
Message-ID: <5543@brl-smoke.ARPA>
Date: Tue, 20-Jan-87 04:28:11 EST
Article-I.D.: brl-smok.5543
Posted: Tue Jan 20 04:28:11 1987
Date-Received: Tue, 20-Jan-87 23:27:29 EST
References: <7478@utzoo.UUCP> <58900008@gorgo.UUCP> <7533@utzoo.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

The real problem with the SVID compliance clause, as I understand it,
is that it precludes non-SVID-compliant vendors, such as those who
started with a 4.2BSD kernel, from adopting ANY part of SVR3, even in
an attempt to transition to a SVID-compliant system.  This includes
such important items as STREAMS and RFS.  Surely we would all be
better off if such facilities could be picked up while the vendors
worked to move their systems into SVID and/or POSIX compliance.