Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.mathworks.com!satisfied.elf.com!usenet.elf.com!lowell
From: lowell@epilogue.com (Lowell Gilbert)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: tar to remote devices
Date: 17 Feb 95 17:54:32
Organization: Epilogue Technology Corporation, Wakefield MA
Lines: 32
Message-ID: <LOWELL.95Feb17175432@quern.epilogue.com>
References: <WCP.95Feb13154951@lpds.lpds.com> <LOWELL.95Feb14103625@quern.epilogue.com>
<3hshav$ao9@alvman.RoBIN.de>
NNTP-Posting-Host: quern.epilogue.com
In-reply-to: ah@alvman.robin.de's message of 15 Feb 1995 09:25:51 GMT
Originally, wcp@lpds.sublink.org (Walter C. Pelissero) wrote:
> On my FreeBSD 2.0 I'm trying to make remote backup with tar but
> without success.
In article <3hshav$ao9@alvman.RoBIN.de> ah@alvman.robin.de (Andreas Haakh) writes:
: When I first used tar to do remote backups I encountered a similar
: problem which was solved when I created the following symbolic link
:
: /etc/rmt -> /usr/sbin/rmt
:
: Hope this solves the problem...
Thanks, but I think you're talking about a different problem. That
link belongs on the machine that has the tape drive, not the one
you're doing the 'tar' from. My problem (and possibly Mr. Pelissero's
as well, but mine for sure) is definitely with the machine on which
'tar' is being executed, and is definitely with the 'tar' executable
itself.
If you recall my original description of the situation, a different
tar executable (the one from the previous version of FreeBSD) works
fine. This is confusing because the sources for tar seem to have the
same version number as the older ones.
Thanks anyway, but I'm afraid that's a solution to a completely
different problem, which had been solved here long ago.
Be well.
Lowell
--
Lowell Gilbert lowell@epilogue.com