From: Robert Love <rml@tech9.net>
To: "Kevin P. Fleming" <kpfleming@cox.net>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] /sbin/hotplug multiplexor
Date: 14 Apr 2003 17:45:54 -0400 [thread overview]
Message-ID: <1050356754.3664.82.camel@localhost> (raw)
In-Reply-To: <3E9B2720.7020803@cox.net>
On Mon, 2003-04-14 at 17:24, Kevin P. Fleming wrote:
> Personally, this is one reason why I'd much rather see a daemon-based model
> where each interested daemon can "subscribe" to the messages it is interested
> in. It's very possible (and likely, i.e. udev) that the steps involved for the
> daemon to respond to the hotplug event are so lightweight that creating a
> subprocess to handle them would be very wasteful.
This screams for d-bus.
I spent the weekend reading about it and I spoke with some of the d-bus
hackers.
It is really neat and certainly something we should look into.
See http://www.freedesktop.org/software/dbus/
Robert Love
next prev parent reply other threads:[~2003-04-14 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:00 [RFC] /sbin/hotplug multiplexor Greg KH
2003-04-14 19:16 ` Oliver Neukum
2003-04-14 19:54 ` Greg KH
2003-04-14 20:09 ` Oliver Neukum
2003-04-14 20:33 ` Greg KH
2003-04-14 21:11 ` Oliver Neukum
2003-04-14 21:24 ` Kevin P. Fleming
2003-04-14 21:34 ` Greg KH
2003-04-14 21:45 ` Robert Love [this message]
2003-04-15 18:17 ` Frank van Maarseveen
2003-04-15 19:59 ` David Brownell
2003-04-14 21:30 ` Greg KH
2003-04-14 21:43 ` Oliver Neukum
2003-04-14 21:52 ` Greg KH
2003-04-14 22:19 ` Oliver Neukum
2003-04-14 22:44 ` Greg KH
2003-04-14 22:46 ` [RFC] /sbin/hotplug multiplexor - take 2 Greg KH
2003-04-15 19:19 ` David Brownell
2003-04-16 4:45 ` Greg KH
2003-04-16 6:22 ` Frederic Lepied
2003-04-18 22:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 22:04 [RFC] /sbin/hotplug multiplexor Arnd Bergmann
2003-04-14 22:21 ` Greg KH
2003-04-14 22:23 ` Arnd Bergmann
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=1050356754.3664.82.camel@localhost \
--to=rml@tech9.net \
--cc=kpfleming@cox.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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