From owner-freebsd-hackers Mon Apr 13 22:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25137 for freebsd-hackers-outgoing; Mon, 13 Apr 1998 22:30:51 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25132 for ; Tue, 14 Apr 1998 05:30:46 GMT (envelope-from fullermd@futuresouth.com) Received: from localhost (fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id AAA16444 for ; Tue, 14 Apr 1998 00:30:45 -0500 (CDT) Date: Tue, 14 Apr 1998 00:30:45 -0500 (CDT) From: "Matthew D. Fuller" To: hackers@FreeBSD.ORG Subject: the place of vi 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 OK, here's a question... Is vi statically linked? If so, what's the chance that it could be stuck in /bin, say? It's kinda aggravating to bring the system up in single user mode and have to fsck and mount /usr jsut to be able to change something stupid in rc.conf that I forgot. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message