James Bottomley <James.Bottomley@xxxxxxx> writes: > The way it's supposed to work is that you listen for the uevent that > signals the sd binding is complete, so you actually get notice > asynchronously. The event carries device information with it. udev > uses the node information to send VPD inquiries, which is how it does > the by-id and by-uuid mappings. Quite hard to sit down and actually write a shell script to do this, though! It feels like the operation of logging into an iscsi target, waiting for the device node and then returning it is something you'd reasonably expect to be able to do, but it's become quite tricky in this async world. Netlink isn't at all accessible to scripts, and udevadm doesn't provide a good front-end to do it either. When something like a USB device being plugged in, the operation is fundamentally asynchronous, but with an iscsi login, the device is appearing because you've run a login command, so it's not completely mad to hope to be get back the ultimate result of that command, even if you have to wait for it. Cheers, Chris. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
