From: Salvatore Bonaccorso <carnil@debian.org>
To: NeilBrown <neilb@suse.de>
Cc: Steve Dickson <steved@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: systemd/50-nfs.conf and interoperability issue with intramfs-tools not including sunrpc into initrd
Date: Mon, 14 Nov 2022 17:45:26 +0100 [thread overview]
Message-ID: <Y3Jwpr3394H2zwOp@eldamar.lan> (raw)
In-Reply-To: <166656275785.12462.14027406790454668194@noble.neil.brown.name>
Hi Neil,
On Mon, Oct 24, 2022 at 09:05:57AM +1100, NeilBrown wrote:
> On Sat, 22 Oct 2022, Salvatore Bonaccorso wrote:
> > Hi Neil, hi Steve,
> >
> > In Debian for the update including the systemd/50-nfs.conf there was a
> > report that sunrpc is not included anymore in the initrd through the
> > initramfs-tools hooks.
> >
> > The report is at https://bugs.debian.org/1022172
> >
> > As we would not start to diverge again from nfs-utils upstream and
> > keep in sync with upstream as much as possible I would like to retain
> > whatever is from nfs-utils upstream downstream as well.
> >
> > Marco d'Intri suggested there three possible solutions, of which one
> > could be done in nfs-utils (whereas the other two are either in kmod
> > upstream or initramfs-tools upstream). The nfs-utils one would be to
> > replace the modprobe configuration with a set of udev rules instead.
> >
> > What do you think?
>
> I don't object to nfs-utils being changed to install an appropriate udev
> rules file instead of the modprobe.d file. Would you be willing to
> develop, test, and post a patch?
Thank you for this positive answer! Yes, I have asked affected persons
if they can help contribute to this and submit it upstream.
The specfic bug in Debian for nfs-utils in Debian is now
https://bugs.debian.org/1024082
Regards,
Salvatore
next prev parent reply other threads:[~2022-11-14 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 14:09 systemd/50-nfs.conf and interoperability issue with intramfs-tools not including sunrpc into initrd Salvatore Bonaccorso
2022-10-23 22:05 ` NeilBrown
2022-11-14 16:45 ` Salvatore Bonaccorso [this message]
2022-11-25 13:11 ` Salvatore Bonaccorso
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=Y3Jwpr3394H2zwOp@eldamar.lan \
--to=carnil@debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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).