linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Executing user script
Date: Tue, 27 Mar 2001 15:58:57 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98571422710538@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98564705605342@msgid-missing>

> I have a script that I want to call everytime that hotplug gets
> activated. (i.e. I want to notify my application everytime a USB device
> is added or removed) Is there a way to do this without hard coding
> my script name in one of the hotplug scripts?

Sounds exactly like when /etc/hotplug/usb.agent gets called, so
at some level you just want a enhanced hotplug agent behavior.

At this point there's no general hook to make that particular
behavioral change, so you'd have to modify or replace that
agent script.  Do you think this will be a common enough task
that the scripts should accomodate it directly?  You didn't say
what your "application" does.

As Greg noted, if you have usbdevfs configured there are
other ways to get such notifications.  As just one example,
the Java USB library has a standard notifier interface that
calls out to report add/remove of devices and busses.  I
don't think the C "libusb" does such stuff now though.

- Dave




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-03-27 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 22:56 Executing user script Michael Wright
2001-03-27  5:19 ` Greg KH
2001-03-27 15:58 ` David Brownell [this message]
2001-03-27 18:08 ` Michael Wright
2001-03-27 18:41 ` David Brownell
2001-03-27 18:58 ` Gioele Barabucci

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=marc-linux-hotplug-98571422710538@msgid-missing \
    --to=david-b@pacbell.net \
    --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).