Xref: utzoo comp.misc:8930 comp.unix.wizards:21895
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!samsung!usc!apple!oliveb!orc!inews!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.misc,comp.unix.wizards
Subject: Re: Your favourite UNIX pipe ?
Keywords: pipe
Message-ID: <1990May9.172931.11033@iwarp.intel.com>
Date: 9 May 90 17:29:31 GMT
References: <690@coma.UUCP>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Followup-To: comp.misc
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 30
In-Reply-To: andy@coma.UUCP (Andreas Lampen)

In article <690@coma.UUCP>, andy@coma (Andreas Lampen) writes:
|   tar cf - | dd bs=20k | rsh coma "cd blubber; dd bs=20k | tar xf -"

I would use:
	tar cf - . | dd obs=20k | rsh coma "cd blubber && tar xf -"

The second dd contributes nothing.

The "&&" prevents you from extracting a whole mess of stuff in the
wrong directory should you "fat-finger" the target directory.

(Leaving the '.' off the tar sends an empty archive... you gotta send
at least *something*. :-)

I also usually leave off the first dd, because tar writes its stuff
20*512 bytes at a time anyway.

If I'm nosy, it comes out as:

	tar cf - . | rsh coma "cd blubber && tar xvf -"

so I can get a progress report.  Run it in a separate window (GNU
Emacs or bitmap window, take yer pick).

Just another tar baby,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/