From owner-freebsd-hackers@FreeBSD.ORG Mon May 17 22:55:19 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FF1716A4CE; Mon, 17 May 2004 22:55:19 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C045743D3F; Mon, 17 May 2004 22:55:16 -0700 (PDT) (envelope-from tim@kientzle.com) Received: from kientzle.com (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i4I4oP90037331; Mon, 17 May 2004 21:50:25 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <40A9960E.7050406@kientzle.com> Date: Mon, 17 May 2004 21:50:22 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Max Laier References: <40A96DA2.4080306@freebsd.org> <200405180534.48284.max@love2party.net> In-Reply-To: <200405180534.48284.max@love2party.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: Tim Kientzle Subject: Re: Wanted: Example tar files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2004 05:55:19 -0000 Max Laier wrote: > On Tuesday 18 May 2004 03:57, Tim Kientzle wrote: > <...> > >>An ideal test archive would not be too big (< 16k) and >>have as many as possible of the following: >> * regular file >> * directory >> * hardlink >> * symlink >> * fifo, socket, device node, etc. >> * regular file with very long pathname (>256 characters) >> * symlink to a file with a very long pathname >> * file with 8-bit character in the filename >> * file with 8-bit character in the user or group name >> * file with ACL, file flags, or other extended permissions > > > How about posting such a tar somewhere so people can retar it with whatever > they have? That would require that people be able to untar whatever I provide. There are enough differences among tar implementations (especially for things like long filenames, 8-bit characters, extended permissions, etc) that it's not really possible. This is part of why I want bsdtar to be able to identify and read so many different formats. ;-) I could scrape together a shell script to build a directory with a suitable set of files (can't quite cover all of the above with that, but can cover much of it). I'll see about that. Tim