From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 01/10] Manual pages: unshare.1: EXAMPLES: improve persistent mount namespace example
Date: Thu, 28 May 2020 16:58:15 +0200 [thread overview]
Message-ID: <20200528145823.978508-1-mtk.manpages@gmail.com> (raw)
The text describing the persistent mount namespace example
is rather confused. Explain more clearly the purpose of making
the parent directory a bind mount with private propagation.
Also make a few other wording improvements.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
sys-utils/unshare.1 | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/sys-utils/unshare.1 b/sys-utils/unshare.1
index ea170b13a..e3a23f78c 100644
--- a/sys-utils/unshare.1
+++ b/sys-utils/unshare.1
@@ -304,9 +304,16 @@ FOO
.EE
.in
.PP
-Establish a persistent mount namespace referenced by the bind mount
-/root/namespaces/mnt. This example shows a portable solution, because it
-makes sure that the bind mount is created on a shared filesystem.
+The following commands
+establish a persistent mount namespace referenced by the bind mount
+.IR /root/namespaces/mnt .
+In order to ensure that this bind mount does not get propagated
+to other mount namespaces,
+the parent directory
+.RI ( /root/namespaces )
+is first made a bind mount with
+.I private
+propagation.
.PP
.in +4n
.EX
--
2.26.2
next reply other threads:[~2020-05-28 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:58 Michael Kerrisk (man-pages) [this message]
2020-05-28 14:58 ` [PATCH 02/10] Manual pages: unshare.1: typo fix Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 03/10] Manual pages: setpriv.1: Minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 04/10] Manual pages: mount.8, umount.8: Clarify that "namespace" means "mount namespace" Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 05/10] Manual pages: mount.8, umount.8: Consistently format pathnames with italic Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 06/10] Manual pages: mount.8: SEE ALSO: add some obvious references Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 07/10] Manual pages: mount.8: Typo fix (remove an accidental paragraph break) Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 08/10] Manual pages: mount.8: Rewrite FILESYSTEM-SPECIFIC MOUNT OPTIONS intro Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 09/10] Manual pages: umount.8: use "filesystem" consistently Michael Kerrisk (man-pages)
2020-05-29 7:46 ` [PATCH 01/10] Manual pages: unshare.1: EXAMPLES: improve persistent mount namespace example Karel Zak
2020-05-29 8:54 ` John Paul Adrian Glaubitz
2020-05-29 12:43 ` Karel Zak
2020-05-29 13:22 ` Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200528145823.978508-1-mtk.manpages@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).