From owner-freebsd-hackers Tue Feb 4 10:15:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA02268 for hackers-outgoing; Tue, 4 Feb 1997 10:15:33 -0800 (PST) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02260 for ; Tue, 4 Feb 1997 10:15:27 -0800 (PST) Received: from deputy.pavilion.co.uk (deputy.pavilion.co.uk [194.242.128.24]) by florence.pavilion.net (8.8.5/8.8.5) with ESMTP id SAA26193; Tue, 4 Feb 1997 18:14:48 GMT From: Josef Karthauser Received: (from jlk@localhost) by deputy.pavilion.co.uk (8.8.3/8.8.4) id SAA00858; Tue, 4 Feb 1997 18:14:48 GMT Message-Id: <199702041814.SAA00858@deputy.pavilion.co.uk> Subject: Re: probing scsi bus after boot? To: dufault@hda.com (Peter Dufault) Date: Tue, 4 Feb 1997 18:14:48 +0000 (GMT) Cc: jkh@time.cdrom.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.org, jlk@pavilion.co.uk In-Reply-To: <199611011028.FAA07666@hda.hda.com> from "Peter Dufault" at Nov 1, 96 05:28:54 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Sorry to bring up an old thread, but I've got a scsi tape drive that I need to use across many machines to back their file systems up. I can think of two ways to do it. Either I use rmt, but I've not found a way of rmt'ing as root on the remote site (please someone let me out of my misery.) The other way is to plug the tape drive into the machine that I'm backing up. I've compiled the super scsi driver into my 2.1.6 kernel (controller ssc), but I still get: # scsi -f /dev/rst0 -p scsi: unable to open device /dev/rst0: Device not configured I guess that I might have to do this on the /dev/scsi/super device, but /dev/MAKEDEV doesn't build it! Any hints would be greatly appreciated. Cheers, Joe. > > > Huh? I just do this on /dev/sd0 or some other - it works great! > > I use it to detect my scanner after power-up all the time. > > The super SCSI device is needed when nothing is on the bus at boot > - you then need a way into the system for that case. Try putting > your scanner on its own bus with no SCSI devices (I forgot - you > NEVER have a system with no SCSI devices). The super SCSI device > should support bus configuration (such as reprobe) and "device > target" types of calls ("become this SCSI NEXUS"). It is essentially > a SCSI bus device. > > I added it when I was doing some work with a prototype device on > a dedicated bus that was frequently not powered up. > > IMHO super SCSI should be left working this way, maybe renamed to > be a bus device. The SCSI user code should be ripped out with > extreme prejudice - it is superceded by the newer configuration > code. > > The code suffers from no use and no test. > > Peter > > -- > Peter Dufault Real-Time Machine Control and Simulation > HD Associates, Inc. Voice: 508 433 6936 > dufault@hda.com Fax: 508 433 5267 > -- Josef Karthauser (joe@pavilion.net) Technical Manager [Tel: +44 1273 607072 Fax: +44 1273 607073] Pavilion Internet plc. ._ .. _. _ ._.. .. .._. . __. ._. ._ _. _..