Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!apple!altos!altos86!ti
From: ti@altos86.Altos.COM (Ti Kan)
Newsgroups: comp.unix.sysv386
Subject: Re: tar under Interactive unix
Message-ID: <4217@altos86.Altos.COM>
Date: 11 Oct 90 17:01:30 GMT
References: <3494@skye.ed.ac.uk> <1990Oct09.114759.1025@virtech.uucp>
Reply-To: ti@altos86.UUCP (Ti Kan)
Organization: Altos Computer Systems, San Jose, CA
Lines: 33

In article <1990Oct09.114759.1025@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
>In article <3494@skye.ed.ac.uk> richard@aiai.UUCP (Richard Tobin) writes:
>>Can it really be that under Interactive "tar cv" writes the names of the
>>files to standard output, so that "tar cvf -" produces a corrupted file?
>
>Yes. (so you have to use tar cf - or tar cvf file to get a good tar file).
>
>>Is this standard System V brain damage?
>
>I believe it is. (Interactive would not be so stupid as to add this 
>blunder to the code).
>

tar cv and xv should output the file listing to stderr, not stdout.
AT&T's Sys V.3 source code is correct, but many 386 UNIX vendors did
not use AT&T's tar sources.  Rather, they used the Microsoft tar source
which came from Xenix.  The Microsoft tar has the wrong behavior of
writing the file listing to stdout.

For the record, all current Altos UNIX (not Xenix) releases for all its
systems has the correct tar behavior.  Although our tar sources are
derived from Microsoft's base, we have corrected the problem.

On a side note, the V.4 tar source from AT&T appears to be a modified
version of Microsoft's tar, not AT&T V.3's.  Thus, the aforementioned
bug is re-introduced into AT&T's own sources!  Ugh.

-Ti
-- 
Ti Kan | vorsprung durch technik!                                       \\\
Internet: ti@altos.com                                                   \\\
UUCP: ...!{sun|sco|pyramid|amdahl|uunet}!altos!ti                     /// \\\
The opinions herein are not necessarily those of Altos.              ////////\