From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: Jes Sorensen <jes@trained-monkey.org>,
Michael Fritscher <michael@fritscher.net>,
Wols Lists <antlists@youngman.org.uk>,
Oleksandr Shchirskyi <oleksandr.shchirskyi@intel.com>
Cc: linux-raid@vger.kernel.org, artur.paszkiewicz@intel.com
Subject: Re: [PATCH] mdmonitor: check if udev has finished events processing
Date: Wed, 10 Mar 2021 17:46:13 +0100 [thread overview]
Message-ID: <4c6c4262-7590-df44-e8cb-eca6bc936287@linux.intel.com> (raw)
In-Reply-To: <6c833d95-7610-a3c3-01ca-3167a3e80335@trained-monkey.org>
On 09.03.2021 15:52, Jes Sorensen wrote:
> On 3/9/21 6:17 AM, Tkaczyk, Mariusz wrote:
>> On 09.03.2021 10:45, Michael Fritscher wrote:
>>> Am 09.03.21 um 10:13 schrieb Wols Lists:
>>>> 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
>>>>
>>>
>>> Good day,
>>>
>>> there is e.g. eudev ( https://wiki.gentoo.org/wiki/Project:Eudev ) with
>>> the explicit target to be used without systemd.
>>
>> It is a udev replacement and offers similar functionality.
>> I'm wondering on configuration without udev (systemd or other forks).
>> Is it still a case?
>
> This is my main concern, small embedded devices that don't use systemd.
> I've never been a big systemd fan, but it's how the chips have fallen,
> so I am not overly worried about a couple of fanatics.
>
> If eudev can do the trick, that would be great.
>
> Cheers,
> Jes
>
Hello,
Mdadm is in use in openwrt without udev (thanks to Artur for research).
They are using hotplug scripts:
https://openwrt.org/docs/guide-user/base-system/hotplug#coldplug
To provide compatibility with libudev dependency they wrote small shim:
https://openwrt.org/packages/pkgdata/libudev-fbsd
Unfortunately, not all libudev functions are defined, mdadm compilation
there might be problematic:
https://openwrt.org/packages/pkgdata_lede17_1/mdadm
Now, it makes sense to define libudev as optional dependency.
It should be done before new release, Intel will do that.
Anyway, I still think that we should drop udev detection from mdadm.
I there is no systemd-udevd, we should expect other tool to provide
similar functionality, like hotplug scripts, eudev.
IMO mdadm doesn't need to create any link.
Mariusz
next prev parent reply other threads:[~2021-03-10 16:47 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
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 [this message]
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=4c6c4262-7590-df44-e8cb-eca6bc936287@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=antlists@youngman.org.uk \
--cc=artur.paszkiewicz@intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=michael@fritscher.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.