Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!ico!dougm
From: dougm@ico.isc.com (Doug McCallum)
Newsgroups: comp.unix.sysv386
Subject: Re: tar under Interactive unix
Message-ID: <1990Oct11.002436.7393@ico.isc.com>
Date: 11 Oct 90 00:24:36 GMT
References: <3494@skye.ed.ac.uk> <1990Oct9.002629.16247@wolves.uucp> <4173@auspex.auspex.com>
Reply-To: dougm@ico.ISC.COM (Doug McCallum)
Organization: Interactive Systems Corp., Boulder CO
Lines: 13

In article <4173@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
...
>The 3B2 S5R3 "tar" source indicates that the only places where the "v"
>flag causes "tar" to print something to the standard output, rather than
>the standard error, is when used with the "t" flag (as you'd expect, the
>table of contents goes to the standard output) or when used with the "w"
>flag (the query for user confirmation is sent to the standard output).

The 386 S5R3.2 "tar" source has "printf" everywhere rather than any
fprintf(stderr,...) calls.  This appears to have been the way it came
back to AT&T (and ISC) from Microsoft during the XENIX merge.  The
version of tar that was shipped with S5R3.0 did it correctly (that is, the 
same as the 3B2 source does it).