From owner-freebsd-hackers Tue Mar 21 06:39:15 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA21338 for hackers-outgoing; Tue, 21 Mar 1995 06:39:15 -0800 Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA21331; Tue, 21 Mar 1995 06:39:14 -0800 X-Authentication-Warning: freefall.cdrom.com: Host LOCALHOST didn't use HELO protocol To: julian@tfs.com (Julian Elischer) cc: phk@ref.tfs.com (Poul-Henning Kamp), fbsd@clem.systemsix.com, hackers@FreeBSD.org, moto@CS.cmu.edu, tinguely@plains.nodak.edu Subject: Re: Problems with 2940 and 950210snap In-reply-to: Your message of "Mon, 20 Mar 95 23:39:28 PST." Date: Tue, 21 Mar 1995 06:39:14 -0800 Message-ID: <21330.795796754@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > if we distributed the 'st' utility like we should, > you could run > > st -f /dev/nrst0 status > > and we could see the mode the device was operating in. > that would tell us a lot about the possible causes.. > then you can use the scsi(1) or is that scsi(8) command > to turn on debugging on the tape > and see what it's being asked to do..... > scsi(8) is in current, > I include st(1) here so you can try it out > it should be in the source tree (next to mt(1)) but appears to be missing.. I was under the impression that we were going to merge st and mt together, and that this was the reason for not bringing st over in the first place. Two tape frobbing commands does strike me as more than a little silly, and `mt' is the historical standard. Jordan