From: Benjamin Coddington <bcodding@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/2] nfsuuid and udev examples
Date: Thu, 10 Feb 2022 13:01:09 -0500 [thread overview]
Message-ID: <cover.1644515977.git.bcodding@redhat.com> (raw)
Changes on v2:
- add forgotten aclocal/libuuid.m4
Benjamin Coddington (2):
nfsuuid: a tool to create and persist nfs4 client uniquifiers
nfsuuid: add some example udev rules
.gitignore | 1 +
aclocal/libuuid.m4 | 17 +++
configure.ac | 4 +
tools/Makefile.am | 1 +
tools/nfsuuid/Makefile.am | 8 ++
tools/nfsuuid/example_udev.rules | 28 +++++
tools/nfsuuid/nfsuuid.c | 203 +++++++++++++++++++++++++++++++
tools/nfsuuid/nfsuuid.man | 33 +++++
8 files changed, 295 insertions(+)
create mode 100644 aclocal/libuuid.m4
create mode 100644 tools/nfsuuid/Makefile.am
create mode 100644 tools/nfsuuid/example_udev.rules
create mode 100644 tools/nfsuuid/nfsuuid.c
create mode 100644 tools/nfsuuid/nfsuuid.man
--
2.31.1
next reply other threads:[~2022-02-10 18:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 18:01 Benjamin Coddington [this message]
2022-02-10 18:01 ` [PATCH v2 1/2] nfsuuid: a tool to create and persist nfs4 client uniquifiers Benjamin Coddington
2022-02-10 18:15 ` Chuck Lever III
2022-02-11 13:44 ` Steve Dickson
2022-02-11 15:48 ` Chuck Lever III
2022-02-11 18:28 ` Benjamin Coddington
2022-02-11 19:04 ` Chuck Lever III
2022-02-11 19:30 ` Benjamin Coddington
2022-02-11 20:00 ` Chuck Lever III
2022-02-11 20:16 ` Benjamin Coddington
2022-02-11 20:51 ` Chuck Lever III
2022-02-11 21:06 ` Benjamin Coddington
2022-02-14 0:04 ` NeilBrown
2022-02-14 11:15 ` Benjamin Coddington
2022-02-14 15:39 ` Chuck Lever III
2022-02-16 19:01 ` Benjamin Coddington
2022-02-16 19:35 ` Chuck Lever III
2022-02-16 20:44 ` Benjamin Coddington
2022-02-16 23:16 ` NeilBrown
2022-03-01 3:43 ` [PATCH] nfs.man: document requirements for NFS mounts in a container NeilBrown
2022-03-01 15:08 ` Chuck Lever III
2022-03-01 15:16 ` Chuck Lever III
2022-03-03 3:26 ` NeilBrown
2022-03-03 14:37 ` Trond Myklebust
2022-03-04 1:13 ` NeilBrown
2022-03-04 15:54 ` Steve Dickson
2022-03-04 16:15 ` Chuck Lever III
2022-03-04 16:54 ` Steve Dickson
2022-03-05 1:15 ` NeilBrown
2022-03-03 15:53 ` Chuck Lever III
2022-03-08 0:44 ` NeilBrown
2022-03-09 16:28 ` Chuck Lever III
2022-03-10 0:37 ` NeilBrown
2022-02-17 14:43 ` [PATCH v2 1/2] nfsuuid: a tool to create and persist nfs4 client uniquifiers Chuck Lever III
2022-02-14 22:40 ` NeilBrown
2022-02-10 18:01 ` [PATCH v2 2/2] nfsuuid: add some example udev rules Benjamin Coddington
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=cover.1644515977.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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 NNTP newsgroup(s).