From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: custom names for each slot in a multislot usb reader
Date: Tue, 15 Mar 2005 16:01:14 +0000 [thread overview]
Message-ID: <1110902474.6630.89.camel@localhost.localdomain> (raw)
In-Reply-To: <d16ve5$clj$1@sea.gmane.org>
On Tue, 2005-03-15 at 15:38 +0000, Samuel Liddicott wrote:
> I have a multislot usb reader that gets assigned sda,sdb,sdc,sdd as the
> main block devices.
>
> I can't work out what rules I need so that sdc becomes /dev/mmc and sdd
> becomes /dev/smartmedia etc
>
> Now I can do rules to match the device and /dev/hda - but this will only
> work if my other usb thumbrive isn't handled first.
>
> So I really need a rule to match on LUN.
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.
Kay
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-15 16:01 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 [this message]
2005-03-17 8:37 ` Sam Liddicott
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=1110902474.6630.89.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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.