From owner-freebsd-hackers Mon Feb 22 11: 5:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.mail.uk.psi.net (relay2.mail.uk.psi.net [154.32.107.6]) by hub.freebsd.org (Postfix) with ESMTP id 6233711DC0 for ; Mon, 22 Feb 1999 11:04:43 -0800 (PST) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay2.mail.uk.psi.net with smtp (Exim 2.02 #3) id 10F0en-0004sY-00 for freebsd-hackers@freebsd.org; Mon, 22 Feb 1999 19:04:42 +0000 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) id 80256720.00688A1A ; Mon, 22 Feb 1999 19:01:50 +0000 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: freebsd-hackers@freebsd.org Message-ID: <80256720.006889BA.00@mail.plasmon.co.uk> Date: Mon, 22 Feb 1999 19:01:49 +0000 Subject: CAM open errors Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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