From owner-freebsd-current Fri Jan 14 2: 7:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 44BEB14A13; Fri, 14 Jan 2000 02:07:36 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id LAA20279; Fri, 14 Jan 2000 11:07:24 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Fri, 14 Jan 2000 11:07:23 +0100 (CET) From: Trond Endrestol To: Sheldon Hearn Cc: FreeBSD stable , FreeBSD current Subject: Re: Making sure /var/tmp/vi.recover exists during reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 11 Jan 2000, Sheldon Hearn wrote: > Not until someone can explain how making /var/tmp a symlink to /tmp is > sensible, given that /var/tmp is documented as containing "temporary > files that are kept between system reboots" (see hier(7)). > > So basically, no. :-) I chose to use MFS for /tmp and symlinking /var/tmp and /usr/tmp to /tmp for sake of speed. No disk activity is involved when the temporary files on the MFS are in use. (This slightly false if the MFS is paged out or swapped out completely.) If I want something preserved between reboots, I'll use /var/otmp which is the original /var/tmp or my own ~/tmp directory. ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.4 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message