Date: Fri, 30 Mar 2012 19:31:50 +0200 From: "C. P. Ghost" <cpghost@cordula.ws> To: sthaug@nethelp.no Cc: freebsd-current@freebsd.org Subject: Re: Using TMPFS for /tmp and /var/run? Message-ID: <CADGWnjXj5W_UCHPExNjxHgq3EZHP1GwocnK4kOHLch5y3gNG0A@mail.gmail.com> In-Reply-To: <20120330.151848.41706133.sthaug@nethelp.no> References: <4F746F1E.6090702@mail.zedat.fu-berlin.de> <4F74BCE8.2030802@vangyzen.net> <CACM2%2B-7Ahn6J=CTASe0g48%2BSD2vvLVd_hG3DRZmvO31QszG5Xw@mail.gmail.com> <20120330.151848.41706133.sthaug@nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 30, 2012 at 3:18 PM, <sthaug@nethelp.no> wrote: >> > However, if you always want to use tmpfs instead of stable storage, >> please do not. =A0Some people expect /tmp to be persistent. =A0This is w= hy >> /etc/defaults/rc.conf has clear_tmp_enable=3D"NO". =A0Changing this woul= d break >> the POLA. >> > >> This is a mistake. >> >> The default should be clear_tmp_enable=3D"YES" >> if only to uncover those broken configurations that expect /tmp to be >> persistent. > > If you want to break POLA and make a lot of people angry, sure. > Otherwise no. I couldn't agree more. Not clearing /tmp on reboot has been the norm for way too long and it is too late to change now. It's not just POLA, it also involves deleting data of unaware users, and that should be avoided. Anyone willing to change policy w.r.t. /tmp can do so on their own machines. Nothing is preventing them from doing so. But by changing defaults, one should err on the side of caution and remain conservative, IMHO. -cpghost. --=20 Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGWnjXj5W_UCHPExNjxHgq3EZHP1GwocnK4kOHLch5y3gNG0A>