All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: mtk.manpages@gmail.com, util-linux@vger.kernel.org
Subject: Re: [PATCH 1/9] Manual pages: nsenter.1, unshare.1: update references to *_namespaces(7) pages
Date: Mon, 25 May 2020 15:13:18 +0200	[thread overview]
Message-ID: <4d4bb487-4a9c-1fcb-71a6-059379597d15@gmail.com> (raw)
In-Reply-To: <20200525121745.rmdn47zlchtf76fh@ws.net.home>

On 5/25/20 2:17 PM, Karel Zak wrote:
> On Sat, May 23, 2020 at 08:43:17AM +0200, Michael Kerrisk wrote:
>>  sys-utils/nsenter.1 | 6 +++---
>>  sys-utils/unshare.1 | 6 +++---
>>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> Applied all 9 patches, thanks.

Thanks, Karel.

A follow-up question. There was one piece of the unshare(1) examples
that I did not try to rework, because I simply don't understand it:

       Establish  a  persistent  mount  namespace  referenced by the bind
       mount /root/namespaces/mnt.  This example shows a  portable  solu‐
       tion,  because  it  makes sure that the bind mount is created on a
       shared filesystem.

           # mount --bind /root/namespaces /root/namespaces
           # mount --make-private /root/namespaces
           # touch /root/namespaces/mnt
           # unshare --mount=/root/namespaces/mnt

I think you wrote this example. What does the sentence "This example shows
a portable solution, because it makes sure that the bind mount is created
on a shared filesystem" mean? I think this needs clarification, and I'd try
to do so, but it's not clear to me what the sentence is trying to say.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-05-25 13:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23  6:43 [PATCH 1/9] Manual pages: nsenter.1, unshare.1: update references to *_namespaces(7) pages Michael Kerrisk
2020-05-23  6:43 ` [PATCH 2/9] Manual pages: nsenter.1, unshare.1: add a reference to time_namespaces(7) Michael Kerrisk
2020-05-23  6:43 ` [PATCH 3/9] Manual pages: nsenter.1, unshare.1: remove repeated references to clone(2) Michael Kerrisk
2020-05-23  6:43 ` [PATCH 4/9] Manual pages: unshare.1: improve intro paragraphs Michael Kerrisk
2020-05-23  6:43 ` [PATCH 5/9] Manual pages: nsenter.1: clarify the intro discussion Michael Kerrisk
2020-05-23  6:43 ` [PATCH 6/9] Manual pages: nsenter.1: note that 'file' can be a bind mount Michael Kerrisk
2020-05-23  6:43 ` [PATCH 7/9] Manual pages: unshare.1: fix examples, part 1 Michael Kerrisk
2020-05-23  6:43 ` [PATCH 8/9] Manual pages: unshare.1: fix examples, part 2 Michael Kerrisk
2020-05-23  6:43 ` [PATCH 9/9] Manual pages: unshare.1: fix examples, part 3 Michael Kerrisk
2020-05-25 12:17 ` [PATCH 1/9] Manual pages: nsenter.1, unshare.1: update references to *_namespaces(7) pages Karel Zak
2020-05-25 13:13   ` Michael Kerrisk (man-pages) [this message]
2020-05-26  8:50     ` Karel Zak
2020-05-27 12:37       ` Michael Kerrisk (man-pages)

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=4d4bb487-4a9c-1fcb-71a6-059379597d15@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.