X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:message-id:in-reply-to
	:references:subject:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=Jgva9fZNPPFcy9Do
	yzN7nKRv0vR67T2RrEoUZPUH2D7svR0i/yCZeZVGJMR7TaYBwyTA/tnA2fBr6Yg+
	K2Kg2uKYk3iQlEKx7eMMPH/yihx7GPxXWp4S69JI9+VgCPCY7YsAvng+oFd8t/q4
	yaiBp+VwYSsc9jHK3tl7/Yh8OHo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:to:message-id:in-reply-to
	:references:subject:mime-version:content-type
	:content-transfer-encoding; s=default; bh=DO2SE0h/1QPUiAiaqE+Ed9
	HEYlU=; b=UbVIdQd4NsmqM90vN4TWsO8C/eXeWJObn32YNejcOEXCdZjmgCu81L
	sSd3VWoCydiF6iNtdJ3btzXW5HRjT2Ii2Mlq2ecY/PdBV4h2AVpXfxc/fCzW/WZG
	Io203qJdRIQSLCRcGSJ7WVp5Kwxu0ghD06sZLH5WZFLy0xxCnh51U=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.6 required=5.0 tests=BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,FREEMAIL_REPLYTO_END_DIGIT,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:2137, dacoup2 AT yahoo DOT com, dacoup2yahoocom, U*dacoup2
X-HELO:	nm23.bullet.mail.gq1.yahoo.com
Date:	Wed, 9 Mar 2016 18:32:29 +0000 (UTC)
From:	Douglas Coup <dacoup2 AT yahoo DOT com>
Reply-To:	Douglas Coup <dacoup2 AT yahoo DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Message-ID:	<160863024.6759470.1457548349068.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To:	<56E05762.8050708@obj-sys.com>
References:	<56DF65A1 DOT 6060305 AT redhat DOT com> <56E05762 DOT 8050708 AT obj-sys DOT com>
Subject:	Re: Question about tar v1.28
MIME-Version:	1.0

My apologies if some people see this twice.  I didn't see my original reply come through the mailing list.




________________________________
From: Douglas Coup <dcoup AT obj-sys DOT com>
To: dacoup2 AT yahoo DOT com 
Sent: Wednesday, March 9, 2016 12:03 PM
Subject: Fwd: Re: Question about tar v1.28







-------- Forwarded Message -------- 
Subject: Re: Question about tar v1.28 
Date: Tue, 8 Mar 2016 16:52:01 -0700 
From: Eric Blake <eblake AT redhat DOT com> 
To: cygwin AT cygwin DOT com 


On 03/08/2016 08:43 AM, Douglas Coup wrote:
> Hello Cygwin community. 
> 
> I'm observing some unusual behavior with tar v1.28, running as part of 

> 32-bit Cygwin on a Windows 10 machine. 


I noticed this in your cygcheck output: > cygdrive prefix /cygdrive system text,noacl,posix=0,auto

Why are you text-mounting it?  Is your current working directorysomewhere under that text mount?  It may be a bug in tar's handling of
text-mounted files (ideally, tar should be reopening everything binary

in spite of text mounts, but I may have missed a spot).

Text mounting is our standard here.  I will try to find out why.

I changed the /etc/fstab so it specifies "binary" instead of "text", and with that change, the problem doesn't occur.  However, the problem doesn't occur with "text" specified on two other systems that use tar v1.27, one running Windows 8.1 and the other running Windows 7.  In fact I had used the "tar" command previously on this Windows 10 system with "text" in place without problems.  I've done other Cygwin installs since then, so probably either the "tar" command itself got updated or something it depends on got updated, such that now this issue occurs. 
> A similar sequence on a Windows 8.1 machine running tar v1.27.1 does not 

> produce this problem. 


Could be an accidental regression in my cygwin-specific patches betweenthe two versions. But I don't normally use or test on text-mounts, so
I'll need confirmation that you are indeed experiencing the problem only

in your text mount, before I spend cycles debugging it. 


-- Eric Blake  eblake redhat com   +1-919-301-3266
Libvirt virtualization library http://libvirt.org 

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -