Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!hao!oddjob!mimsy!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: AT&T/Sun merged OS
Message-ID: <6626@brl-smoke.ARPA>
Date: Fri, 30-Oct-87 02:33:39 EST
Article-I.D.: brl-smok.6626
Posted: Fri Oct 30 02:33:39 1987
Date-Received: Wed, 4-Nov-87 05:52:07 EST
References: <1803@unc.cs.unc.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <1803@unc.cs.unc.edu> leech@unc.UUCP (Jonathan Leech) writes:
>... does this mean that the SVID will grow to
>encompass the additional Sun OS material, or will this be a separate
>product from System V?

As it was explained to me, Sun has already been influencing the SVID,
and that would continue, along with modification to SunOS so that by
the end of Phase I (1988) SunOS (at least on the SPARC machines)
would be fully SVID-compliant.  Note that the forthcoming ANSI C
standard and POSIX (including the POSIX-based FIPS) are also likely to
have significant impact on the direction the SVID takes.

The resulting evolved SunOS will then be marketed by both Sun and AT&T
under the "System V" banner.  It sure sounds to me that the intent is
to make this merged OS the future official System V porting base.