On Wed, Mar 25, 2009 at 03:03:21PM -0400, Bill Nottingham wrote: > Then where is a better place to put this, as scsi_wait_scan.ko is > a ridiculous interface for userspace? It would be nice if people would comment on "ridiculous interface"s when they're asked for feedback, instead of waiting more than two years. I think you're misunderstanding how to use scsi_wait_scan. The idea was that the bit of userspace that probes all the device drivers would do: modprobe fusion.ko modprobe aic79xx.ko modprobe sym53c8xx.ko modprobe scsi_wait_scan rmmod scsi_wait_scan et voila, you're done. It seems like you want random other bits of userspace to wait for scsi scanning to be done, and that wasn't the original intent. I suppose we could add Yet Another Damn Sysfs File, say /sys/bus/scsi/wait_scan -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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
