From: Miklos Szeredi <mszeredi@redhat.com>
To: Karel Zak <kzak@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>,
Jeff Layton <jlayton@redhat.com>,
"Eric W. Biederman" <ebiederm@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
util-linux@vger.kernel.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: User-visible context-mount API
Date: Thu, 18 Jan 2018 10:48:24 +0100 [thread overview]
Message-ID: <CAOssrKeRaA77NUctnwQ0=r6xMg_o1UVbqqTBJ60q-n4DP_LvDw@mail.gmail.com> (raw)
In-Reply-To: <20180117110633.zneqvnjzgxkv4yc2@ws.net.home>
On Wed, Jan 17, 2018 at 12:06 PM, Karel Zak <kzak@redhat.com> wrote:
>> Documenting --make-private thing properly would also help. To me the
>> wording "make private" strongly implies "I want to make submounts
>> private to this instance". See for example rhbz#1432211.
>
> All propagation stuff is poorly documented in mount.8. It would be
> nice to add section about it to the man page. Volunteer? (My skills to
> explain this topic to end-users is pretty limited...)
Propagation is common to mount(2) and there's some info in there
already, but fine points like this are not explained.
Maybe a new page in section 7?
Thanks,
Miklos
next prev parent reply other threads:[~2018-01-18 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28167.1516032442@warthog.procyon.org.uk>
[not found] ` <CAOssrKdgudK7kKbhQBAnV9EwzHBq=4+9M26JGfmhNDGrGXmnFg@mail.gmail.com>
[not found] ` <1643.1516117204@warthog.procyon.org.uk>
[not found] ` <CAOssrKdn-ZhOB9V28uL-JK9zgNGJzF4cFBeyoqLLj4pADqNFVQ@mail.gmail.com>
[not found] ` <20180117041727.GS13338@ZenIV.linux.org.uk>
2018-01-17 9:53 ` User-visible context-mount API Miklos Szeredi
2018-01-17 11:06 ` Karel Zak
2018-01-18 9:48 ` Miklos Szeredi [this message]
2018-01-19 2:27 ` Al Viro
2018-01-19 6:32 ` Al Viro
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='CAOssrKeRaA77NUctnwQ0=r6xMg_o1UVbqqTBJ60q-n4DP_LvDw@mail.gmail.com' \
--to=mszeredi@redhat.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@redhat.com \
--cc=jlayton@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=util-linux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).