Date: Mon, 20 Jun 2005 05:39:39 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Replace /rescue/vi with mined(1) from DragonFlyBSD Message-ID: <20050619193939.GR50157@cirb503493.alcatel.com.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, 2005-Jun-19 12:00:12 -0700, Tim Kientzle wrote:
>Peter Jeremy wrote:
>>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.)
libarchive-formats(3) states:
Tar Formats
The libarchive(3) library can read most tar archives. However, it only
writes POSIX-standard ``ustar'' and ``pax interchange'' formats.
But tar(1) does state it can write cpio. I skipped from tar(1) to
libarchive-formats(3) too quickly and missed that, sorry.
I think that just strengthens my argument that having pax in /rescue
is redundant, superfluous and unnecessary :-).
--
Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050619193939.GR50157>