From owner-cvs-all@FreeBSD.ORG Sun Jun 6 02:56:41 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4CC516A4CE; Sun, 6 Jun 2004 02:56:41 -0700 (PDT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C8FB43D1D; Sun, 6 Jun 2004 02:56:41 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])i569ud4u009981; Sun, 6 Jun 2004 19:56:39 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i569uaLS008398; Sun, 6 Jun 2004 19:56:37 +1000 Date: Sun, 6 Jun 2004 19:56:36 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Tim Kientzle In-Reply-To: <40C2E401.5010400@freebsd.org> Message-ID: <20040606195023.M3004@gamplex.bde.org> References: <20040605053115.45AE416A585@hub.freebsd.org> <20040605000326.B54841@root.org> <20040606143616.W2060@gamplex.bde.org> <40C2E401.5010400@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Tim Kientzle cc: src-committers@FreeBSD.org cc: cvs-src@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Nate Lawson Subject: Re: cvs commit: src/lib/libarchive archive_read_extract.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 09:56:41 -0000 On Sun, 6 Jun 2004, Tim Kientzle wrote: > Bruce Evans wrote: > > On Sat, 5 Jun 2004, Tim Kientzle wrote: > > In fact, this stuff is quite broken. After "cd /tmp; ln -s /tmp foo", > > tarring up foo[/.] gives the following misbehaviours with yesterday's > > versions of tars: > > > > tar cf z foo: > > only puts foo in the archive (correct) > > bsdtar cf z foo: > > same, except bsdtar seems to be too smart about padding the output > > to a block boundary for regular files, so subsequent piping of the > > file might not work > > The default padding behavior for bsdtar was changed quite > a while ago to not pad regular files; are you sure you're up-to-date? Yes; not padding is a bug and the above says that I have it. > > tar cf z foo/: > > only puts foo in the archive (broken) > > bsdtar cf z foo/: > > same > > Here, bsdtar cf z foo/ does follow the symlink, which I > presume you believe to be the correct behavior? Yes. foo/ is not a symlink (the slash forces folling the symlink) in the kernel, so it should do so in utilities too. Tab completion in shells cah cause problems here. You want the symlink and type foo, but tab completion may change it to "foo/". Bruce