From owner-freebsd-bugs Wed Oct 23 02:48:16 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08909 for bugs-outgoing; Wed, 23 Oct 1996 02:48:16 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA08902; Wed, 23 Oct 1996 02:48:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id TAA29780; Wed, 23 Oct 1996 19:40:14 +1000 Date: Wed, 23 Oct 1996 19:40:14 +1000 From: Bruce Evans Message-Id: <199610230940.TAA29780@godzilla.zeta.org.au> To: darrylo@sr.hp.com, freebsd-bugs@freefall.freebsd.org, scrappy@freefall.freebsd.org Subject: Re: bin/1547 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Synopsis: ncrcontrol won't work with FAILSAFE kernel > >State-Changed-From-To: feedback-closed >State-Changed-By: scrappy >State-Changed-When: Tue Oct 22 22:47:11 PDT 1996 >State-Changed-Why: > >Originator Confirmed Closure It's obviously still broken. A struct depends on MAX_TARGET which depends on SCSI_NCR_DFLT_TAGS which depends on FAILSAFE. I tested this. It is broken :-). I have to use the equivalent of FAILSAFE here for a Toshiba MK547FB boot drive, but I didn't notice the problem because I changed the source to define SCSI_NCR_DEFLT_TAGS as 0 before FAILSAFE existed, and have never used FAILSAFE. Bruce