From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82275 invoked by alias); 12 Mar 2016 15:36:21 -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 82255 invoked by uid 89); 12 Mar 2016 15:36:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=volumes, instructed, H*Ad:D*yahoo.com X-HELO: mail-lb0-f178.google.com Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Sat, 12 Mar 2016 15:36:19 +0000 Received: by mail-lb0-f178.google.com with SMTP id x1so190699168lbj.3 for ; Sat, 12 Mar 2016 07:36:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=A9UQ3KgP/ucyD4TgnjG9yZGKgQRta+pmVcS0yyjrvOQ=; b=WOQJUZZFDEpOvGg8bwh8+ey/A8ctaBCgTGGSsmLPJIM24TeKQbWbsligKDN4aO5ExV Qso0uUvjIqUXoY8EC4+iCUhyJL4/2utrw4sU6uDCE5TLK6AZSA/S5hcE/325D9Dex82x +YkrxLx+N9bQo7XihDVD5c+vecw/SyVKKcLnfx2Aw2IesFBCq0PIfr9DTnFNuzhooUbt RMhvvZd3Xe2WIvYPEFP/3oHkrE+tDEbUpZRlnGI5Zjkylr/7ZyCkvF8So3GDXLZ1mj+W Jp6EmvMBnX5AXt/vTb/jbYLPHuJvH6Db4k/3VnkPoot2KmBn+n9DwdS/3yXI1I44NInz TMlg== X-Gm-Message-State: AD7BkJJmK7wuzU1wB0vOoNz2Yw5raQTLkuivwkh4Imv9sbATpHDzKVZvgKqrlVtO21GslYoveVkvICsk2b96fQ== MIME-Version: 1.0 X-Received: by 10.112.170.137 with SMTP id am9mr3877791lbc.84.1457796976021; Sat, 12 Mar 2016 07:36:16 -0800 (PST) Received: by 10.25.216.205 with HTTP; Sat, 12 Mar 2016 07:36:15 -0800 (PST) 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 15:36:00 -0000 Message-ID: Subject: Re: Question about tar v1.28 From: Bryan Berns To: Douglas Coup , cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00183.txt.bz2 > 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