Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Jun 2005 19:25:43 +1000
From:      Tim Robbins <tjr@freebsd.org>
To:        Tim Kientzle <kientzle@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   cpio/pax using libarchive? (was Re: Replace /rescue/vi with mined(1) from DragonFlyBSD)
Message-ID:  <20050620092543.GA54301@cat.robbins.dropbear.id.au>
In-Reply-To: <42B5C0BC.40904@freebsd.org>
References:  <20050617214658.GA41804@troutmask.apl.washington.edu> <58826.1119044951@critter.freebsd.dk> <20050617220222.GA42080@troutmask.apl.washington.edu> <20050617220653.GA114@saltmine.radix.net> <20050617221353.GA48584@troutmask.apl.washington.edu> <20050618061603.GM50157@cirb503493.alcatel.com.au> <20050619033904.GB3061@dragon.NUXI.org> <20050619070640.GQ50157@cirb503493.alcatel.com.au> <42B5C0BC.40904@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 19, 2005 at 12:00:12PM -0700, Tim Kientzle wrote:
> Peter Jeremy wrote:
> >On Sat, 2005-Jun-18 20:39:04 -0700, David O'Brien wrote:
> >>On Sat, Jun 18, 2005 at 04:16:04PM +1000, Peter Jeremy wrote:
> >>
> >>>If you're looking for ways to save space in /rescue, there are other
> >>>low-hanging fruit before you start moving to yet another editor:
> >>
> >>>- pax (when the new libarchive tar is available)
> >>
> >>Pax does more than just tar archives.  Can libarchive'ed tar handle cpio
> >>archives?
> >
> >According to tar(1) and libarchive-formats(3), yes it read anything that
> >pax can.  (It can't write cpio but I don't see that as a requirement in
> >/rescue).
> 
> Yes, it can write cpio.  (Posix octet-oriented cpio format, also called 
> 'odc cpio'  Other variants are easy to add if there's demand.)
> 
> Is that not in the manpages?  I'll add it.

This is a bit off topic, but is there a good reason (other than lack of
time) that cpio and pax could not be rewritten to use libarchive?
Doing that would win us at least (a) a pax that correctly extracts GNU tar
archives, and (b) a non-GPL cpio implementation.

For the sake of completeness, it may also make sense to make shar either
a C program that calls into libarchive or a wrapper around tar -Wformat=shar,
but this doesn't have much practical value.


Tim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050620092543.GA54301>