>>>>> On Fri, 10 Jul 1998 11:04:49 +0100 (BST), Ian Grant <I.A.N.Grant@damtp.cam.ac.uk> said:
Ian> I'm wondering now how I tell SANE where to find the scanner. My
Ian> system has a /dev/cam device, and I see from sanei_scsi.c that
Ian> for SCSI/CAM sanei_scsi_open expects a device string of the
Ian> form "bNtNlN" where the N's are bus, target and lun, and opens
Ian> /dev/cam. The trouble is that I can't see where I have to
Ian> specify the bus/target/lun string. For example the sane-hp man
Ian> page says:
Ian> "This backend expects device names of the form:
Ian> special
Ian> Where special is the UNIX path-name for the special
Ian> device that corresponds to the scanner.
Ian> Is this just a bug in the man page, and should I be putting
Ian> b0t2l0 or whatever in the hp.conf file?
Yes, you're supposed to put b0t2l0 in hp.conf.
Ian> Also, can anyone tell me how buggy the user-level scsi
Ian> interface is? I.e does it trash disks? What sort of bugs
Ian> should I expect?
As I mentioned earlier, expect it to be buggy. I wrote that code
based on some DUX docs and I'm pretty sure some things are not quite
right. It has the potential to trash the disks.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com