From: Robert Anderson <rea@q.sr.unh.edu>
To: linux-hotplug@vger.kernel.org
Subject: Re: possible change to usb.agent
Date: Mon, 14 Jan 2002 20:29:30 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101104039207049@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101097712222027@msgid-missing>
>Date: Mon, 14 Jan 2002 11:17:38 -0800
>From: David Brownell <david-b@pacbell.net>
>X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
>Content-type: text/plain; charset=iso-8859-1
>X-Priority: 3
>X-MSMail-priority: Normal
>
>> I used the jPhoto example, except where they used "usb.handmap" I used
>> "usb.usermap". It seemed like the comments indicated it should be in
>> the "usb.usermap" section to me, perhaps I misunderstood the comments?
>
>That was a bug in the jPhoto "hotsync" example, which is
>now fixed. (Thanks for reporting that!) "usermap" is correct.
>
>Given that, I don't think there's a bug. When you load a kernel
>module "foo", if there's a script /etc/hotplug/usb/foo it will also
>be run. You shouldn't need a "usermap" entry in addition to
>a kernel module ... just name the script after the module.
>
>- Dave
Thanks for getting back to me so quickly.
Obviously you know what you're talking about, and it indeed works
great if I simply link my script in as "/etc/hotplug/usb/usb-storage".
Just to be safe I'm put in a test to exit if the $PRODUCT not equal to
'4cb/100/100'.
I can see this approach works great now, but I do wonder what happens
when I get an rpm that installs scripts for my MP3 player, Camera, and
external harddrive. I thought that was the idea behind the
"usb.usermap" file and all the matching options. The way I had
changed it the device driver would load as well as anything matching
in the usb.usermap file. It allowed individual and multiple scripts
per device.
Just adding my 2 cents. Feel free to ignore it, I'm very happy it
works and is a lot easier than I had originally thought. Keep up the
great work.
--------------------------------------------------------------
Robert E. Anderson email: rea@sr.unh.edu
Systems Programmer phone: (603) 862-3489
UNH Research Computing Center fax: (603) 862-1761
--------------------------------------------------------------
_______________________________________________
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-01-14 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 2:58 possible change to usb.agent Robert Anderson
2002-01-14 19:17 ` David Brownell
2002-01-14 20:29 ` Robert Anderson [this message]
2002-01-14 22:33 ` David Brownell
2002-01-15 14:43 ` Robert Anderson
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-101104039207049@msgid-missing \
--to=rea@q.sr.unh.edu \
--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).