From: Wols Lists <antlists@youngman.org.uk>
To: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>,
Jes Sorensen <jes@trained-monkey.org>,
Oleksandr Shchirskyi <oleksandr.shchirskyi@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdmonitor: check if udev has finished events processing
Date: Tue, 9 Mar 2021 09:13:03 +0000 [thread overview]
Message-ID: <60473C1F.4080602@youngman.org.uk> (raw)
In-Reply-To: <51ec46c1-c632-b3a9-010f-8f13aee0e02c@linux.intel.com>
On 09/03/21 09:01, Tkaczyk, Mariusz wrote:
> On 08.03.2021 16:23, Jes Sorensen wrote:
>
>> I think it is reasonable to require libudev in 2021, so I have applied
>> this. However if someone feels there is a reason to not have this build
>> requirement, I will also accept a patch to make this dependency optional.
>
> Hi Jes,
>
> If community agrees for adding this dependency, I think that is a good
> time to drop all legacy code for handling cases if udev is not available.
> This code is dead, we cannot compile mdadm without libudev.
>
Is udev part of systemd? Are there alternate implementations for the
anti-systemd-holdouts? Iirc you don't need systemd itself to have udev,
but it might provoke a few screams ...
My current (gentoo) system is OpenRC, but that's still on KDE4 and
hasn't been updated in a couple of years (don't ask why). My new system
is currently being built and is gentoo/systemd, but it's clear the
anti-systemd sentiment is still strong ...
Cheers,
Wol
next prev parent reply other threads:[~2021-03-09 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 14:14 [PATCH] mdmonitor: check if udev has finished events processing Oleksandr Shchirskyi
2021-03-08 15:23 ` Jes Sorensen
2021-03-09 9:01 ` Tkaczyk, Mariusz
2021-03-09 9:13 ` Wols Lists [this message]
2021-03-09 9:45 ` Michael Fritscher
2021-03-09 11:17 ` Tkaczyk, Mariusz
2021-03-09 14:52 ` Jes Sorensen
2021-03-10 16:46 ` Tkaczyk, Mariusz
2021-03-11 12:58 ` Jes Sorensen
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=60473C1F.4080602@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=oleksandr.shchirskyi@intel.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