From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS mounting - SOLVED
Date: Tue, 03 Dec 2024 11:44:50 +0000 [thread overview]
Message-ID: <2216351.Mh6RI2rZIc@rogueboard> (raw)
In-Reply-To: <2994796.e9J7NaK4W3@cube>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
On Tuesday 3 December 2024 11:29:15 GMT Peter Humphrey wrote:
> On Monday 2 December 2024 17:56:38 Greenwich Mean Time Michael wrote:
> > I had (another) look at the wiki. You're right, it seems to describe
> > NFSv3
> > only. I don't have NFSv3 here to compare. With NFSv4 you export the
> > global root directory to allow its subdirectories to be exported too - at
> > least this is how I understand it works on my systems.
>
> ...but today I see, buried in what you might call the small print: "If the
> NFS server or client support NFSv3 only, the full path to the exported
> directory (e.g. /export/home or /export/data) needs to be specified when
> mounting." [1]
>
> We could debate whether that's guidance enough.
>
> 1. https://wiki.gentoo.org/wiki/Nfs-utils#Mounting_exports , about a page
> down.
Yes, but further up all the IPv4 configuration syntax still shows v3 style
examples with '/export/foo' paths. I think there should be clearer
disambiguation with separate examples between v3 and v4. However, isn't NFS
v3 considered legacy by now?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-03 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 16:13 [gentoo-user] NFS mounting - SOLVED Peter Humphrey
2024-12-02 17:56 ` Michael
2024-12-03 11:29 ` Peter Humphrey
2024-12-03 11:44 ` Michael [this message]
2024-12-03 11:48 ` Peter Humphrey
2024-12-05 1:53 ` Peter Humphrey
2024-12-03 13:08 ` Matt Jolly
2024-12-03 13:28 ` Peter Humphrey
2024-12-04 2:20 ` Peter Humphrey
2024-12-05 0:55 ` Gentoo wiki [was: Re: [gentoo-user] NFS mounting - SOLVED] Alexis
2024-12-05 1:21 ` Peter Humphrey
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=2216351.Mh6RI2rZIc@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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