summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorG. Branden Robinson <g.branden.robinson@gmail.com>2023-07-28 12:58:55 -0500
committerAlejandro Colomar <alx@kernel.org>2023-07-28 22:55:03 +0200
commit47b6b10ec8a61dade7f50d6ec2a2ff7001fb19af (patch)
treeb9d082e091105b5f7954973dff895d0b62f8d1a7
parent8baa2d238cfb8f4317329ebe4b1a2560623010b6 (diff)
vfork.2: ffix
[Clean up in preparation for "MR sed".] * Use typographer's quotation marks. * Quote the 4.2BSD vfork(2) page _exactly_, including font styling. https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/man/man2/vfork.2 This is to remove a false positive in preparation for a sed(1)-driven update of man page cross references to use the groff 1.23.0 `MR` macro. Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
-rw-r--r--man2/vfork.29
1 files changed, 4 insertions, 5 deletions
diff --git a/man2/vfork.2 b/man2/vfork.2
index 3a65010ca..c2b18fcf2 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -149,13 +149,12 @@ and cannot rely on any specific behavior with respect to shared memory.
Some consider the semantics of
.BR vfork ()
to be an architectural blemish, and the 4.2BSD man page stated:
-"This system call will be eliminated when proper system sharing mechanisms
-are implemented.
+\[lq]This system call will be eliminated
+when proper system sharing mechanisms are implemented.
Users should not depend on the memory sharing semantics of
-.BR vfork ()
+.I vfork
as it will, in that case, be made synonymous to
-.BR fork (2).\c
-"
+.IR fork .\[rq]
However, even though modern memory management hardware
has decreased the performance difference between
.BR fork (2)