From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: status of /etc/hotplug/usb/
Date: Fri, 02 Dec 2005 18:51:06 +0000 [thread overview]
Message-ID: <20051202185106.GA5669@vrfy.org> (raw)
In-Reply-To: <dmq2m1$oac$1@sea.gmane.org>
On Fri, Dec 02, 2005 at 07:08:15PM +0100, Andreas Jellinghaus wrote:
> Hi,
>
> I read that debian killed that directory and thus
> openct was no longer working(1).
>
> So I wonder what the position of the hotplug and udev
> people here is on /etc/hotplug/usb/
Everything that is called "hotplug" should go, yes. :)
> 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.
> and if there is some > paper with reasoning and suggestions
> for the transition. any link would be fine.
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.
That way all applications interested in a certain class of hardware
just get the proper information and can adopt to the changing setup.
Kay
-------------------------------------------------------
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 18:51 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 [this message]
2005-12-02 19:42 ` Andreas Jellinghaus
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=20051202185106.GA5669@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).