Date: Mon, 22 May 2006 09:23:31 -0700 (PDT) From: Bill Schoolcraft <bill@wiliweld.com> To: Jerry McAllister <jerrymc@clunix.cl.msu.edu> Cc: freebsd-questions@freebsd.org Subject: Re: MESS (statically compiled vi ) Message-ID: <Pine.LNX.4.61.0605220918130.12915@liam.billschoolcraft.com> In-Reply-To: <200605221542.k4MFgiQF004622@clunix.cl.msu.edu> References: <200605221542.k4MFgiQF004622@clunix.cl.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 22 May 2006 it looks like Jerry McAllister composed:
> >
> > At Mon, 22 May 2006 it looks like Jerry McAllister composed:
> >
> > > Yup. It is in /usr/bin
> > > I guess, I am so used to putting a copy of vi in /bin shortly after
> > > installing a new system that I assume it is always there.
> > >
> >
> > Can we actually 'de-install' then 're-install' vi(m) from PORTS with
> > it statically compiled?
> >
> > Then we can move it to /bin (?)
>
> You don't really need to de-install it.
> Just cp /usr/bin/vi /bin/.
> Make sure you are happy with the permissions.
>
> It will work. vi is pretty well self contained.
Hmm, not sure if we are talking about in single user mode with only
/ mounted, here is what my version does with a dependency check...
I see it need libs in /lib, which I'm sure is not on it's own
partition, but I was hoping to get vi statically compiled.
###############################################
[root@bsd /usr/ports/editors]-> ldd `which vi`
/usr/bin/vi:
libncurses.so.5 => /lib/libncurses.so.5 (0x280b9000)
libc.so.5 => /lib/libc.so.5 (0x280f8000)
###############################################
--
Bill Schoolcraft | http://wiliweld.com
"If your life was full of nothing but
sunshine, you would just be a desert."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.61.0605220918130.12915>