scott@bbxsda.UUCP (Scott Amspoker) (05/02/90)
In article <6420@star.cs.vu.nl> maart@cs.vu.nl (Maarten Litmaath) writes: >)uncompress -c $1.'tar' | tar xtopvwf - <- > ^^ ^^ > ^^ What's this? > ^^ > On SunOS 4.0.3c only one of `x' and `t' > is allowed; anyway `x' is intended here. > >It's a bug in tar: it sends the confirmation message to stdout (!) and >reads the user input from stdin (!)... :-( >In both cases tar should have opened /dev/tty. >Peter, it seems you're stuck with the temp file if you want to use the >`w' option. Also, I might add that on some systems the 'v' switch outputs to stdout. So a tar command such as tar cvf - somefiles would frequently create a corrupted tar file on stdout. This may not show up unless the output is large since the 'v' output appears to be buffered and could appear rather late in the output file. -- Scott Amspoker Basis International, Albuquerque, NM (505) 345-5232 unmvax.cs.unm.edu!bbx!bbxsda!scott
rowland@ecn.purdue.edu (Mav) (05/06/90)
In article <6420@star.cs.vu.nl> maart@cs.vu.nl (Maarten Litmaath) writes: >In article <23157@adm.BRL.MIL>, > jones@mips1.uqam.ca (Jones*Peter) writes: >)When I want to decompress a tar file, the following code works fine, albeit >)at the expense of creating a temp file on disk: [script deleted] >)The following was intended to do the same thing, but when I run it, I get >)checksum errors. I suspect the tar process is getting confused by the >)interactive confirmations requested by the -w switch. What should I do? Seems to me you could use the zcat program.. like: zcat xx.tar.Z |tar -xf[other flags here] - Works for me...suppose the w command might be different. I'm on BSD 4.3 Tahoe (actually Gould UTX 3/2) -- Mav F.U.N. X G.P.A. = CONSTANT Internet: rowland@en.ecn.purdue.edu UUCP: {gateway}!pur-ee!rowland