Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
X-Posting-Agent:	Hamster/1.3.22.0
Message-ID:	<00ea01c0b6d7$91442500$419c953e@aldebaran>
From:	<noog AT libero DOT it>
To:	<cygwin AT sources DOT redhat DOT com>
Subject:	tar hates stdout? possible bug
Date:	Tue, 27 Mar 2001 17:54:20 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	27 Mar 2001 16:22:57.0024 (UTC) FILETIME=[2EC63000:01C0B6DA]

For some strange reason, tar has lost its ability to write correctly to stdout.
Consider the two following commands:

tar -cv folder>filename.tar
tar -cvf filename.tar folder

they should generate the same archive. They don't. The archive generated in the
first way is slightly larger (a matter of a hundred byte), and invalid right
after the second file, so only one file is listed. Oddly enough, this happens
only when recursign through directories, only when a directory and not a series
of file names is specified, and it affects only tar.

An interesting, "on the fly" test follows:

D:\home\Hyperion>tar -cv Desktop|tar -t
Desktop/
Desktop/AUTOEXEC.BAT
Desktop/CapOrderForWeb.PDF
Desktop/console.png
Desktop/
Desktop/AUTOEXEC.BAT
tar: Skipping to next header
Desktop/DCONFIG.SYS
Desktop/desk.png
Desktop/Desktop.rar
tar: 343 garbage bytes ignored at end of archive
tar: 288 garbage bytes ignored at end of archive
tar: Error exit delayed from previous errors

D:\home\Hyperion>

this from inside the standard Windows NT command shell. They confirmed me it's
not the typical "lf-to-crlf", and I experimented that the bug is specific to
tar. However writing directly to disk works

from inside bash, it works since when I mounted / as binary


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -