From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: replace dev.d/ with a rule based program execution
Date: Thu, 24 Feb 2005 21:04:44 +0000 [thread overview]
Message-ID: <1109279085.7242.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20050221181242.GA22891@vrfy.org>
On Thu, 2005-02-24 at 15:45 -0500, David Zeuthen wrote:
>On Thu, 2005-02-24 at 21:34 +0100, Kay Sievers wrote:
>>HAL needs this only in the coldplug case, so what about letting udevinfo
>>dumping a list of _all_ devpath -> node matches with a single call and
>>HAL can merge all the names in one go into the device objects?
>
>That would work, yeah.
So we should go for it? What format? Any options needed?
$ udevinfo -d
/block/fd0:/dev/fd0
/block/hda:/dev/hda
/class/input/mice:/dev/input/mice
/class/mem/null:/dev/null
...
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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-02-24 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 18:12 replace dev.d/ with a rule based program execution Kay Sievers
2005-02-22 8:08 ` Hannes Reinecke
2005-02-22 17:53 ` Harald Hoyer
2005-02-23 1:08 ` Marco d'Itri
2005-02-24 20:15 ` David Zeuthen
2005-02-24 20:34 ` Kay Sievers
2005-02-24 20:45 ` David Zeuthen
2005-02-24 21:04 ` Kay Sievers [this message]
2005-02-24 21:52 ` Kay Sievers
2005-02-24 22:03 ` David Zeuthen
2005-02-25 23:26 ` Greg KH
2005-02-26 0:28 ` Kay Sievers
2005-02-26 0:57 ` Marco d'Itri
2005-02-26 1:04 ` Kay Sievers
2005-02-26 1:06 ` Marco d'Itri
2005-02-26 2:22 ` 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=1109279085.7242.22.camel@localhost.localdomain \
--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).