Date: Mon, 22 Feb 1999 19:01:49 +0000 From: amobbs@allstor-sw.co.uk To: freebsd-hackers@freebsd.org Subject: CAM open errors Message-ID: <80256720.006889BA.00@mail.plasmon.co.uk>
next in thread | raw e-mail | index | archive | help
Is there a reson (such as meeting spec.) that cam_open_btl et. al. don't
return an error code, but just stick a string in cam_errbuf?
I'm using an application which uses the CAM passthrough drivers, and
basically tries to grab everything on a given bus, and I'd like to be able
to distinguish a genuine failure from simply one caused by the device not
being there.
I've looked at camcontrol.c, and it doesn't deal with this, it simply
prints the cam_errbuf and exits.
I could always just hack camlib to do what I want, but if there's a better,
or more standard solution I'd prefer that.
Andrew.
--
Andrew Mobbs - Software Engineer
- Allstor Software Ltd.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80256720.006889BA.00>