Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!ukma!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: att & osf Message-ID: <12145@ncoast.UUCP> Date: 10 Aug 88 23:23:47 GMT References: <4964@killer.DALLAS.TX.US> <3395@vpk4.UUCP> <1988Aug2.171126.17906@utzoo.uucp> <3396@vpk4.UUCP> <249@quintus.UUCP> <1275@sfmag.UUCP> <258@quintus.UUCP> <12118@ncoast.UUCP> <268@quintus.UUCP> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 45 As quoted from <268@quintus.UUCP> by ok@quintus.uucp (Richard A. O'Keefe): +--------------- | In article <12118@ncoast.UUCP> allbery@ncoast.UUCP (Brandon S. Allbery) writes: | >As quoted from <258@quintus.UUCP> by ok@quintus.uucp (Richard A. O'Keefe): | > To summarize: the SVID is good news for applications developers. | > AT&T _could_ ADD enormous chunks to the SVID without warning | > and that was Henry Spencer's original point. | >A few years ago, people were bitching about the System V standard because it | >didn't include networking. Now they're bitching because there's a mechanism | >for adding such missing pieces?! | | My posting was a reply to ..... someone from AT&T who denied that the SVID | had ever changed, +--------------- Did we read the same messages? The "someone from AT&T" NEVER asserted that the SVID had not changed! He said that it had been *expanded* -- which is exactly what I'm talking about and what is *necessary* if Unix is not to die. +--------------- | and that poster thought he was refuting Henry Spencer's | claim that the SVID was not as stable and multilaterally controlled a | standard as POSIX will be. +--------------- Frankly, POSIX is liable to be *too* stable. How often have you used pure ANSI Standard Pascal? How about ANSI Fortran? It is notable that the *effective* standard for Fortran has always been set by a single company (IBM), and that Pascal (which has no such backing) effectively has no standards at all. +--------------- | As for bitching about networking, I've read the relevant V.3 manuals | several times, and, well, does anyone know of anything printed in English | that explains V.3 networking? +--------------- Before anyone answers that, let's make sure it's a real issue: is there anything printed in English which explains BSD networking? (I.e. if there is, the point is valid, but if not then why does it matter?) ++Brandon -- Brandon S. Allbery, uunet!marque!ncoast!allbery DELPHI: ALLBERY For comp.sources.misc send mail to ncoast!sources-misc