Date: Sat, 06 Sep 2008 23:56:33 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: chinsan.tw@gmail.com Cc: arch@freebsd.org Subject: Re: pax in /rescue Message-ID: <20080906.235633.-267228782.imp@bsdimp.com> In-Reply-To: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com>
chinsan <chinsan.tw@gmail.com> writes:
: On Sun, Sep 7, 2008 at 12:40 PM, M. Warner Losh <imp@bsdimp.com> wrote:
: > Is there any reason to continue to include both tar and pax in
: > /rescue?
: >
: Maybe for rescue some important file?
tar can read all the formats that pax can read. Why the duplication
in functionality?
: BTW, could editors/e3 be include into /rescue?
: I think it's ineed to have a text editor to edit some file for rescue.
: Because vi(1) lives in /usr/bin.
/rescue already has nvi.
: ps. e3 is a full featured text editor written in NASM assembler. It is highly
: optimized for size.
I notice pax was there when I was looking at it on my FreeBSD/arm box
:-)
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080906.235633.-267228782.imp>