Date: Thu, 26 Apr 2001 10:00:37 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Brian Somers <brian@Awfulhak.org> Cc: Kris Kennaway <kris@obsecurity.org>, hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: pax(1) gzip functionality Message-ID: <20010426100037.C84210@dragon.nuxi.com> In-Reply-To: <200104261542.f3QFgiM61575@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Thu, Apr 26, 2001 at 04:42:44PM %2B0100 References: <obrien@FreeBSD.ORG> <200104261542.f3QFgiM61575@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote:
> > On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote:
> > > Please review the following code from OpenBSD; it adds -z and -Z
> > > options to pax(1) to gzip(1) the archives created.
> >
> > Sigh. They could have generalized this just a little and supported Bzip2
> > at the same time. Please let me know after you commit this so I can do
> > this.
>
> Is this necessary ? What's the problem with using a pipe ? Isn't
> this the same argument as the xargs one we've just gotten through ?
What's wrong with:
tar cf - foo | gzip >foo.tar.gz
gzip -dc foo.tar.gz | tar xf -
Someone deemed them too inconvient for the number of times they are
invoked. I'm not going to enter that discussion, but _if_ gzip support
is added, I feel bzip2 support should be added to be orthogonal with
today's uses.
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010426100037.C84210>