Date: Mon, 29 Aug 2005 00:31:34 -0700 (PDT) From: Jon Dama <jd@ugcs.caltech.edu> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. Message-ID: <Pine.LNX.4.53.0508290022390.20467@riyal.ugcs.caltech.edu> In-Reply-To: <4312AEE0.8080806@mac.com> References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> <Pine.LNX.4.53.0508282332420.20467@riyal.ugcs.caltech.edu> <4312AEE0.8080806@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Um, that they may be but... I was under the impression (mistaken?) that /tmp is a directory defined under the POSIX standard and is in fact supposed to be flushed in those cases, and that /var/tmp is to be used for programs desiring persistant storage across shutdowns (scheduled and unscheduled). Perhaps it only says that a program is not allowed to rely on /tmp being persistent. I don't have a copy at hand :-/ -Jon On Mon, 29 Aug 2005, Chuck Swiger wrote: > Jon Dama wrote: > > yes, that's quite generous. > > > > why isn't /tmp just an mfs mount though? > > While I like that suggestion personally, some people get perturbed about files > in /tmp going away if the power fails or you reboot. > > -- > -Chuck >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.53.0508290022390.20467>