LDP: Update original to LDP v3.68

[linuxjm/LDP_man-pages.git] / original / man3 / shm_open.3

diff --git a/original/man3/shm_open.3 b/original/man3/shm_open.3
index 90991a4..f2ea6d3 100644 (file)
--- a/original/man3/shm_open.3
+++ b/original/man3/shm_open.3
@@ -83,7 +83,9 @@ and any of the other flags listed here:
 Open the object for read access.
 A shared memory object opened in this way can be
 .BR mmap (2)ed
-only for read (\fBPROT_READ\fP) access.
+only for read
+.RB ( PROT_READ )
+access.
 .TP
 .B O_RDWR
 Open the object for read-write access.
@@ -92,7 +94,7 @@ Open the object for read-write access.
 Create the shared memory object if it does not exist.
 The user and group ownership of the object are taken
 from the corresponding effective IDs of the calling process,
-.\" In truth it is actually the file system IDs on Linux, but these
+.\" In truth it is actually the filesystem IDs on Linux, but these
 .\" are nearly always the same as the effective IDs.  (MTK, Jul 05)
 and the object's
 permission bits are set according to the low-order 9 bits of
@@ -263,7 +265,7 @@ On Linux, this will successfully truncate an existing
 shared memory object\(emthis may not be so on other UNIX systems.
 .LP
 The POSIX shared memory object implementation on Linux 2.4 makes use
-of a dedicated file system, which is normally
+of a dedicated filesystem, which is normally
 mounted under
 .IR /dev/shm .
 .SH SEE ALSO
@@ -277,3 +279,12 @@ mounted under
 .BR open (2),
 .BR umask (2),
 .BR shm_overview (7)
+.SH COLOPHON
+This page is part of release 3.68 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.