From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 15:56:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC520106568F for ; Mon, 30 Jun 2008 15:56:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id B206E8FC16 for ; Mon, 30 Jun 2008 15:56:07 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m5UFtdtv026704; Mon, 30 Jun 2008 08:55:44 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <486901FB.5080308@freebsd.org> Date: Mon, 30 Jun 2008 08:55:39 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <20080626110521.GA68764@wep4017.physik.uni-wuerzburg.de> <1214815958.3581.67.camel@localhost> In-Reply-To: <1214815958.3581.67.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: cpio -dumpl damages the files? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 15:56:08 -0000 Vladimir Grebenschikov wrote: > On Thu, 2008-06-26 at 13:05 +0200, Alexey Shuvaev wrote: > >>In a nutshell the problem is that bsdcpio damages the files: > > Same here, also it shows strange warning on every directory being > copied: > > cpio: Can't create 'dst/a/b/c/3': Operation not permitted: Operation not > permitted > > Bad news, that it damaged original files also. > > PS: > upgrading now ... Let me know if you still see this problem after the upgrade. I believe it's completely fixed now. Tim