From owner-freebsd-current Wed Mar 22 02:07:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA29413 for current-outgoing; Wed, 22 Mar 1995 02:07:49 -0800 Received: from sbstark.cs.sunysb.edu (sbstark.cs.sunysb.edu [130.245.1.47]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA29407 for ; Wed, 22 Mar 1995 02:07:48 -0800 Received: from starkhome.UUCP (root@localhost) by sbstark.cs.sunysb.edu (8.6.9/8.6.9) with UUCP id FAA13583 for current@freebsd.org; Wed, 22 Mar 1995 05:07:42 -0500 Received: by starkhome.cs.sunysb.edu (8.6.11/1.34) id FAA11442; Wed, 22 Mar 1995 05:06:57 -0500 Date: Wed, 22 Mar 1995 05:06:57 -0500 From: starkhome!gene@sbstark.cs.sunysb.edu (Gene Stark) Message-Id: <199503221006.FAA11442@starkhome.cs.sunysb.edu> To: "Rodney W. Grimes" Cc: current@FreeBSD.org In-reply-to: "Rodney W. Grimes"'s message of Tue, 21 Mar 1995 22:55:19 -0800 (PST) Subject: ANy one useing ft driver under 2.0 current??? Sender: current-owner@FreeBSD.org Precedence: bulk >I am trying to get a colorado 250 working. It probes and every thing >but ``tar czf - | ft "test1" runs for awhile and then finishes without >error. I use the ft driver regularly with -current for backups and restores. It works fine for this. I am not surprised about the crash problem in accessing the ft device with dd. I have seen this type of thing myself and I might even have reported the bug at one point. I only use the drive with the ft command at the moment. As was already pointed out, you forgot the directory to tar in the above command. - Gene