util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation
@ 2021-09-09  0:08 Michael Kerrisk
  2021-09-09  0:08 ` [PATCH 2/2] unshare.1.adoc: Improve wording re creation of bind mounts Michael Kerrisk
  2021-09-21  8:47 ` [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Karel Zak
  0 siblings, 2 replies; 3+ messages in thread
From: Michael Kerrisk @ 2021-09-09  0:08 UTC (permalink / raw)
  To: mtk.manpages, Karel Zak; +Cc: util-linux

The terminonoly "unshare the namespace" is not very helpful.
Instead, use wording that explains what these options actually
fo: "create a new namespace".

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
 sys-utils/unshare.1.adoc | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/sys-utils/unshare.1.adoc b/sys-utils/unshare.1.adoc
index f0fdf506f..2f1be8fc3 100644
--- a/sys-utils/unshare.1.adoc
+++ b/sys-utils/unshare.1.adoc
@@ -53,30 +53,30 @@ The process can have a distinct view of *CLOCK_MONOTONIC* and/or *CLOCK_BOOTTIME
 == OPTIONS
 
 *-i*, *--ipc*[**=**__file__]::
-Unshare the IPC namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new IPC namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
 
 *-m*, *--mount*[**=**__file__]::
-Unshare the mount namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. Note that _file_ must be located on a mount whose propagation type is not *shared* (or an error results). Use the command *findmnt -o+PROPAGATION* when not sure about the current setting. See also the examples below.
+Create a new mount namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. Note that _file_ must be located on a mount whose propagation type is not *shared* (or an error results). Use the command *findmnt -o+PROPAGATION* when not sure about the current setting. See also the examples below.
 
 *-n*, *--net*[**=**__file__]::
-Unshare the network namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new network namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
 
 *-p*, *--pid*[**=**__file__]::
-Unshare the PID namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. (Creation of a persistent PID namespace will fail if the *--fork* option is not also specified.)
+Create a new PID namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. (Creation of a persistent PID namespace will fail if the *--fork* option is not also specified.)
 +
 See also the *--fork* and *--mount-proc* options.
 
 *-u*, *--uts*[**=**__file__]::
-Unshare the UTS namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new UTS namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
 
 *-U*, *--user*[**=**__file__]::
-Unshare the user namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new user namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
 
 *-C*, *--cgroup*[**=**__file__]::
-Unshare the cgroup namespace. If _file_ is specified, then persistent namespace is created by bind mount.
+Create a new cgroup namespace. If _file_ is specified, then persistent namespace is created by bind mount.
 
 *-T*, *--time*[**=**__file__]::
-Unshare the time namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. The *--monotonic* and *--boottime* options can be used to specify the corresponding offset in the time namespace.
+Create a new time namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. The *--monotonic* and *--boottime* options can be used to specify the corresponding offset in the time namespace.
 
 *-f*, *--fork*::
 Fork the specified _program_ as a child process of *unshare* rather than running it directly. This is useful when creating a new PID namespace. Note that when *unshare* is waiting for the child process, then it ignores *SIGINT* and *SIGTERM* and does not forward any signals to the child. It is necessary to send signals to the child process.
-- 
2.31.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH 2/2] unshare.1.adoc: Improve wording re creation of bind mounts
  2021-09-09  0:08 [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Michael Kerrisk
@ 2021-09-09  0:08 ` Michael Kerrisk
  2021-09-21  8:47 ` [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Karel Zak
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Kerrisk @ 2021-09-09  0:08 UTC (permalink / raw)
  To: mtk.manpages, Karel Zak; +Cc: util-linux

Use consistent wording for the options that create
bind mounts, and improve the wording.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
 sys-utils/unshare.1.adoc | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/sys-utils/unshare.1.adoc b/sys-utils/unshare.1.adoc
index 2f1be8fc3..490dfc8b9 100644
--- a/sys-utils/unshare.1.adoc
+++ b/sys-utils/unshare.1.adoc
@@ -53,30 +53,30 @@ The process can have a distinct view of *CLOCK_MONOTONIC* and/or *CLOCK_BOOTTIME
 == OPTIONS
 
 *-i*, *--ipc*[**=**__file__]::
-Create a new IPC namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new IPC namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_.
 
 *-m*, *--mount*[**=**__file__]::
-Create a new mount namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. Note that _file_ must be located on a mount whose propagation type is not *shared* (or an error results). Use the command *findmnt -o+PROPAGATION* when not sure about the current setting. See also the examples below.
+Create a new mount namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_. Note that _file_ must be located on a mount whose propagation type is not *shared* (or an error results). Use the command *findmnt -o+PROPAGATION* when not sure about the current setting. See also the examples below.
 
 *-n*, *--net*[**=**__file__]::
-Create a new network namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new network namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_.
 
 *-p*, *--pid*[**=**__file__]::
-Create a new PID namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. (Creation of a persistent PID namespace will fail if the *--fork* option is not also specified.)
+Create a new PID namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_. (Creation of a persistent PID namespace will fail if the *--fork* option is not also specified.)
 +
 See also the *--fork* and *--mount-proc* options.
 
 *-u*, *--uts*[**=**__file__]::
-Create a new UTS namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new UTS namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_.
 
 *-U*, *--user*[**=**__file__]::
-Create a new user namespace. If _file_ is specified, then a persistent namespace is created by a bind mount.
+Create a new user namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_.
 
 *-C*, *--cgroup*[**=**__file__]::
-Create a new cgroup namespace. If _file_ is specified, then persistent namespace is created by bind mount.
+Create a new cgroup namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_.
 
 *-T*, *--time*[**=**__file__]::
-Create a new time namespace. If _file_ is specified, then a persistent namespace is created by a bind mount. The *--monotonic* and *--boottime* options can be used to specify the corresponding offset in the time namespace.
+Create a new time namespace. If _file_ is specified, then the namespace is made persistent by creating a bind mount at _file_. The *--monotonic* and *--boottime* options can be used to specify the corresponding offset in the time namespace.
 
 *-f*, *--fork*::
 Fork the specified _program_ as a child process of *unshare* rather than running it directly. This is useful when creating a new PID namespace. Note that when *unshare* is waiting for the child process, then it ignores *SIGINT* and *SIGTERM* and does not forward any signals to the child. It is necessary to send signals to the child process.
-- 
2.31.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation
  2021-09-09  0:08 [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Michael Kerrisk
  2021-09-09  0:08 ` [PATCH 2/2] unshare.1.adoc: Improve wording re creation of bind mounts Michael Kerrisk
@ 2021-09-21  8:47 ` Karel Zak
  1 sibling, 0 replies; 3+ messages in thread
From: Karel Zak @ 2021-09-21  8:47 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: util-linux

On Thu, Sep 09, 2021 at 02:08:27AM +0200, Michael Kerrisk wrote:
>  sys-utils/unshare.1.adoc | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)

Applied (both patches), thanks.

 Karel


-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-09-21  8:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-09-09  0:08 [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Michael Kerrisk
2021-09-09  0:08 ` [PATCH 2/2] unshare.1.adoc: Improve wording re creation of bind mounts Michael Kerrisk
2021-09-21  8:47 ` [PATCH 1/2] unshare.1.adoc: Improve wording re namespace creation Karel Zak

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).