Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.sysv386
Subject: Re: tar under Interactive unix
Message-ID: <1990Oct12.115213.15482@virtech.uucp>
Date: 12 Oct 90 11:52:13 GMT
References: <3494@skye.ed.ac.uk> <1990Oct09.114759.1025@virtech.uucp> <4217@altos86.Altos.COM>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 24

In article <4217@altos86.Altos.COM> ti@altos86.UUCP (Ti Kan) writes:
>
>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.

Being one to nitpick, AT&T's System V.3.x (where x < 2) probably had 
the correctly behaving tar.  However, with the introductin of 3.2 AT&T's
source had the bug.

>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.

That's because they brought forward the 3.2 sources to the 4.0 baseline
(at least for some parts of the system).


-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170