On Tue, 2024-02-13 at 21:28 +0100, Dan Shelton wrote: > On Fri, 9 Feb 2024 at 16:32, Jeff Layton <jlayton@xxxxxxxxxx> 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@xxxxxxxxx> 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? > Just someone with a will to write the patches for it (including a way to properly test it). I don't have a problem with making the public fh settable on the Linux server, but we'd need to hear more about how the client implementation would work. -- Jeff Layton <jlayton@xxxxxxxxxx>
