From owner-freebsd-hackers Sun Sep 5 18:40: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thneed.ubergeeks.com (thneed.ubergeeks.com [209.145.74.245]) by hub.freebsd.org (Postfix) with ESMTP id 8BB12151BB for ; Sun, 5 Sep 1999 18:39:55 -0700 (PDT) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by thneed.ubergeeks.com (8.9.3/8.9.3) with ESMTP id VAA01283; Sun, 5 Sep 1999 21:38:17 -0400 (EDT) (envelope-from adrian@ubergeeks.com) X-Authentication-Warning: thneed.ubergeeks.com: adrian owned process doing -bs Date: Sun, 5 Sep 1999 21:38:17 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Ben Rosengart Cc: hackers@FreeBSD.ORG Subject: Re: placement of vi in the filesystem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 5 Sep 1999, Ben Rosengart wrote: > I'm sure this is old ground, but could anyone please tell me why vi is > in /usr/bin instead of /bin? It would be nice to be able to edit files > in /etc (especially the fstab) without /usr mounted on a vanilla install. IIRC, because vi has a lot of bagage like termcap and curses. I know it's rough, but you do have ed when in single-user mode. On the other hand I built a static nvi and put it in /tmp with a copy of termcap and set the TERMCAP variable. With only / mounted, nvi did just fine, and it only took 460592 and 188100 bytes for the static nvi and termcap respectivly. 620K isn't much to argue about these days unless you want it on a floppy. cheers, Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message