From: Anssi Saari <as@sci.fi>
To: linux-hotplug@vger.kernel.org
Subject: NAME{all_partitions}, how does it work?
Date: Sat, 28 Feb 2004 19:44:05 +0000 [thread overview]
Message-ID: <20040228194404.GA26312@sci.fi> (raw)
I have a multiple memory card reader thing for USB with four slots. I'm
using this currently in udev.rules:
# Iwill 6-in-1 memory card reader
BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="CF/MD ", NAME="cf%n"
BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="SM ", NAME="sm%n"
BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="SD/MMC ", NAME="sd_mmc%n"
BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="MS ", NAME="ms%n"
And it works, except that if there are no cards when I plug the reader
in, no devices for partitions are created and apparently plugging in a
memory card in the reader is not a hotplug event.
The manpage says to use NAME{all_partitions} to get all 15 partitions
of a block device created, so I tried
BUS="scsi", SYSFS_vendor="6-in-1 ", SYSFS_model="CF/MD ", NAME="cf%n{all_partitions}"
and various other things, but all I was able to get was
a) no device created
b) /udev/cf{all_partitions} was created
c) /udev/cf was created
So how is this really supposed to be used? Is it even a thing that could
help me?
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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 reply other threads:[~2004-02-28 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 19:44 Anssi Saari [this message]
2004-02-28 20:19 ` NAME{all_partitions}, how does it work? Kay Sievers
2004-02-29 6:02 ` Anssi Saari
2004-02-29 13:39 ` Kay Sievers
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=20040228194404.GA26312@sci.fi \
--to=as@sci.fi \
--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.