Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!sundc!nears!occrsh!occrsh.UUCP!gorgo.UUCP!authorplaceholder
From: bsteve@gorgo.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Remote File Sharing (RFS) - SVR
Message-ID: <58900008@gorgo.UUCP>
Date: Mon, 12-Jan-87 23:01:00 EST
Article-I.D.: gorgo.58900008
Posted: Mon Jan 12 23:01:00 1987
Date-Received: Wed, 14-Jan-87 23:20:49 EST
References: <7478@utzoo.UUCP>
Lines: 19
Nf-ID: #R:utzoo.UUCP:-747800:gorgo.UUCP:58900008:000:1058
Nf-From: gorgo.UUCP!bsteve    Jan 12 22:01:00 1987


In response to henry@utzoo.UUCP in comp.unix.questions:
>Unfortunately, licensing SVR3 is not something that can be taken for granted,
>since the license contains some troublesome clauses about mandatory SVID
>compliance that have made a lot of vendors think twice about it.

 This is *NOT* unfortunate. Previous ports of System V UNIX by multiple vendors
produced a hodge-podge of systems that were only marginally compatible. The
SVID compliance clauses in vendor licenses are designed to prevent the problems
in previous releases. The major reasoning for there being a SVID is that if I
write a product for an xyzzy that is SVID compliant, I want to be able to port
it trivially to an aardvark which is also SVID compliant. This certainly does
not preclude the implementation of 'universes' or other more global programming
and user environments, it just means that the product must be what it is
advertised to be... and high time, thank you.

   Steve Blasingame (at the summit of Monster Island)
   bsteve@eris.berkeley.edu
   ihnp4!occrsh!gorgo!bsteve