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:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=lMChSb8W/xzn4lxv
	67waOBk2F290sqvsenWjhA3TJVvXLaQYlBsXFRkPB3ZTBn8L6TCvt0005zPuMWJS
	B6MPunxUaIz7RkcqCu0v881Ce2WHan58ibcWFLiJUeoZY6YDW4kvEWNxis2xjZRK
	6TQ3DDqi5L/NFpdof5zMpxCCKko=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 10 Mar 2016 00:54:57 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <546009875.20160310005457@yandex.ru>
To: Douglas Coup <dacoup2@yahoo.com>, cygwin@cygwin.com
Subject: Re: Question about tar v1.28
In-Reply-To: <160863024.6759470.1457548349068.JavaMail.yahoo@mail.yahoo.com>
References: <56DF65A1.6060305@redhat.com> <56E05762.8050708@obj-sys.com>   <160863024.6759470.1457548349068.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Douglas Coup!

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

Text mounting is VERY, VERY, VERY bad idea.
Never do that again.

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

The problem with text mounts is that you can never know, how a given program
would handle it. It may even not in the program's hands, as certain libraries
behind it may have their own second or even third opinion on the subject.
And when you tell the program to read N bytes, you never know, if it will stop
after reading N, or M, or N+M...


-- 
With best regards,
Andrey Repin
Thursday, March 10, 2016 00:51:33

Sorry for my terrible english...


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