From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: should the module script be invoked every time?
Date: Mon, 25 Nov 2002 21:39:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103826054405963@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103825785302736@msgid-missing>
On Monday 25 November 2002 21:49, Gene Cash wrote:
> 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.
Is there a reason to name the hotplug scripts like the modules?
There was the same issue some time ago with the usb-midi firmware loader
script, but now the script is named 'ezusbmidi' instead 'usb-midi', and our
problems are gone.
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
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:[~2002-11-25 21:39 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 [this message]
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
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-103826054405963@msgid-missing \
--to=plcl@telefonica.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.