From: Dave Hansen <haveblue@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: getting udev to work with USB combo drive
Date: Sun, 08 Feb 2004 03:22:04 +0000 [thread overview]
Message-ID: <1076210508.1262.1332.camel@nighthawk> (raw)
I have a pretty stupid USB combo device that doesn't like to report very
detailed information about itself (For Google's sake, the drive is a
Vosonic X's Drive Pro VP-300):
SYSFS_vendor="USB "
SYSFS_model="USB "
SYSFS_rev="1.00"
Despite that, SYSFS_serial looked good, so I decided to use it for
udev. The device has an internal hard disk, and 3 media slots, so I
laid out 3 entries like this:
SYSFS_serial="0123", ID="*:0", NAME="xdrive/disk%n"
SYSFS_serial="0123", ID="*:1", NAME="xdrive/cf%n"
SYSFS_serial="0123", ID="*:2", NAME="xdrive/sm%n"
SYSFS_serial="0123", ID="*:3", NAME="xdrive/xd%n"
But, these rules never matched. The wildcard in the ID= field appears
to be ignored. Is that a bug?
I worked around it with a script of my own and a single udev.rules
entry:
BUS="usb", SYSFS_serial="0123", PROGRAM="/path/xdrive.sh %b", RESULT="*", NAME="xdrive/%c%n"
#!/bin/sh
ID=$1
# strip out everything before the last :
SLOT_NUM=${ID/*:/}
case $SLOT_NUM in
0) NAME=disk ;;
1) NAME=compactflash ;;
2) NAME=smartmedia ;;
3) NAME=xd ;;
esac
echo -n $NAME
--dave
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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 reply other threads:[~2004-02-08 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 3:22 Dave Hansen [this message]
2004-02-12 1:38 ` getting udev to work with USB combo drive Greg KH
2004-02-12 5:45 ` Dave Hansen
2004-02-12 17:45 ` Greg KH
2004-02-12 18:04 ` Dave Hansen
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=1076210508.1262.1332.camel@nighthawk \
--to=haveblue@us.ibm.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).