From owner-freebsd-questions Mon Feb 6 15:14:08 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA24199 for questions-outgoing; Mon, 6 Feb 1995 15:14:08 -0800 Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA24193 for ; Mon, 6 Feb 1995 15:14:06 -0800 Received: by plains.NoDak.edu; Mon, 6 Feb 1995 17:13:18 -0600 Date: Mon, 6 Feb 1995 17:13:18 -0600 From: Mark Tinguely Message-Id: <199502062313.AA06911@plains.NoDak.edu> To: aerygis@aluf.technion.ac.il, freebsd-questions@FreeBSD.org Subject: Re: rdump error Sender: questions-owner@FreeBSD.org Precedence: bulk > Trying to do a dump onn the remote server with a command > > rdump -0uf korney:/dev/nrmt0h / > check the PATH you are using in the account on the korney. adding /usr/sbin to the PATH should help. if you are using another OS on korney soft link /usr/bin/rmt to wherever it located on your machine. if you are using a non-privledge account on korney to do the dump then softlink ~/rmt to the system remtape. A word of warning to those going from FreeBSd 1.1.x to FreeBSD 2.0 using DAT tapes, my FreeBSD 2.0 won't read my old dump tapes. . I fact it still won't read a dump tape made with FreeBSD 2.0 from FreeBSD 2.0 unless I specify a block size: dump 0usbf 99999 4 /dev/nrst0 /dev/rsd0a yep, can't even dd it off, and neither Linux. I guess (and I will certainly get corrected if I am wrong), is has to do with fixed versus non-fixed record sizes. I just wanted to warn anyone making FreeBSD 1.x dumps on DAT (and prob 8mm) and expect to someday upgrade, add a block size to your dump script or for those dumping with FreeBSD 2.0 check today to see if you can restore the files and if not add ... --mark.