On Wed, 5 Aug 2009, Kay Sievers wrote:
Here's the /dev/disk/by-path with the flash disk inserted
pci-0000:00:14.2-usb-0:4:1.0-scsi-0:0:0:0 -> ../../pny
pci-0000:00:14.2-usb-0:4:1.0-scsi-0:0:0:0-part1 -> ../../pny1
pci-0000:00:14.2-usb-0:4:1.0-scsi-0:0:0:0-part4 -> ../../pny4
Do not rename any kernel device name, just add symlinks if needed.
Random stuff breaks if you do that.
OK didn't know that.
what should I be looking for in the output of udevinfo?
Nothing, just use the plain links which are already
created. The needed logic is _not_ contained in udevinfo
or the kernel name.
I'm not sure how this relates to my problem.
In case you haven't got my problem, I have 15 ports on USB
hubs. The user has a flash drive that the computer has never
seen (and may not see again), which he can insert now, or
someone may have prefilled the slots with flash drives
earlier. He tells the program which slot holds the flash
disk, which file(s) he wants and tells the computer to write
them. At the end the program tells the user to remove the
flash drive and the computer has to detect that the slot has
become empty. All the other slots can be writing or holding
flash drives at the same time.
To setup I can put flash drives into each slot to find the
association between a slot and the computer's descriptors,
but I don't know how to fine the association. How do I use
the plain links which are created on insertion to know which
slot a flash drive is sitting in?
Thanks Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
