From owner-freebsd-stable Fri Jan 14 7:13: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AB1F14C40; Fri, 14 Jan 2000 07:12:59 -0800 (PST) (envelope-from khera@kciLink.com) Received: by kci.kciLink.com (Postfix, from userid 100) id 6F6D3E89D; Fri, 14 Jan 2000 10:12:54 -0500 (EST) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14463.15606.393166.953233@kci.kciLink.com> Date: Fri, 14 Jan 2000 10:12:54 -0500 (EST) To: Trond Endrestol Cc: Sheldon Hearn , FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TE" == Trond Endrestol writes: TE> I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to TE> /tmp for sake of speed. TE> No disk activity is involved when the temporary files on the MFS are TE> in use. (This slightly false if the MFS is paged out or swapped out TE> completely.) If vi.recover is not going to survive a reboot, why bother having it at all? That's is sole purpose for existing. If you don't like the warning, just delete the recovery procedure rather than creating the directory. It does no good for you to try to recover something that will never be there. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message