From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Question about tar v1.28
Date: Fri, 09 Dec 2016 03:04:00 -0000 [thread overview]
Message-ID: <f3ffc9a1-deae-6ab3-8250-16621667a08e@redhat.com> (raw)
In-Reply-To: <56DF65A1.6060305@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]
[reviving an old thread]
On 03/08/2016 05:52 PM, Eric Blake wrote:
> 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 directory
> somewhere 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).
In fact, I missed LOTS of spots. My cygwin-specific patches to 1.27
were accidentally not copied to 1.28. I'm fixing it as part of
packaging 1.29, which should hit mirrors soon.
I'm actually a bit surprised that there were so few reports of this
problem in the meantime (I built 1.28 in May 2015, this report was in
March 2016, and I didn't find much else about it in the meantime).
Maybe that means that text mounts are used much less than they used to
be when I took over building tar in 2005, back when setup.exe used to
have a now-removed option to create text mounts at install time.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2016-12-09 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1104577559.5773489.1457451810513.JavaMail.yahoo.ref@mail.yahoo.com>
2016-03-08 15:43 ` Douglas Coup
2016-03-08 23:52 ` Eric Blake
[not found] ` <56E05762.8050708@obj-sys.com>
2016-03-09 18:33 ` Douglas Coup
2016-03-09 22:05 ` Andrey Repin
2016-03-12 15:36 ` Bryan Berns
2016-12-09 3:04 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3ffc9a1-deae-6ab3-8250-16621667a08e@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).