DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Hi
	ejrI6duysiOFM84cGEbbuyFtsifOscYLKL41UAmBkMlODUxX6zwPgcDeqYtuvLwk
	kd5Wt9ZBdblkfVsUrm2u0hKiRqDpHXDPjsIFI14RjIp7KPY+cHKE+Mp+uQOXUT8F
	CB/Dx+lNeZzCd4Nwf+a72xwFo8EAbhGvqo+ITv3t4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
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>
Date: Sat, 12 Mar 2016 10:36:15 -0500
Message-ID: <CADi7v6+xThyXXyLrUuQ4GXkSS7==W3m85cN2zZfOFLGLrG4kTg@mail.gmail.com>
Subject: Re: Question about tar v1.28
From: Bryan Berns <bryan.berns@gmail.com>
To: Douglas Coup <dacoup2@yahoo.com>, cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

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

For what it's worth, I recently had the similar issues with Cygwin tar
on text-mounted volumes in the last year.  We had users moving between
Cygwin tar and Redhat tar and there were issues extracting the tar
files.  I instructed them to create a binary mount for tar-related
purposes and that addressed the issue.  We need to use text-mounts, in
general, for other reasons.  It would be great if tar could be
adjusted to operate properly in these scenarios.

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