From: Andreas Jellinghaus <aj@leogic.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: status of /etc/hotplug/usb/
Date: Fri, 02 Dec 2005 19:42:05 +0000 [thread overview]
Message-ID: <dmq85v$c3b$1@sea.gmane.org> (raw)
In-Reply-To: <dmq2m1$oac$1@sea.gmane.org>
Kay Sievers wrote:
> Everything that is called "hotplug" should go, yes. :)
ok, thanks. does that include the linux kernel hotplug
mechanism? AFAIK there is the old /proc/sys/kernel/hotplug
based exec mechanism and a new netlink interface. will either
or both die?
>> what the replacement is (I guess udev rules files),
>
> For a lot of simple things udev rules are a good replacement, right.
> For everthing advanced, more complicated, or touching Desktop
> applications, HAL is the way to go. SUSE uses HAL(simple hook-in)
> for openct.
from openct point of view, it will deliver the same result?
i.e. hardware is attached, and openct-control attach ... is
started, if it is a hardware we support (I can add a fitting
file for hal).
does hal, udev or anything else provide coldplugging to me?
what openct currently does is this: the init script is
started and openct-control prepares everything (a status
file), starts fixed configured readers, and does a usb
scan for hotplugable readers it supports. it would be nicer
to send a feedback to some system "I'm ready know, if you
have any hardware for the list I gave you, please send
events".
> There is no paper, it just died silently. :)
>
> The rules can do everything that the map files did in the past. But as
> said, HAL is the proper place to do this. It can just do what
> /etc/hotplug/usb did, but ideally, any advanced hardware setup
> would expose its state trough HAL to the whole system with appropriate
> signals and properties on the corresponding HAL device object.
ok, I was about to add a udev rules file for debian. will talk
to them about using hal as alternative.
> That way all applications interested in a certain class of hardware
> just get the proper information and can adopt to the changing setup.
I understood hal always as some kind of message bus? I hope I don't
need to run a daemon or anything to receive signals? Since I can
express what I'm interested in in modules map compatible format
(and I guess many other apps can do so too), it would be nice
if some central authority could do all that matching. otherwise
we would write the same code in each usb hotplug'able application,
I guess.
Will join the hal mailing list and readup on the recent documentation.
thanks!
Andreas
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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:[~2005-12-02 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 18:08 status of /etc/hotplug/usb/ Andreas Jellinghaus
2005-12-02 18:51 ` Kay Sievers
2005-12-02 19:42 ` Andreas Jellinghaus [this message]
2005-12-02 21:01 ` Kay Sievers
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='dmq85v$c3b$1@sea.gmane.org' \
--to=aj@leogic.com \
--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).