Date: Mon, 3 Apr 2000 10:20:54 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Anatoly Vorobey <mellon@pobox.com> Cc: Bruce Evans <bde@zeta.org.au>, Marc Olzheim <marcolz@stack.nl>, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/17619: pax cannot read all tar files created by tar. Message-ID: <20000403102054.A8152@stack.nl> In-Reply-To: <20000402131424.A61897@happy.checkpoint.com>; from mellon@pobox.com on Sun, Apr 02, 2000 at 01:14:24PM %2B0000 References: <200004020840.AAA76390@freefall.freebsd.org> <Pine.BSF.4.21.0004022001380.1363-100000@alphplex.bde.org> <20000402131424.A61897@happy.checkpoint.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Bah. So what should be done in this case (assuming something needs > to be done?). I can patch pax to accept one-block archives and > yet produce correct archives - maybe that's the way to go? Given that > the GNU tar maintainer had more than 8 years to think about it, he's > obviously emotionally attached to one-trailing-block files and won't > let them go ;) That seems like a good idea to me. > > I admit I didn't even know pax(1) existed until I saw the PR and > was sufficiently intrigued to look at it ;) Well, I usually use the -rw option which does not need a pipe to copy directory-trees. Furthermore it uses a more sensible exit-code system than GNU-tar. > > By the way, Marc, Solaris's tar (SunOS 5.6) does handle correctly your > example (creates a tarfile with two trailing blocks), so if you have > anything specific from Solaris's tar that breaks pax, do tell. Hmm, I must 've tried the wrong file, since I cannot reproduce it. So it seems to work fine... Sorry for the fuss. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000403102054.A8152>