All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: Michael Fritscher <michael@fritscher.net>,
	Wols Lists <antlists@youngman.org.uk>,
	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 12:17:20 +0100	[thread overview]
Message-ID: <b604528a-2e5e-e5d7-0d05-e72e14f991e9@linux.intel.com> (raw)
In-Reply-To: <1b5b0495-c645-7f81-24f4-07fbad54ca0e@fritscher.net>

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.
> 
> Best regards,
> Michael Fritscher
> 

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?

Thanks,
Mariusz

  reply	other threads:[~2021-03-09 11:18 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 [this message]
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=b604528a-2e5e-e5d7-0d05-e72e14f991e9@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=antlists@youngman.org.uk \
    --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.