From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Device has module AND init script
Date: Mon, 21 Jan 2002 03:17:44 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101158320730954@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101158194629165@msgid-missing>
> I have a joystick which has the usual module stack, but which also needs to
> have jscal executed upon hotplugging (via my script
> /etc/hotplug/usb/setupstick). There are three issues here:
>
> 1. The logical place to name the setup script is usb.usermap, but if any
> modules are found, usb.agent bypasses usb.usermap. Workaround: put the
> lines in usb.handmap.
Simplest is to just name your setup script after the name of the
relevant module ... perhaps "joydev", and use "case $PRODUCT"
in that script to trigger "jscal" (or "setupstick" etc) for this device.
> 2. Both modules and setup scripts have an order dependence which modprobe
> may not be able to 100% straighten out. Workaround: Use the source, Luke!
> The right effect is achieved if the script is listed first, then the most
> specific driver, to the most general. I'm not sure how order dependence
> could be enforced neatly, specifically to get the script executed last, so
> I didn't try to hack anything for this.
The sequence is always: modprobe, then run setup script
of that same name (if it exists). The setup scripts can run
modprobe itself, if that helps.
If that doesn't resolve your problem, then I'm not sure I understand
the issue you're trying to describe.
> 3. In the obsolete version in my distro (2001_04_24-1_6),
> ...
I'll look at that a bit later.
- Dave
_______________________________________________
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
prev parent reply other threads:[~2002-01-21 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 2:53 Device has module AND init script Jim Carter
2002-01-21 3:17 ` David Brownell [this message]
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-101158320730954@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).