From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anssi Saari Date: Sat, 28 Feb 2004 19:44:05 +0000 Subject: NAME{all_partitions}, how does it work? Message-Id: <20040228194404.GA26312@sci.fi> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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_id56&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