chris@mimsy.UUCP (10/03/87)
In article <4764@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes: >... I've had problems with some systems reading from a zcat | tar xf - >pipeline, which goes away if I uncompress the input file and say tar >xf filename. I infer that the "blocksize" on a pipe is widely variable, >at least with zcat on the other end, .... The block size does indeed depend on the program behind the pipe. If you have a 4.2BSD-based tar, `zcat | tar xBf -' solves the problem; 4.3BSD's tar automatically asserts `B'lock-buffer with `f'ile `-'. On other systems, `zcat | cat | tar xf -' may work. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris
gwyn@brl-smoke.UUCP (10/04/87)
In article <8896@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes: >On other systems, `zcat | cat | tar xf -' may work. The best way to reblock I/O in a pipeline is to use "dd", not "cat".