Russ Cox wrote:
I always thought vfork was introduced because copy-on-write hadn't been invented yet. It's the only logical explanation. Russ
It is the correct explanation, that was the only reason to justify one of the most dangerous system calls ever invented, all in the name of performance, so I was relieved when it was finally made synonymous to fork() in almost any decent Unix out there (with the exception of NetBSD that reintroduced it and Linux that copied it from them).
Regards, -Leonardo Valencia
