From: Dan Shelton <dan.f.shelton@gmail.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Tom Talpey <tom@talpey.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Public NFSv4 handle?
Date: Tue, 13 Feb 2024 21:28:00 +0100 [thread overview]
Message-ID: <CAAvCNcAsow-QTPYLm0fUNX3K5X4Aci=aFi+hi4a0S8k19oa-KA@mail.gmail.com> (raw)
In-Reply-To: <14e1e8c8613c74d07cb0cefbcebbf79a3a57311e.camel@kernel.org>
On Fri, 9 Feb 2024 at 16:32, Jeff Layton <jlayton@kernel.org> wrote:
>
> On Thu, 2024-02-08 at 21:37 -0500, Tom Talpey wrote:
> > On 2/8/2024 7:19 PM, Dan Shelton wrote:
> > > ?
> > >
> > > On Thu, 25 Jan 2024 at 02:48, Dan Shelton <dan.f.shelton@gmail.com> wrote:
> > > >
> > > > Hello!
> > > >
> > > > Do the Linux NFSv4 server and client support the NFS public handle?
> >
> > Are you referring the the old WebNFS stuff? That was a v2/v3 thing,
> > and, I believe, only ever supported by Solaris.
> >
>
> One more try! I think my MUA was having issues this morning.
>
> NFSv4.1 supports the PUTPUBFH op:
>
> https://www.rfc-editor.org/rfc/rfc8881.html#name-operation-23-putpubfh-set-p
>
> ...but this op is only for backward compatibility. The Linux server
> returns the rootfh (as it SHOULD).
No, I do not consider this "backward compatibility". The "public"
option is also intended for public servers, like package mirrors (e.g.
Debian), to have a better solution than http or ftp.
What does it take to implement a "public" export option?
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
next prev parent reply other threads:[~2024-02-13 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:48 Public NFSv4 handle? Dan Shelton
2024-02-09 0:19 ` Dan Shelton
2024-02-09 2:37 ` Tom Talpey
2024-02-09 11:09 ` Jeff Layton
2024-02-09 14:52 ` Jeff Layton
2024-02-09 15:32 ` Jeff Layton
2024-02-13 20:28 ` Dan Shelton [this message]
2024-02-13 20:42 ` Jeff Layton
2024-02-13 20:58 ` Trond Myklebust
2024-02-14 6:12 ` Cedric Blancher
2024-02-15 17:25 ` Frank Filz
2024-02-13 21:16 ` Chuck Lever III
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='CAAvCNcAsow-QTPYLm0fUNX3K5X4Aci=aFi+hi4a0S8k19oa-KA@mail.gmail.com' \
--to=dan.f.shelton@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@talpey.com \
/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).