Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mtune!codas!cpsc6a!rtech!daveb
From: daveb@rtech.UUCP (Dave Brower)
Newsgroups: comp.unix.questions
Subject: Re: vfork wars
Message-ID: <981@rtech.UUCP>
Date: Mon, 29-Jun-87 12:48:47 EDT
Article-I.D.: rtech.981
Posted: Mon Jun 29 12:48:47 1987
Date-Received: Sat, 4-Jul-87 22:21:17 EDT
References: <7737@brl-adm.ARPA> <1186@ius2.cs.cmu.edu>
Reply-To: daveb@rtech.UUCP (Dave Brower)
Organization: Relational Technology, Alameda CA
Lines: 19
Summary: Isn't "really" in BSD anyway...

In article <1028@bloom-beacon.MIT.EDU> tytso@athena.mit.edu (Theodore Y. Ts'o) writes:
>In article <22253@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:

[ Basically beating each other up ]

MU!

A look at the "4.2BSD System Manual, Revised July 1983" by Joy, Cooper,
Fabry, Leffler, McKusick and Mosher shows no such beast as a vfork. See
Section 2.5, paragraph 1.1.  There is a fork and an execve, but no
vfork.

From this, one may conclude that the 4.2BSD specification makes no mention of
vfork, but that the VAX implementation as documented in the man pages
does provide the thingy, warts and all.

-dB
-- 
{amdahl, cbosgd, mtxinu, ptsfa, sun}!rtech!daveb daveb@rtech.uucp