From owner-freebsd-current@FreeBSD.ORG Tue May 27 04:29:04 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 3B3CE106566C for ; Tue, 27 May 2008 04:29:04 +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 138FC8FC2B for ; Tue, 27 May 2008 04:29:03 +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 m4R3xHtv034900; Mon, 26 May 2008 20:59:17 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <483B8715.9060609@freebsd.org> Date: Mon, 26 May 2008 20:59:17 -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: Giorgos Keramidas References: <483B0FDB.1060400@freebsd.org> <87d4n8zbqp.fsf@kobe.laptop> In-Reply-To: <87d4n8zbqp.fsf@kobe.laptop> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Call for Testers: bsdcpio 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: Tue, 27 May 2008 04:29:04 -0000 Giorgos Keramidas wrote: > On Mon, 26 May 2008 12:30:35 -0700, Tim Kientzle wrote: > >>Please let me know your experiences with bsdcpio. > > Are there particular tests you want us to run with bsdcpio? I'm > using cpio a lot for copying stuff around, so if there's anything > particular you want me to watch out for, or something you'd like > tested/stressed a bit more, just let me know. I don't know of any particular weak points right now. But this is still new enough code that there's certainly some bugs, surprises, or missing features. The trickiest issue has been getting hardlink handling correct; -p mishandled hardlinks up until just a few weeks ago, and the different strategies used for handling hard links in old and new cpio formats have been responsible for a lot of code thrash. There may also be subtle differences compared to GNU cpio, especially in areas like filename pattern matching. I'm also looking for feedback about the feature set, including missing options and cpio file format variants that people rely on. Basically, I just want people to use it, notice if it causes problems ;-), and let me know about it. Cheers, Tim