Path: utzoo!yunexus!torsqnt!dptcdc!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: richard%aiai.edinburgh.ac.uk@nss.cs.ucl.ac.uk (Richard Tobin)
Newsgroups: comp.sys.sun
Subject: vfork under 4.0?
Keywords: SunOS
Message-ID: <27717.8902241844@subnode.aiai.ed.ac.uk>
Date: 8 Mar 89 17:26:07 GMT
Article-I.D.: subnode.27717.8902241844
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 7
Approved: Sun-Spots@rice.edu
Original-Date: Fri, 24 Feb 89 18:44:34 GMT
X-Sun-Spots-Digest: Volume 7, Issue 187, message 12 of 15

Is there any reason to use vfork() under 4.0?  Isn't fork just as
efficient now that copy-on-write is implemented?  I see that the manual
page still says "this system call will be eliminated when proper system
sharing mechanisms are implemented".  Is this just an anachronism, or a
subtle attack on the 4.0 implementation?

-- Richard