*BSD News Article 42464


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
Followup-To: comp.os.386bsd.bugs
Date: 14 Feb 95 10:36:25
Organization: Epilogue Technology Corporation, Wakefield MA
Lines: 32
Message-ID: <LOWELL.95Feb14103625@quern.epilogue.com>
References: <WCP.95Feb13154951@lpds.lpds.com>
NNTP-Posting-Host: quern.epilogue.com
Summary: grab an executable from 1.1.5.1
In-reply-to: wcp@lpds.sublink.org's message of 13 Feb 1995 15:43:30 -0600

In article <WCP.95Feb13154951@lpds.lpds.com> 
wcp@lpds.sublink.org (Walter C. Pelissero) writes:
   On my FreeBSD 2.0 I'm trying to make remote backup with tar but
   without success. It seems that the child rsh dumps a core but I can't
   say it for sure. Dump, instead, works fine but I would like to make
   compressed backups and dump doesn't support them.

   Any idea?

Several.  I hit this also, and although I don't have an answer, I
apparently did a bit more investigation.  

Rsh is not at fault; I replaced rsh with a shell script that dumped
the call to rsh (including parameters) to a log file.  Using this, I
showed that rsh was never getting called.  I recompiled tar, since its
sources didn't seem to have changed since the one released with
FreeBSD 1.1.5.1, but that failed with the same symptoms.  An
executable copied directly from one of my coworkers' 1.1.5.1 machines
works flawlessly.  So my immediate problem (backing up the machine) is
solved, but I'd still like to be able to compile things myself.

Incidentally, I tried to report this as a bug, but I'm not sure I've
fully figured out send-pr yet.  The documentation referred me to the
installation package for send-pr, which I didn't have since it came
already built into the FreeBSD distribution.  Once I figure out how to
submit bug reports correctly, maybe I'll submit one on that... :-)

Be well.
        Lowell
--
Lowell Gilbert		lowell@epilogue.com