linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Jaskaran Singh <jaskaransingh7654321@gmail.com>, corbet@lwn.net
Cc: mszeredi@redhat.com, ebiggers@google.com,
	linux-doc@vger.kernel.org, neilb@suse.com,
	linux-kernel@vger.kernel.org, tobin@kernel.org,
	stefanha@redhat.com, mchehab+samsung@kernel.org,
	akpm@linux-foundation.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	christian@brauner.io
Subject: Re: [Linux-kernel-mentees] [PATCH v2 3/3] docs: filesystems: Add mount map description in Content
Date: Mon, 18 Nov 2019 07:50:06 +0800	[thread overview]
Message-ID: <a5b17c43fbd2b186240252b5a7fbef9c6a0ad54d.camel@themaw.net> (raw)
In-Reply-To: <20191117172436.8831-4-jaskaransingh7654321@gmail.com>

On Sun, 2019-11-17 at 22:54 +0530, Jaskaran Singh wrote:
> The second paragraph of the content section does not properly
> describe how mount points are determined by autofs.
> 
> Replace the lines detailing how the determination of these mount
> points is "ad hoc" by a short description of the mount map syntax
> used by autofs.
> 
> Signed-off-by: Jaskaran Singh <jaskaransingh7654321@gmail.com>
> ---
>  Documentation/filesystems/autofs.rst | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/autofs.rst
> b/Documentation/filesystems/autofs.rst
> index 2f704e9c5dc0..c17f6bf0eb5d 100644
> --- a/Documentation/filesystems/autofs.rst
> +++ b/Documentation/filesystems/autofs.rst
> @@ -49,9 +49,10 @@ extra properties as described in the next section.
>  Objects can only be created by the automount daemon: symlinks are
>  created with a regular `symlink` system call, while directories and
>  mount traps are created with `mkdir`.  The determination of whether
> a
> -directory should be a mount trap or not is quite ad hoc, largely for
> -historical reasons, and is determined in part by the
> -*direct*/*indirect*/*offset* mount options, and the *maxproto* mount
> option.
> +directory should be a mount trap is based on a master map. This
> master
> +map is consulted by autofs to determine which directories are mount
> +points. Mount points can be *direct*/*indirect*/*offset*.
> +On most systems, the default master map is located at
> */etc/auto.master*.

Ok, lets just use this for now since it's better than what was
originally there and I'll put together an update after these
changes are merged.

What happens is actually a bit more complicated, the opening
sentence above this is talking about what happens with maps
associated with autofs mount points given in the master map,
not so much master map entries themselves.

>  
>  If neither the *direct* or *offset* mount options are given (so the
>  mount is considered to be *indirect*), then the root directory is

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2019-11-18  0:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 17:24 [Linux-kernel-mentees] [PATCH v2 0/3] docs: filesystems: convert autofs.txt to reST Jaskaran Singh
2019-11-17 17:24 ` [Linux-kernel-mentees] [PATCH v2 1/3] " Jaskaran Singh
2019-11-17 17:24 ` [Linux-kernel-mentees] [PATCH v2 2/3] docs: filesystems: Update code snippets in autofs.rst Jaskaran Singh
2019-11-17 17:24 ` [Linux-kernel-mentees] [PATCH v2 3/3] docs: filesystems: Add mount map description in Content Jaskaran Singh
2019-11-17 23:50   ` Ian Kent [this message]
2019-11-18 19:21 ` [Linux-kernel-mentees] [PATCH v2 0/3] docs: filesystems: convert autofs.txt to reST Jonathan Corbet

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=a5b17c43fbd2b186240252b5a7fbef9c6a0ad54d.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=akpm@linux-foundation.org \
    --cc=christian@brauner.io \
    --cc=corbet@lwn.net \
    --cc=ebiggers@google.com \
    --cc=jaskaransingh7654321@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=neilb@suse.com \
    --cc=stefanha@redhat.com \
    --cc=tobin@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).