From: David Zeuthen <david@fubar.dk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and DBUS
Date: Sat, 28 Feb 2004 14:13:55 +0000 [thread overview]
Message-ID: <1077977635.1295.74.camel@powerbook.fubar.dk> (raw)
In-Reply-To: <20040217214449.GB12411@wonderland.linux.it>
(for some reason it seems that linux-hotplug-devel rejects my mail once
in a while so if you reply, please quote in full)
On Thu, 2004-02-26 at 18:00, Marco d'Itri wrote:
> On Feb 26, David Zeuthen <david@fubar.dk> wrote:
>
> >Maybe we should remove dbus support from udev and distributions and/or
> >hardware/hotplug abstractions like HAL can install their own callout
> >scripts (side-question: is it now as easy to install a callout as with
> >hotplug e.g. place an executable in /etc/hotplug.d/default/) which sends
> >a dbus message to a well-defined service (in HAL's case this would be
> >org.freedesktop.Hal.Manager).
> I'm not sure if this would work, because I think HAL wants to know which
> name has just been created by udev.
>
Right - my suggestion was for HAL to install a callout in udev, a script
really, that sends a D-BUS message to the HAL service.
> >What do you think?
>
> Last week I added this to README.Debian:
>
> D-BUS support
> ~~~~~~~~~~~~~
> It has been temporarily disabled for many reasons, among them it needing
> libraries in /usr/lib and introducing a pause of many seconds at boot time.
> A possible solution could be to build two versions of the daemon, start
> the bare one in the init script[1] and patch it to exit when SIGUSR1 has
> been received and the queue is empty.
>
>
> [1] or initrd or initramfs.
This could work as well, but it's really up to Greg to answer this one I
think. Since udev is now a daemon we should probably revisit D-BUS
support and add support for queries, I'll look into this.
Thanks,
David
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-28 14:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 21:44 udev and DBUS Marco d'Itri
2004-02-26 17:00 ` Marco d'Itri
2004-02-28 14:13 ` David Zeuthen [this message]
2004-03-10 16:31 ` udev and dbus David Zeuthen
2004-03-10 17:52 ` Kay Sievers
2004-03-10 19:18 ` Greg KH
2004-03-10 19:56 ` Greg KH
2004-03-10 19:57 ` Marco d'Itri
2004-03-10 20:00 ` Marco d'Itri
2004-03-10 20:02 ` Greg KH
2004-03-10 22:25 ` Patrick Mansfield
2004-03-10 22:37 ` Kay Sievers
2004-03-10 22:48 ` Greg KH
2004-03-11 1:28 ` Greg KH
2004-03-11 2:35 ` Kay Sievers
2004-03-11 8:55 ` Martin Waitz
2004-03-11 14:30 ` Kay Sievers
2004-03-11 15:06 ` David Zeuthen
2004-03-11 17:14 ` Kay Sievers
2004-03-11 17:23 ` Kay Sievers
2004-03-11 17:30 ` David Zeuthen
2004-03-11 17:41 ` David Zeuthen
2004-03-11 17:44 ` Kay Sievers
2004-03-11 18:12 ` Kay Sievers
2004-03-11 18:22 ` David Zeuthen
2004-03-11 18:32 ` Greg KH
2004-03-11 18:35 ` Greg KH
2004-03-11 18:36 ` Greg KH
2004-03-11 18:37 ` Kay Sievers
2004-03-11 18:38 ` Kay Sievers
2004-03-11 18:40 ` Kay Sievers
2004-03-11 18:47 ` Greg KH
2004-03-11 18:56 ` Kay Sievers
2004-03-12 0:18 ` Greg KH
2004-03-12 11:37 ` David Zeuthen
2004-03-12 15:54 ` Kay Sievers
2004-03-12 16:40 ` Daniel Stekloff
2004-03-12 17:17 ` Marco d'Itri
2004-03-12 17:26 ` Marco d'Itri
2004-03-13 15:22 ` David Zeuthen
2004-03-13 18:29 ` Kay Sievers
2004-03-14 19:59 ` Olaf Hering
2004-03-14 20:06 ` Kay Sievers
2004-03-14 20:11 ` Olaf Hering
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=1077977635.1295.74.camel@powerbook.fubar.dk \
--to=david@fubar.dk \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).