From: Randy Dunlap <rdunlap@infradead.org>
To: David Howells <dhowells@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: AFS documentation
Date: Fri, 4 Dec 2020 21:46:31 -0800 [thread overview]
Message-ID: <de7da229-e0ea-6263-9dd2-e534cf49aaee@infradead.org> (raw)
In-Reply-To: <f77d3d67-ea63-4cce-fa6f-2977db078b74@infradead.org>
On 12/4/20 9:35 PM, Randy Dunlap wrote:
> Hi David,
>
> I was browsing Documentation/filesystems/afs.rst and fs/afs/super.c
> and had a few questions/comments.
>
> 1. afs.rst says:
>
> <<<
> When inserting the driver modules the root cell must be specified along with a
> list of volume location server IP addresses::
>
> modprobe rxrpc
> modprobe kafs rootcell=cambridge.redhat.com:172.16.18.73:172.16.18.91
>
> The first module is the AF_RXRPC network protocol driver. This provides the
> RxRPC remote operation protocol and may also be accessed from userspace. See:
>
> Documentation/networking/rxrpc.rst
>
> The second module is the kerberos RxRPC security driver, and the third module
> is the actual filesystem driver for the AFS filesystem.
>>>>
>
> so that above mentions 3 modules but only lists (modprobes) 2 of them.
> Or am I missing something?
>
>
> 2. fs/afs/super.c seems to be willing to parse "source=" (Opt_source).
>
> Can you tell me the format & meaning of that mount option?
> and maybe even add it to the doc. file?
Ah, I see that source= is a general fs mount option. Never mind on that one. :)
--
~Randy
prev parent reply other threads:[~2020-12-05 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 5:35 AFS documentation Randy Dunlap
2020-12-05 5:46 ` Randy Dunlap [this message]
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=de7da229-e0ea-6263-9dd2-e534cf49aaee@infradead.org \
--to=rdunlap@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@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).