From: "Chris Weiss" <chris@free-source.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: should the module script be invoked every time?
Date: Mon, 09 Jun 2003 15:12:15 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105517163314509@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103825785302736@msgid-missing>
I'm new to the list, bringing up an old topic becasue I too had the same issue and
it doesn't seem to have been resolved on the list or in the docs.
> >The script is now /etc/hotplug/usb/visor, since it's the visor module
> >that supports the palms.
>
> If you give your script some other name, like 'palmsync' or something
> else, your script shall run everytime you plug in the device.
>
If you rename the module in distmap, the kernel module won't load. But if the
kernel module is already loaded, the usermap won't get run at all.
The docs are WRONG on this! http://linux-hotplug.sourceforge.net/?selected=usb
"When your device support involves a kernel driver, instead of a purely user mode
driver, name the script after that driver. Similar scripts can trigger when you
connect a PDA, printer, or other device. "
This clearly implies that the script will run so long it has the same name as the
module...period. no editing maps, no if's and's or but's. This is wrong.
What needs to be done is copy the visor line from the distmap to the handmap,
renaming the module to your own name, then add the script of this new name.
Note that the usermap will NEVER get processed if the distmap or handmap sucessfully
do something usefull, but distmap and handmap will both always be processed. From
looking at the *.agent scripts, it also seems as though this feature ONLY applies to
usb.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
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:[~2003-06-09 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 20:49 should the module script be invoked every time? Gene Cash
2002-11-25 21:39 ` Pedro Lopez-Cabanillas
2002-11-25 21:57 ` David Brownell
2002-11-25 21:58 ` Gene Cash
2002-11-25 22:04 ` Zach Welch
2002-11-25 22:13 ` Pedro Lopez-Cabanillas
2002-11-25 22:40 ` Pedro Lopez-Cabanillas
2002-11-25 23:12 ` David Brownell
2002-11-26 16:04 ` Gene Cash
2003-06-09 15:12 ` Chris Weiss [this message]
2003-06-09 15:55 ` David Brownell
2003-06-09 17:19 ` Chris Weiss
2003-06-09 17:24 ` David Brownell
2003-06-09 21:25 ` Paul Hedderly
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-105517163314509@msgid-missing \
--to=chris@free-source.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).