From: Sam Liddicott <sam@Liddicott.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: custom names for each slot in a multislot usb reader
Date: Thu, 17 Mar 2005 08:37:33 +0000 [thread overview]
Message-ID: <d1bfgt$q06$1@sea.gmane.org> (raw)
In-Reply-To: <d16ve5$clj$1@sea.gmane.org>
Kay Sievers wrote:
> On Tue, 2005-03-15 at 15:38 +0000, Samuel Liddicott wrote:
>>I can't work out what rules I need so that sdc becomes /dev/mmc and sdd
>>becomes /dev/smartmedia etc
>
> Try:
> udevinfo -a -p /block/sda
> udevinfo -a -p /block/sdb
> ...
>
> You will find keys here that are different for every slot, but
> independent of the kernel enumeration. I have one reader that already
> has names for the slot one other has numerical id's to match.
Thanks
Based on that advice, these rules work:
BUS="scsi" SYSFS{model}="Flash XL CF" SYSFS{vendor}="Medion*"
NAME{all_partitions}="media/compactflash"
BUS="scsi" SYSFS{model}="Flash XL MS" SYSFS{vendor}="Medion*"
NAME{all_partitions}="media/memorystick"
BUS="scsi" SYSFS{model}="Flash XL MMC/SD" SYSFS{vendor}="Medion*"
NAME{all_partitions}="media/securedigital"
BUS="scsi" SYSFS{model}="Flash XL SM" SYSFS{vendor}="Medion*"
NAME{all_partitions}="media/smartmedia"
Sam
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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:[~2005-03-17 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 15:38 custom names for each slot in a multislot usb reader Samuel Liddicott
2005-03-15 16:01 ` Kay Sievers
2005-03-17 8:37 ` Sam Liddicott [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='d1bfgt$q06$1@sea.gmane.org' \
--to=sam@liddicott.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 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.