clone.2, mount.2, unshare.2, proc.5, path_resolution.7: Global fix: s/mount-point namespace/mount namespace/

This is more consistent with the term "mounts namespace"
used in the 2008 ACM SIGOPS paper, "Virtual servers
and and checkpoint/restart in mainstream Linux".
(I avoided the "s", because using the plural strikes me
as klunky English, and anyway we don't talk about
the "PIDs namespace" or the "networks namespace", etc..)

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/clone.2

@@ -43,7 +43,7 @@
 .\" FIXME . 2.6.25 marks the unused CLONE_STOPPED as obsolete, and it will
 .\"       probably be removed in the future.
 .\"
-.TH CLONE 2 2008-11-19 "Linux" "Linux Programmer's Manual"
+.TH CLONE 2 2008-11-20 "Linux" "Linux Programmer's Manual"
 .SH NAME
 clone, __clone2 \- create a child process
 .SH SYNOPSIS
@@ -285,9 +285,9 @@ This flag can't be specified in conjunction with
 .BR CLONE_SYSVSEM .
 .TP
 .BR CLONE_NEWNS " (since Linux 2.4.19)"
-Start the child in a new mount-point namespace.
+Start the child in a new mount namespace.
 
-Every process lives in a mount-point namespace.
+Every process lives in a mount namespace.
 The
 .I namespace
 of a process is the data (the set of mounts) describing the file hierarchy
@@ -298,21 +298,21 @@ or
 .BR clone ()
 where the
 .B CLONE_NEWNS
-flag is not set, the child lives in the same mount-point
+flag is not set, the child lives in the same mount
 namespace as the parent.
 The system calls
 .BR mount (2)
 and
 .BR umount (2)
-change the mount-point namespace of the calling process, and hence affect
+change the mount namespace of the calling process, and hence affect
 all processes that live in the same namespace, but do not affect
-processes in a different mount-point namespace.
+processes in a different mount namespace.
 
 After a
 .BR clone ()
 where the
 .B CLONE_NEWNS
-flag is set, the cloned child is started in a new mount-point namespace,
+flag is set, the cloned child is started in a new mount namespace,
 initialized with a copy of the namespace of the parent.
 
 Only a privileged process (one having the \fBCAP_SYS_ADMIN\fP capability)

man2/mount.2

@@ -37,7 +37,7 @@
 .\" 2008-10-06, mtk: move umount*() material into separate umount.2 page.
 .\" 2008-10-06, mtk: Add discussion of namespaces.
 .\"
-.TH MOUNT 2 2008-11-19 "Linux" "Linux Programmer's Manual"
+.TH MOUNT 2 2008-11-20 "Linux" "Linux Programmer's Manual"
 .SH NAME
 mount \- mount file system
 .SH SYNOPSIS
@@ -377,8 +377,8 @@ just silently ignored in this case.
 .\" The change is in patch-2.4.0-prerelease.
 .SS Per-process Namespaces
 Starting with kernel 2.4.19, Linux provides
-per-process mount-point namespaces.
-A mount-point namespace is the set of file system mounts that
+per-process mount namespaces.
+A mount namespace is the set of file system mounts that
 are visible to a process.
 Mount-point namespaces can be (and usually are)
 shared between multiple processes,
@@ -389,11 +389,11 @@ was a single namespace was shared by every process on the system.)
 
 A child process created by
 .BR fork (2)
-shares its parent's mount-point namespace;
-the mount-point namespace is preserved across an
+shares its parent's mount namespace;
+the mount namespace is preserved across an
 .BR execve (2).
 
-A process can obtain a private mount-point namespace if:
+A process can obtain a private mount namespace if:
 it was created using the
 .BR clone ()
 .BR CLONE_NEWNS
@@ -407,7 +407,7 @@ or it calls
 with the
 .BR CLONE_NEWNS
 flag,
-which causes the caller's mount-point namespace to obtain a private copy
+which causes the caller's mount namespace to obtain a private copy
 of the namespace that it was previously sharing with other processes,
 so that future mounts and unmounts by the caller are invisible
 to other processes (except child processes that the caller
@@ -415,7 +415,7 @@ subsequently creates) and vice versa.
 
 The Linux-specific
 .I /proc/PID/self
-file exposes the list of mount points in the mount-point
+file exposes the list of mount points in the mount
 namespace of the process with the specified ID; see
 .BR proc (5)
 for details.

man2/unshare.2

@@ -18,7 +18,7 @@
 .\" FIXME Document CLONE_NEWUTS, which is new in 2.6.19
 .\" FIXME Document CLONE_SYSVSEM, which is new in 2.6.26
 .\"
-.TH UNSHARE 2 2008-11-19 "Linux" "Linux Programmer's Manual"
+.TH UNSHARE 2 2008-11-20 "Linux" "Linux Programmer's Manual"
 .SH NAME
 unshare \- disassociate parts of the process execution context
 .SH SYNOPSIS
@@ -34,7 +34,7 @@ unshare \- disassociate parts of the process execution context
 .BR unshare ()
 allows a process to disassociate parts of its execution
 context that are currently being shared with other processes.
-Part of the execution context, such as the mount-point namespace, is shared
+Part of the execution context, such as the mount namespace, is shared
 implicitly when a new process is created using
 .BR fork (2)
 or
@@ -87,7 +87,7 @@ effect as the
 .BR clone (2)
 .B CLONE_NEWNS
 flag.
-Unshare the mount-point namespace,
+Unshare the mount namespace,
 so that the calling process has a private copy of
 its namespace which is not shared with any other process.
 Specifying this flag automatically implies

man5/proc.5

@@ -58,7 +58,7 @@
 .\" to see what information could be imported from that file
 .\" into this file.
 .\"
-.TH PROC 5 2008-11-19 "Linux" "Linux Programmer's Manual"
+.TH PROC 5 2008-11-20 "Linux" "Linux Programmer's Manual"
 .SH NAME
 proc \- process information pseudo-file system
 .SH DESCRIPTION
@@ -432,7 +432,7 @@ in the kernel source tree.
 .TP
 .IR /proc/[pid]/mounts " (since Linux 2.4.19)"
 This is a list of all the file systems currently mounted in the
-process's mount-point namespace.
+process's mount namespace.
 The format of this file is documented in
 .BR fstab (5).
 Since kernel version 2.6.15, this file is pollable:
@@ -1308,10 +1308,10 @@ kernel.
 .I /proc/mounts
 Before kernel 2.4.19, this file was a list
 of all the file systems currently mounted on the system.
-With the introduction of per-process mount-point namespaces in
+With the introduction of per-process mount namespaces in
 Linux 2.4.19, this file became a link to
 .IR /proc/self/mounts ,
-which lists the mount points of the process's own mount-point namespace.
+which lists the mount points of the process's own mount namespace.
 The format of this file is documented in
 .BR fstab (5).
 .TP

man7/path_resolution.7

@@ -20,7 +20,7 @@
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
 .\"
-.TH PATH_RESOLUTION 7 2008011-19 "Linux" "Linux Programmer's Manual"
+.TH PATH_RESOLUTION 7 2008-11-20 "Linux" "Linux Programmer's Manual"
 .SH NAME
 Unix/Linux path resolution \- find the file referred to by a filename
 .SH DESCRIPTION
@@ -38,7 +38,7 @@ A process may get a different root directory
 by use of the
 .BR chroot (2)
 system call.
-A process may get an entirely private mount-point namespace in case
+A process may get an entirely private mount namespace in case
 it \(em or one of its ancestors \(em was started by an invocation of the
 .BR clone (2)
 system call that had the