Re: vfork revisited (was 64bit clean XEmacs)

PA> Isn't fork copy-on-write these days? Imprecise. Fork duplicates the address space. Ignoring the details of a particular VM (virtual memory) implementation, the confusion folks seem to have is that the address space may ultimately point at copy on write _pages_. This concept may be easier to understand when you start thinking about what the failure mode(s) should be. In UNIX we don't have the notion that a process may arbitrarily fail when a copy-on-write operation fails (we do have signals, but none describe COW failure) whereas fork() _is_ defined as possibly failing with ENOMEM.