From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <786ca3b23235717eb6c440a6bf0f15e7@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] APE fork()
From: Brantley Coile <brantley@coraid.com>
Date: Sat, 12 Aug 2006 13:22:07 -0400
In-Reply-To: <ee9e417a0608120815l34c06f8docd1464bad0ee227d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9d9820a2-ead1-11e9-9d60-3106f5b1d025

BUGS section of 4th BSD manual, VFORK(2V)

 ``This system call may be unnecessary if the 
 system sharing mechanism allow fork
 to be implemented more efficiently''
 
 
>> On 8/12/06, Victor Nazarov <vir@comtv.ru> wrote:
>> > POSIX-fork() copies data and bss segmets, child process doesn't share
>> > data with it's parent.
>>
>> vfork() causes both child and parent to share address space.  I
>> believe this was introduced to make the fork/exec sequence faster as
>> the address space COW didn't need to be setup.
> 
> I always thought vfork was introduced because
> copy-on-write hadn't been invented yet.
> 
> It's the only logical explanation.
> 
> Russ