Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!mips!pacbell.com!decwrl!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  Skeleton include files
Message-ID: <9008291307.AA01249@richter.mit.edu>
Date: 29 Aug 90 13:07:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

Hah! Missing Unix include files ... try the Aegis /sys/ins files that keep
having new mistakes introduced in them at every minor OS release! As usual,
HP/Apollo's response is something along the lines of "Well, when OSF is
released, you won't want to use those insert files anyway (BSD and Aegis)"
We've been getting that sort of encouragement for the past two years.
OSF will be out in about 6 months, by my guess; and it will be SYSV
compliant according to all the literature. HP/Apollo has said nothing
about BSD compliance nor whether they will port any of the Apollo
specific libraries to OSF.

Here's a simple question in economics ... if company A has to support
HP/UX, Aegis, BSD, SYSV, and OSF and if company B only has to support
a SYSV derivative, who has the better profit margin? If company A says
that OSF is "the standard", how much effort will they put into the

other 4 OS releases, and how much effort will they put into forcing
(ahem, I meant to say "encouraging") their customer base into adopting
the "standard" OS?


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)