From: "Aurélien Couderc" <aurelien.couderc2002@gmail.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
ms-nfs41-client-devel@lists.sourceforge.net
Subject: Linux script-driven idmapper, Linux idmapper for multi-site idmapping? Re: [Ms-nfs41-client-devel] [Announcement] NFSv4.2/NFSv4.1 filesystem client Windows driver binaries for Windows 10/11+WindowsServer 2019/2022/2025 for testing, 2026-04-27 ...
Date: Tue, 28 Apr 2026 10:41:39 +0200 [thread overview]
Message-ID: <CA+1jF5qEAR6GYf-_gnLQH1mwt4T6wECQD-CKB+S5MCMmUiQVCw@mail.gmail.com> (raw)
In-Reply-To: <CANH4o6PPZk3UwFBO+e2pF=5Z0-sZDNEJ9kReL9ZANH=VKpbw9w@mail.gmail.com>
On Mon, Apr 27, 2026 at 8:46 PM Martin Wege <martin.l.wege@gmail.com> wrote:
>
> Hello,
>
> Please test the binaries. The NFSv4.2/4.1 client is for Windows 10/11
> ARM64+AMD64+x86 and Windows Server 2019+2022+2025/AMD64, but
> Interoperability feedback with NFSv4.1/NFSv4.2 servers based on Linux
> 6.6+ LTS and 6.19+/7.1 would be great.
>
> News:
> See announcement below; New idmapper which maps any NFS user/group to
> any Windows user/group,
IMO the interesting bit here is the (bash, perl, python) script-driven
idmapper. It has much more flexibility, and covers the multi-site use
case (one NFS client connecting to several different NFS sites with
different account management rules), which the Linux idmapper
currently covers very poorly.
How difficult would it be to port this to Linux?
Aurélien
--
Aurélien Couderc <aurelien.couderc2002@gmail.com>
Big Data/Data mining expert, chess enthusiast
prev parent reply other threads:[~2026-04-28 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKAoaQkL_e0-5c8T1c6G7qQA_5vjf75MQffuy4J7x=AO90+ykA@mail.gmail.com>
2026-04-27 18:46 ` Fwd: [Ms-nfs41-client-devel] [Announcement] NFSv4.2/NFSv4.1 filesystem client Windows driver binaries for Windows 10/11+WindowsServer 2019/2022/2025 for testing, 2026-04-27 Martin Wege
2026-04-28 8:41 ` Aurélien Couderc [this message]
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=CA+1jF5qEAR6GYf-_gnLQH1mwt4T6wECQD-CKB+S5MCMmUiQVCw@mail.gmail.com \
--to=aurelien.couderc2002@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ms-nfs41-client-devel@lists.sourceforge.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).