From owner-freebsd-hackers Mon Jun 26 04:53:42 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09572 for hackers-outgoing; Mon, 26 Jun 1995 04:53:42 -0700 Received: from lambda (lambda.demon.co.uk [158.152.17.124]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA09566 for ; Mon, 26 Jun 1995 04:53:37 -0700 Received: (from paul@localhost) by lambda (8.6.11/8.6.9) id MAA00268 for hackers@freebsd.org; Mon, 26 Jun 1995 12:52:58 +0100 From: Paul Richards Message-Id: <199506261152.MAA00268@lambda> Subject: scsi reprobing To: hackers@freebsd.org Date: Mon, 26 Jun 1995 12:51:42 +0100 (BST) Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1171 Sender: hackers-owner@freebsd.org Precedence: bulk The scsi(8) manpage says: The -p option can be used against the "super scsi" device /dev/scsi/super to probe all devices with a given SCSI lun on a given SCSI bus. The bus can be selected with the -b option and the default is 0. The lun can be selected with the -l option and the default is 0. See scsi(4) for a de- scription of the "super scsi" device. The -r option can be used in FreeBSD 1.1 to reprobe a specific SCSI de- vice at a given Bus, Target and Lun. This is not needed in FreeBSD 2.1, since opening a fixed SCSI device has the side effect of reprobing it, and probing with the bus with the -p option should bring on line any new- ly found devices. See scsi(4) for a description of fixed scsi devices. Does any of this actually work? Opening a device that wasn't on when the system booted results in "device not configured messages". The super scsi device doesn't exist and isn't reference in the scsi(4) manpage. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)