[Info-vax] Looking into C-include files on VMS

[Bob Koehler]

In article <7ltgfgF3ggj8tU1 at mid.dfncis.de>, js at cs.tu-berlin.de (Joerg Schilling) writes:
> 
> It seems that you don't know that AT&T was not allowed to sell UNIX in the 
> 1970s as AT&T was a monopoly and thus some US anti trust laws did forbid
> AT&T to sell anything not related to the monopoly.

   OK, the oldest add from AT&T that I've found was 1981.  Prior to
   being able to sell UNIX for money they gave copies to a few
   universities and other institutions.  But it didn't catch on.  And
   when they did try to sell it, it didn't sell.

   It took startups like Sun to create a product that included UNIX
   and found a market.  At a time when DEC kept coming out with
   small, cheap VAX-11 series systems (compared to IBM et. al. that
   DEC viewed as DEC's competition), Sun and others offered small,
   cheaper systems, in part because they did hardware integration, not
   CPU design and FAB, and they didn't invest a lot of money in writing 
   operating systems.

> You also seem to forget that the name vfork() and the related interface 
> is not a VMS invention but was introduced by Bill Joy at UCB in BSD UNIX. 

   vfork() on VMS is the first part of a two routines (the second is one
   of the exec() variations, several are supported) that together emulate 
   the behaviour of vfork() and the same exec() varition on UNIX.  The
   implementation is completely different (VMS doesn't actuall create
   the second process until the exec() call).

   I've always known this and I think I've said nothing that conflicts
   with it.  As a matter of fact, I recently said basically what I just
   said above.