Path: utzoo!mnetor!uunet!husc6!yale!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: Squueeezing Disk Space
Message-ID: <7067@brl-smoke.ARPA>
Date: 13 Jan 88 06:07:40 GMT
References: <2509@dasys1.UUCP> <7050@brl-smoke.ARPA> <10139@mimsy.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Distribution: na
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <10139@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>You seem to believe that SVID compatibility => BSD incompatibility.

No, rather that developing under BSD without paying much attention
to portability often results in SVID-incompatible code (and vice-versa,
I'm sure), so if SunOS starts to default to SVID-conforming, some
BSD-dependent code will break.  It is easier to develop SVID-compatible
applications under a System V environment, even an approximate one like
my emulation, than under a native BSD environment.