From: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>
To: linux-nfs@vger.kernel.org
Cc: Antonio Alvarez Feijoo <antonio.feijoo@suse.com>
Subject: [PATCH 0/2] systemd: Handle nfsroot
Date: Thu, 22 May 2025 08:59:08 +0200 [thread overview]
Message-ID: <cover.1747753109.git.antonio.feijoo@suse.com> (raw)
Every initrd generator (dracut, initramfs-tools, mkinitcpio, ...) has
its own implementation of nfsroot, i.e., allow to mount the real root
filesystem via NFS in the initrd.
The main goal of this patchset is to provide a common, centralized,
simple and modern systemd implementation of nfsroot that can be used
by any initrd generator. nfs-utils can easily provide it, and thus
also improve the maintainability of this feature.
The initial idea is to support NFSv4 only.
The matching patch for dracut (on top of openSUSE Tumbleweed) would be:
https://github.com/aafeijoo-suse/dracut/commit/f737e382988e77bd650dbb4951ef6925644fb523
OBS build with this patchset and the dracut patch:
https://download.opensuse.org/repositories/home:/afeijoo:/branches:/openSUSE:/Factory:/nfsroot/openSUSE_Tumbleweed/
Antonio Alvarez Feijoo (2):
systemd: Allow nfs-idmapd.service to be started without the server
systemd: Add a generator to mount /sysroot via NFSv4 in the initrd
.gitignore | 1 +
systemd/Makefile.am | 8 +-
systemd/nfs-idmapd.service | 2 +-
systemd/nfs.systemd.man | 62 +++++++--
systemd/nfsroot-generator.c | 243 ++++++++++++++++++++++++++++++++++++
systemd/systemd.c | 16 ++-
systemd/systemd.h | 1 +
7 files changed, 321 insertions(+), 12 deletions(-)
create mode 100644 systemd/nfsroot-generator.c
--
2.43.0
next reply other threads:[~2025-05-22 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:59 Antonio Alvarez Feijoo [this message]
2025-05-22 6:59 ` [PATCH 1/2] systemd: Allow nfs-idmapd.service to be started without the server Antonio Alvarez Feijoo
2025-06-05 10:53 ` Steve Dickson
2025-05-22 6:59 ` [PATCH 2/2] systemd: Add a generator to mount /sysroot via NFSv4 in the initrd Antonio Alvarez Feijoo
2025-06-05 10:53 ` Steve Dickson
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.1747753109.git.antonio.feijoo@suse.com \
--to=antonio.feijoo@suse.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