well, it looks like my sh has some dependancies too, so I wouldn't worry about it really.
[EMAIL PROTECTED] /usr/ports/lang/php5]# ldd `which sh` /bin/sh: libedit.so.5 => /lib/libedit.so.5 (0x2808c000) libncurses.so.6 => /lib/libncurses.so.6 (0x280a0000) libc.so.6 => /lib/libc.so.6 (0x280df000) On 5/22/06, Bill Schoolcraft <[EMAIL PROTECTED]> wrote:
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. ############################################### [EMAIL PROTECTED] /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." _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"