From owner-freebsd-scsi Sat Mar 14 21:49:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16915 for freebsd-scsi-outgoing; Sat, 14 Mar 1998 21:49:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16910 for ; Sat, 14 Mar 1998 21:49:34 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA04774; Sat, 14 Mar 1998 22:46:23 -0700 (MST) Date: Sat, 14 Mar 1998 22:46:23 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803150546.WAA04774@narnia.plutotech.com> To: Karl Denninger cc: scsi@FreeBSD.ORG Subject: Re: CAM question Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980314122132.45239@mcs.net> <199803141930.MAA03892@narnia.plutotech.com> <19980314164119.15655@mcs.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The big problem with things like systat is that it completely breaks them > (not just returning no data, but causing them to blow up entirely). Seems to work just fine on my CAM systems (other than not returning and disk data and telling you nicely that "-iostat" makes little sense for a system that reports having no drives). I don't believe that we've changed anything in the systat code for CAM (yet) and if systat blows up when there are no drives in the system (dkndrive is 0), then systat was broken long before CAM came around (think diskless configurations). For the short term, I'm more concerned with implementing full SCSI controller and device support than fixing things like systat, so if you feel that "not having systat" is too much of a restriction to using CAM, you're more than welcome not to use the patches. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message