Date: Fri, 14 May 2021 00:46:07 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Rick Macklem <rmacklem@uoguelph.ca>, freebsd-fs <freebsd-fs@freebsd.org> Subject: =?UTF-8?Q?Re=3a_autofs_+_default_/net_map_+_NFS4_=e2=80=94_how_to?= =?UTF-8?Q?=3f?= Message-ID: <161f2cd2-2edd-0a73-836c-bfbc3e0490e6@FreeBSD.org> In-Reply-To: <YQXPR0101MB09686590F5AC4BC617D5A0F6DD519@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> References: <36080caf-4aa1-d262-cb93-9df9b72f884d@FreeBSD.org> <YQXPR0101MB09686590F5AC4BC617D5A0F6DD519@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14.05.2021 0:10, Rick Macklem wrote: > lev wrote: > [stuff snipped] >> I could mount "blob:/home" or "blob:/ports" with mount -t nfs like this: >> >> # mount -t nfs -o nfsv4,tcp blob:/home /mnt > Oh, and you might want to consider using "minorversion=1" (or even 2 > if/when you are running FreeBSD13 or later). > NFSv4.1 (and 4.2) are much better protocols than NFSv4.0 and the > implementations should now be pretty solid, so long as you avoid > enabling delegations (off by default). Could it be done on server-side? I don't want to touch all clients. Like "Prefer 4.2, but allow 4.0 too"? > - NFSv4.1 was a minor revision in name only. The RFC is only 500+ pages long. "only"! :) -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?161f2cd2-2edd-0a73-836c-bfbc3e0490e6>