From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: extras/dbus/udev_dbus
Date: Fri, 14 May 2004 11:50:20 +0000 [thread overview]
Message-ID: <20040514115020.GB19004@vrfy.org> (raw)
After a conversation with David Zeuthen on the hal mailing list, I want
to ask for the complete removal of the currently broken dbus callout.
We've added the dbus callout to send events to hal and possibly other
applications, but it seems impossible to fix the issues with dbus and our
low level udev architecture. There is no easy fix to prevent concurrently
running dbus callouts, all wanting to claim the same service on the bus,
which is ugly for the receiving applications.
Hal solved this issue by placing its own callout in the dev.d/ directory,
which invokes a method inside the permanentely running hald daemon,
instead of trying to claim a own service.
I can't think of any application, that wants to be notified about a
udev event through dbus. Any lower level program better places it's own
callout in dev.d/ and higher level applications should listen to hal
events instead.
So if nobody really needs this callout _and_ is willing to fix the issues,
I vote for a complete removal from the udev tree.
The udev_selinux callout is pretty useless too, cause it's better replaced
by a call to selinux's restorecon(8).
thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&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 reply other threads:[~2004-05-14 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 11:50 Kay Sievers [this message]
2004-05-14 12:21 ` extras/dbus/udev_dbus Harald Hoyer
2004-05-14 22:09 ` extras/dbus/udev_dbus Greg KH
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=20040514115020.GB19004@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).