From owner-freebsd-questions Thu Feb 17 22:30:51 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 891F637B791 for ; Thu, 17 Feb 2000 22:30:47 -0800 (PST) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.9.3/8.9.3) id RAA70416; Fri, 18 Feb 2000 17:30:17 +1100 (EST) (envelope-from nicks) Date: Fri, 18 Feb 2000 17:30:17 +1100 From: Nick Slager To: R Joseph Wright Cc: freebsd-questions@FreeBSD.ORG Subject: Re: vi weirdness Message-ID: <20000218173017.D68962@albury.net.au> Mail-Followup-To: R Joseph Wright , freebsd-questions@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from joseph@nwlink.com on Thu, Feb 17, 2000 at 06:32:27PM -0800 X-Homer: Whoohooooooo! Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm having trouble with vi. In fact I'm having a lot of trouble. I just > tried to move /var to /usr/var and create a link to /var. Instead of > moving /var to /usr/var, it copied all of /var except /var/run/log. So, I > didn't create the link or anything. /var is still intact where it > was. But now when I try to use vi, it says "too many levels of symbolic > links" and it won't let me edit files. > You're probably better off to do this with tar, a la: mkdir /usr/var cd /var tar cf - . | (cd /usr/var; tar xf -) cd .. mv /var /var.old ln -s /usr/var /var chmod 1777 /var/tmp And a reboot after this is also a good idea. Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message