From owner-freebsd-scsi Fri Jun 22 14:10:34 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 4178C37B401 for ; Fri, 22 Jun 2001 14:10:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f5ML7rg75210; Fri, 22 Jun 2001 14:07:54 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 22 Jun 2001 14:07:47 -0700 (PDT) From: Matthew Jacob Reply-To: To: "Kenneth D. Merry" Cc: j mckitrick , Subject: Re: how to invalidate scsi connection to driver module In-Reply-To: <20010622150607.A57782@panzer.kdm.org> Message-ID: <20010622140658.P20923-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > That seems to work well... note it removes all periphs that referred to that > > device. > > Yep. I decided to do things more riskily, and the AC_FOUND_DEVICE even works w/o tremendous confusion during probe time- this means that while we're booting and probing, the wad of device arrivals get sorted out as well. Not bad. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message