Date: Sun, 11 Mar 2007 17:42:28 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@freebsd.org Subject: Re: BSDtar performance vs GNUtar (Re: cvs commit: src/usr.bin/tar Makefile bsdtar.c bsdtar.h bsdtar_platform.h config_freebsd.h getdate.y matching.c read.c tree.c util.c write.c src/usr.bin/tar/test config.sh test-acl.sh test-basic.sh test-deep-dir.sh test-flags.sh test-nodump.sh ...) Message-ID: <45F4A1F4.4060703@freebsd.org> In-Reply-To: <20070312001026.GA20000@xor.obsecurity.org> References: <200703111036.l2BAaha6031394@repoman.freebsd.org> <45F46291.4090209@freebsd.org> <20070312001026.GA20000@xor.obsecurity.org>
index | next in thread | previous in thread | raw e-mail
>>Bsdtar should now be considerably faster than before. >>I'd appreciate any feedback ... > > The first archive was created with bsdtar (tar cvf ports.tar ports) > which made gtar bitch a bit .... Which version of gtar were you using? In my testing, there's a small but definite slowdown from gtar 1.13 to 1.15 to 1.16. > ... gtar bitch a bit about unknown options (SCHILY.*) ... bsdtar should probably warn about unknown options as well; I'll have to look into that. (It's a little tricky because libarchive is set up to only return one error for any one operation. I might have to generalize that.) Now that gtar is following standards, I wonder if they'll adopt some of the extensions developed by other people? (Such as Joerg Schilling's solid work on integrating file flags and ACL support into pax format.) Tim Kientzlehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45F4A1F4.4060703>