>From 33671da01189ff40533708c1d81e6d78bfa5e312 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Goddard=20Rosa?= <andre.goddard@xxxxxxxxx> Date: Sat, 17 Oct 2009 09:44:17 -0300 Subject: [PATCH] [PATCH] vfork.2: Improve text legibility and fix verbs tense MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: André Goddard Rosa <andre.goddard@xxxxxxxxx> diff --git a/man2/vfork.2 b/man2/vfork.2 index ef86812..4f73f80 100644 --- a/man2/vfork.2 +++ b/man2/vfork.2 @@ -74,7 +74,7 @@ is a special case of It is used to create new processes without copying the page tables of the parent process. It may be useful in performance-sensitive applications -where a child will be created which then immediately issues an +where a child will be created which then will immediately issue an .BR execve (2). .PP .BR vfork () @@ -110,7 +110,9 @@ and to create a unique task structure for the child. However, in the bad old days a .BR fork (2) would require making a complete copy of the caller's data space, -often needlessly, since usually immediately afterwards an +often needlessly, since usually immediately afterwards a +.BR vfork () +an .BR exec (3) is done. Thus, for greater efficiency, BSD introduced the @@ -125,7 +127,7 @@ child was using its resources. The use of .BR vfork () was tricky: for example, not modifying data -in the parent process depended on knowing which variables are +in the parent process depended on knowing which variables were held in a register. .SH "CONFORMING TO" 4.3BSD, POSIX.1-2001. -- 1.6.5.1.31.gad12b
From 33671da01189ff40533708c1d81e6d78bfa5e312 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Goddard=20Rosa?= <andre.goddard@xxxxxxxxx> Date: Sat, 17 Oct 2009 09:44:17 -0300 Subject: [PATCH] [PATCH] vfork.2: Improve text legibility and fix verbs tense MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: André Goddard Rosa <andre.goddard@xxxxxxxxx> diff --git a/man2/vfork.2 b/man2/vfork.2 index ef86812..4f73f80 100644 --- a/man2/vfork.2 +++ b/man2/vfork.2 @@ -74,7 +74,7 @@ is a special case of It is used to create new processes without copying the page tables of the parent process. It may be useful in performance-sensitive applications -where a child will be created which then immediately issues an +where a child will be created which then will immediately issue an .BR execve (2). .PP .BR vfork () @@ -110,7 +110,9 @@ and to create a unique task structure for the child. However, in the bad old days a .BR fork (2) would require making a complete copy of the caller's data space, -often needlessly, since usually immediately afterwards an +often needlessly, since usually immediately afterwards a +.BR vfork () +an .BR exec (3) is done. Thus, for greater efficiency, BSD introduced the @@ -125,7 +127,7 @@ child was using its resources. The use of .BR vfork () was tricky: for example, not modifying data -in the parent process depended on knowing which variables are +in the parent process depended on knowing which variables were held in a register. .SH "CONFORMING TO" 4.3BSD, POSIX.1-2001. -- 1.6.5.1.31.gad12b
