From: Lionel Cons <lionelcons1972@gmail.com>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Fwd: Eregex support in nfsmount.conf for [ Server "Server_Name" ]?
Date: Tue, 21 Apr 2026 12:50:59 +0200 [thread overview]
Message-ID: <CAPJSo4WTedqW4N3Zs2-+RcNMGkaqw3U3818WtNTF0_B72u_g9g@mail.gmail.com> (raw)
In-Reply-To: <CAPJSo4WEkdPfLUcMN3t1Ea2ZTp3Ga6WEo=Y4UJ+FrEzidwxRGw@mail.gmail.com>
[[Repost, somehow the list didn't forward this]]
---------- Forwarded message ---------
From: Lionel Cons <lionelcons1972@gmail.com>
Date: Mon, 20 Apr 2026 at 09:20
Subject: Eregex support in nfsmount.conf for [ Server "Server_Name" ]?
To: linux-nfs <linux-nfs@vger.kernel.org>
Would it be possible to support POSIX extended regular expressions for
[ Server "Server_Name" ]?
It is a great mess with /etc/nfsmount.conf when you have Kubernetes,
or just lots of NFS servers, say 15000 NFS server machines. POSIX
eregex matching would reduce the pain a lot.
Lionel
prev parent reply other threads:[~2026-04-21 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 7:20 Eregex support in nfsmount.conf for [ Server "Server_Name" ]? Lionel Cons
2026-04-21 10:50 ` Lionel Cons [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=CAPJSo4WTedqW4N3Zs2-+RcNMGkaqw3U3818WtNTF0_B72u_g9g@mail.gmail.com \
--to=lionelcons1972@gmail.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).