From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83208 invoked by alias); 9 Mar 2016 22:05:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 83192 invoked by uid 89); 9 Mar 2016 22:05:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*r:sk:postmas, Text X-HELO: smtp.ht-systems.ru Received: from smtp.ht-systems.ru (HELO smtp.ht-systems.ru) (78.110.50.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 09 Mar 2016 22:05:13 +0000 Received: from [95.165.144.62] (helo=darkdragon.lan) by smtp.ht-systems.ru with esmtpa (Exim 4.80.1) (envelope-from ) (Authenticated sender: postmaster@rootdir.org) id 1admE8-0007qa-SL ; Thu, 10 Mar 2016 01:05:08 +0300 Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Wed, 09 Mar 2016 21:54:57 -0000 Date: Wed, 09 Mar 2016 22:05:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <546009875.20160310005457@yandex.ru> To: Douglas Coup , 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 X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00111.txt.bz2 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