Received-SPF: pass (google.com: domain of linux-nfs+bounces-3377-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Precedence: bulk
MIME-Version: 1.0
References: <CAAvCNcCTWbU-ejURuUC0_xhcoU3GF+2jX28rV4+2cKgfO5Lqxg@mail.gmail.com>
 <619bbf23-dbfe-4c26-adb9-1cc89f3f22a2@redhat.com>
In-Reply-To: <619bbf23-dbfe-4c26-adb9-1cc89f3f22a2@redhat.com>
From: Dan Shelton <dan.f.shelton@gmail.com>
Date: Fri, 24 May 2024 19:11:37 +0200
Message-ID: <CAAvCNcCGhZ917yerEOMcEEj7+_Yz5by8en2F4Yr5zLk0iQEGjg@mail.gmail.com>
Subject: Re: RFC2224 support in Linux /sbin/mount.nfs4?
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"

On Wed, 15 May 2024 at 23:46, Steve Dickson <steved@redhat.com> wrote:
>
> Hey!
>
> On 5/14/24 5:57 PM, Dan Shelton wrote:
> > Hello!
> >
> > Solaris, Windows and libnfs NFSv4 clients support RFC2224 URLs, which
> > provide platform-independent paths where resources can be mounted
> > from, i.e. nfs://myhost//dir1/dir2
> >
> > Could Linux /sbin/mount.nfs4 support this too, please?
> Why? What does it bring to the table that the Linux client
> does already do via v4... with the except, of course, public
> filehandles, which is something I'm pretty sure the Linux
> client will not support.

This is NOT for Linux only. Every OS has its own system to describe
shares, and not all are compatible. URLs are portable.

>
> So again why? WebNFS died with Sun... Plus RFC2224 talks
> about v2 and v3... How does it fit in a V4 world.

This is NOT about WebNFS or SUN, this is to make the job of admins easier.

Dan
-- 
Dan Shelton - Cluster Specialist Win/Lin/Bsd