On Thu, 16 Mar 2000 10:34:28 -0400,
Horst von Brand <vonbrand@pincoya.inf.utfsm.cl> wrote:
>vfork(2) was introduced to avoid copying a
>memory space just to discard it immediately on exec(2). With modern COW
>fork(2)s, it isn't needed
vfork is used in embedded Linux on systems that do not support COW,
usually because they have no memory management. And yes, the only safe
thing that the child can do is exec. uClinux vfork suspends the parent
until the child issues exec.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:23 EST