On 8/12/06, Victor Nazarov <[EMAIL PROTECTED]> 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

Reply via email to