X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
Message-Id: <1321870509.30560.140661001630353@webmail.messagingengine.com>
From: "Ronald Fischer" <ynnor AT mm DOT st>
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Subject: Please explain afio warning message
Date: Mon, 21 Nov 2011 11:15:09 +0100
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Executing the command

find . -print0 | afio -o -z -Z -0 -Y '*.log' -T 1k -G 2
/cygdrive/c/temp/arch.afio

results in the following warning message:

afio: ".": Cannot create cpio-compatible file header for this input
afio: "/cygdrive/c/temp/save.afio" [offset 0]: Continuing, archive will
not be fully compatible with cpio or afio versions 2.4.7 and lower
afio: "/cygdrive/c/temp/save.afio": Warning: Created archive is not
fully compatible with cpio or afio versions 2.4.7 and lower.
afio: "/cygdrive/c/temp/save.afio": See the ARCHIVE PORTABILITY section
of the manpage.

I read the section about portability, but still don't know the reason
for this warning, only that it somehow must be related to the usage of
"." for denoting the working directory.

Can I safely ignore the warnings? Is there a way to suppress them, other
than redirecting stderr to the bit bucket? cpio compatibility is not
crucial for me.

-- 
Ronald Fischer <ronaldf AT eml DOT cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


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