Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sun-barr!ccut!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Re: fork() vs vfork() and COW
Message-ID: <5932@titcce.cc.titech.ac.jp>
Date: 24 Jul 90 06:05:15 GMT
References: <58053@bbn.BBN.COM> <476@exodus.Eng.Sun.COM> <58086@bbn.BBN.COM> <3733@auspex.auspex.com>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 15

In article <3733@auspex.auspex.com>
	guy@auspex.auspex.com (Guy Harris) writes:

>(BTW, for those who insist on making some stupid BSD vs. S5 debate out
>of this, note that S5R4 has "vfork()", and that the S5R4 "vfork()" man
>page includes a warning from which one could possibly infer that it
>operates similarly to the 4.xBSD and SunOS 4.x "vfork()".

NeXT (thus MACH) man page also have the same description, though,
actually, vfork is identical to fork.

Vfork on NeXT dosen't even wait for the completion or execing of
child process.

						Masataka Ohta