From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Using udev to collect device information
Date: Tue, 27 Jun 2006 00:01:03 +0000 [thread overview]
Message-ID: <20060627000103.GA25090@kroah.com> (raw)
In-Reply-To: <44A06971.3020507@us.ibm.com>
On Mon, Jun 26, 2006 at 04:10:41PM -0700, Eric Munson wrote:
> I am working on a project that maintains a list of active hardware on a
> machine and we want to make it hotplug "aware". Making udev call our
> process for adding or removing an entry to or from our list each time
> hardware is added or removed seems easy enough, but I have several
> questions:
>
> 1. Our system will be thread safe, but if we are calling the hotplug
> updater each time a device is added or removed with the rules:
> ACTION="add" RUN+="/usr/sbin/program"
> and
> ACTION="remove" RUN+="/usr/sbin/program"
> Are we going to cause serious slow downs for the rest of the system if
> we are flooded with adds/removes? The program that we will be running
> won't be terribly slow but it will include some disk IO.
It all depends on what your /usr/sbin/program does, we can't answer that
for you.
> 2. How can I pass information about the event, things like what device
> is being added/removed into the program being called? Does udev provide
> any of this information during rule execution (I assume that udev has
> it, I just need to know where to get it)?
>
> Sorry if this is a gross abuse of udev, but we are looking to plug into
> a "hotplug" like system without requiring our users to install the
> linux-hotplug system so if there is a better way to accomplish the same
> thing please let me know.
No, this is a fine way. But why not just hook into HAL? It already
does all of this for you, and you can get it to send you DBUS messages
for any new device in the system.
Or, if you don't like how HAL works, you should at least look into how
it ties into udev, as that sounds like the same exact way you want to do
things. But don't reinvent the wheel if you don't have to.
thanks,
greg k-h
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-06-27 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 23:10 Using udev to collect device information Eric Munson
2006-06-27 0:01 ` Greg KH [this message]
2006-06-27 16:31 ` 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=20060627000103.GA25090@kroah.com \
--to=greg@kroah.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).