From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dracut: patch dracut-network
Date: Wed, 18 Jan 2023 20:01:46 +0100 [thread overview]
Message-ID: <20230118190146.AKQDchx3-HTSPvYzt7FfoA1y9esmckcxrDSwReUAdTg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41720@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/41720#issuecomment-1387606129
Comment:
This really belongs upstream, but for now seems fine to get us out of a logjam.
Some comments from upstream developers have indicated a desire to abandon support for anything besides systemd. While this is fine, it ought to be done in a single pass rather than death by 1000 cuts with subtle breakage like this. The upstream `network` module should properly dispatch to `network-legacy` in the meantime.
It is probably better to query whether the other backend modules are available and installable rather than looking for systemd and binaries that they require. Is this even possible in `module-setup.sh`?
next prev parent reply other threads:[~2023-01-18 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 18:48 [PR PATCH] " LaszloGombos
2023-01-18 19:01 ` ahesford [this message]
2023-01-18 19:44 ` LaszloGombos
2023-01-18 19:44 ` LaszloGombos
2023-01-18 19:47 ` LaszloGombos
2023-01-18 20:07 ` [PR PATCH] [Updated] " LaszloGombos
2023-01-18 20:15 ` LaszloGombos
2023-01-18 20:28 ` LaszloGombos
2023-01-18 20:32 ` [PR PATCH] [Updated] " LaszloGombos
2023-01-18 20:32 ` LaszloGombos
2023-01-18 20:51 ` [PR PATCH] [Updated] " LaszloGombos
2023-01-18 21:07 ` LaszloGombos
2023-01-18 23:37 ` classabbyamp
2023-01-18 23:37 ` [PR PATCH] [Merged]: " classabbyamp
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=20230118190146.AKQDchx3-HTSPvYzt7FfoA1y9esmckcxrDSwReUAdTg@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).