From owner-freebsd-hackers Thu Nov 28 23:53:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04854 for hackers-outgoing; Thu, 28 Nov 1996 23:53:05 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA04844 for ; Thu, 28 Nov 1996 23:52:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA28701 for ; Fri, 29 Nov 1996 08:52:45 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA03013 for freebsd-hackers@freebsd.org; Fri, 29 Nov 1996 08:52:45 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id IAA29645 for freebsd-hackers@freebsd.org; Fri, 29 Nov 1996 08:47:15 +0100 (MET) From: J Wunsch Message-Id: <199611290747.IAA29645@uriah.heep.sax.de> Subject: Re: eject for JAZ drives To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 29 Nov 1996 08:47:15 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611290054.LAA18652@genesis.atrad.adelaide.edu.au> from Michael Smith at "Nov 29, 96 11:24:30 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Smith wrote: > > scsi -f /dev/rsd1.ctl -c "1b 0 0 0 2 0" > > Unless there's a significant difference between the rsd1.ctl and rsd1c > device for scsi(8)'s purposes, this doesn't work. That's surprising. It's the same that all MO drives or CD drives are using. So somebody has to get their documentation then. > Some interesting observations based on my testing this morning : > > - setting the 'immediate' bit in the above command crashes the 'ncr' > driver ("1b 1 0 0 2 0"); I get timeouts and system death. Expected, i'd say. > - sending a short command causes the system to eventually grind to a > halt ("1b 0 0 0 2") (was under X so I didn't see any console messages). Also not unexpected. Basically, it kills that SCSI bus for quite some time. Of course, it only grinds your system to a halt if the system relies on that SCSI bus. :-/ Both are good reasons why the direct SCSI commands are only allowed for the superuser. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)