public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: udev (viable) alternatives ?
Date: Mon, 10 Nov 2014 07:30:43 -0500	[thread overview]
Message-ID: <CAGfcS_=VHEByYaaaAnB+uQQz647486K0qzaO-2vezSc8PF0rsQ@mail.gmail.com> (raw)
In-Reply-To: <54609BD1.2000206@libertytrek.org>

On Mon, Nov 10, 2014 at 6:04 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>
> eudev is looking more attractive every day... but can it continue to
> work and be supported if Lennart gets his way and upstream udev stops
> working without systemd?
>

Well, there are no plans to make udev stop working without systemd as
far as I can tell.  HOWEVER, there ARE plans to require using kdbus to
communicate with udev, and for that to work there needs to be a
userspace initialization of kdbus/etc.

Udev is probably just be the tip of the iceberg.  Lots of packages use
dbus, and it seems likely to me that many will start switching to
kdbus.  The fact that it is going to be a standard kernel IPC
mechanism also means that packages that have avoided dbus in the
interests of not having large dependencies may start picking it up as
well - it might be used even on embedded systems.

I have no idea how much work is involved or if anybody else is
interested in doing it.  If busybox is willing to have their mdev
module, I don't see why they wouldn't want a kdbus module to go along
with that.  However, that is speaking mostly out of ignorance, and
somebody needs to write the code.

I don't think avoiding kdbus is going to be a viable long-term
solution.  Folks who don't want to run systemd need to start planning
for this, and cross "needs dbus" off their list of reasons not to use
systemd.

--
Rich


  reply	other threads:[~2014-11-10 12:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 15:25 [gentoo-user] udev (viable) alternatives ? James
2014-09-25 17:47 ` Dale
2014-09-25 18:17 ` Samuli Suominen
2014-09-25 19:03   ` [gentoo-user] " James
2014-09-25 19:32     ` Dale
2014-09-26  0:23     ` Walter Dnes
2014-09-26  3:27       ` Alan McKinnon
2014-09-26  8:07         ` Neil Bothwick
2014-09-26  8:22           ` Canek Peláez Valdés
2014-09-26  8:46             ` Neil Bothwick
2014-09-26  8:47             ` Samuli Suominen
2014-09-26  9:04               ` Samuli Suominen
2014-09-26 16:47                 ` David W Noon
2014-09-27  2:06                   ` Samuli Suominen
2014-09-26  5:04     ` Samuli Suominen
2014-11-10 11:04       ` Tanstaafl
2014-11-10 12:30         ` Rich Freeman [this message]
2014-11-10 13:23           ` Tanstaafl
2014-11-10 14:23             ` Rich Freeman
2014-11-10 15:48         ` Samuli Suominen
2014-11-10 16:01           ` Tanstaafl
2014-11-11  5:20           ` Walter Dnes
2014-11-11  5:33             ` Samuli Suominen
2014-11-11  5:35             ` Canek Peláez Valdés
2014-11-11 12:18             ` Rich Freeman
2014-11-13 17:08               ` Walter Dnes
2014-11-17 10:27                 ` Tom H

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='CAGfcS_=VHEByYaaaAnB+uQQz647486K0qzaO-2vezSc8PF0rsQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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