Date: Fri, 15 May 2009 12:16:46 +0530 From: Manish Jain <invalid.pointer@gmail.com> To: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: freebsd-questions@freebsd.org Subject: Re: How to move vi to /bin Message-ID: <4A0D0FD6.4040107@gmail.com> In-Reply-To: <200905142019.56242.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> References: <cb0fa7b70905130021t390bb560r4a1dd64ab3b2e79@mail.gmail.com> <200905142019.56242.mel.flynn%2Bfbsd.questions@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mel Flynn wrote: > On Wednesday 13 May 2009 09:21:46 manish jain wrote: > >> I want to move vi to /bin so that I have an editor available in >> single-user mode. > > The only reason to need an editor and not have /usr and /var available is to > edit /etc/fstab. It is trivial to spot errors with /rescue/cat and fix with > /rescue/sed, without having to worry about a terminal. > > In all other cases: > fsck -p > /etc/rc.d/mountcritlocal start > /etc/rc.d/ldconfig start > > And one can use any editor one would want. Don't forget to export or setenv > TERM to cons25 from 'dumb'. > From all the discussion I have walked through on the issue of where to place vi, it does appear FreeBSD has a skewed policy on the issue. There are plenty of reasons you might need access an editor in single-user mode - editing fstab is just one. Having to use the workarounds suggested in place of vi is not so good, and manually moving vi to /bin is not simply a matter of 'mv /usr/bin/vi /bin/'. One of the things I would dearly like to see in a future release is vi being placed under /bin. -- Regards Manish Jain invalid.pointer@gmail.com Laast year I kudn't spell Software Engineer. Now I are won.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A0D0FD6.4040107>