Date: Thu, 14 May 2009 00:29:59 +0200 From: Polytropon <freebsd@edvax.de> To: nightrecon@verizon.net Cc: freebsd-questions@freebsd.org Subject: Re: How to move vi to /bin Message-ID: <20090514002959.cb34499f.freebsd@edvax.de> In-Reply-To: <gue44o$pqu$1@ger.gmane.org> References: <cb0fa7b70905130021t390bb560r4a1dd64ab3b2e79@mail.gmail.com> <20090513082716.GB1363@joni.subvert.org.uk> <b79ecaef0905130130o10d593cdm3fb60b6175112d67@mail.gmail.com> <gue44o$pqu$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 May 2009 05:34:43 -0400, Michael Powell <nightrecon@verizon.net> wrote: > Yes - use the /rescue/vi as it has been statically compiled so it does not > rely on dynamic libraries which may not be available. The purpose here is > have a fallback position for repairing a damage/problem which may prevent a > successful mount of /usr. In addition, you eventually want to do something about the termcap files that - at least I think - vi needs to run in a usable manner. The default is /etc/termcap@ -> /usr/share/misc/termcap - and in a "worst case scenario" /usr is out of reach. You can copy the file /usr/share/misc/termcap to /etc, run "cap_mkdb /etc/termcap" and then have /etc/termcap and /etc/termcap.db, which you can then symlink to /usr/share/misc/termcap and /usr/share/misc/termcap.db again. But note that this might lead to interferences with the freebsd-update tool as well as with the canonical way of updating the system through "make update" and "make build/install kernel/world". -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090514002959.cb34499f.freebsd>