From owner-freebsd-current  Mon Feb  3 17:08:02 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA04289
          for current-outgoing; Mon, 3 Feb 1997 17:08:02 -0800 (PST)
Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04273
          for <current@freebsd.org>; Mon, 3 Feb 1997 17:07:58 -0800 (PST)
Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id RAA23558 for <current@freebsd.org>; Mon, 3 Feb 1997 17:07:58 -0800 (PST)
Date: Mon, 3 Feb 1997 17:07:53 -0800 (PST)
From: Tom Bartol <bartol@salk.edu>
To: current@freebsd.org
Subject: SCSI_FREEZE kernel option?
Message-ID: <Pine.BSF.3.95.970203165443.13561C-100000@pauling.salk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Hi,

I was just looking at the manpage for scsi (8) and was particularly
intrigued by the -z option which claims to be able to freeze the scsi bus
for an audible "beep" delimited (with the -v option) specified period of
time provided you have compiled your kernel with the "SCSI_FREEZE" option.
The manpage goes on to state that this kernel code is not committed yet
and indeed a grep of the kernel source for -current for the string
"SCSI_FREEZE" comes up empty-handed.  I presume that an appropriately
contrived sequence of scsi -z and scsi -p commands could be used to
perform hot-swapping of scsi devices -- something I would dearly love to
be able to do.  Does this actually work yet and how should I specify any
required kernel options?

Thanks for your help,

Tom