From owner-freebsd-security Tue Sep 4 14:52:12 2001 Delivered-To: freebsd-security@freebsd.org Received: from allmaui.com (server25.aitcom.net [208.234.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 2491B37B409 for ; Tue, 4 Sep 2001 14:52:08 -0700 (PDT) Received: from allmaui.com (pwnat-3-o.placeware.com [209.1.15.35]) by allmaui.com (8.8.8/8.8.5) with ESMTP id RAA14416; Tue, 4 Sep 2001 17:52:04 -0400 Message-ID: <3B954E5C.7558CDE6@allmaui.com> Date: Tue, 04 Sep 2001 14:57:48 -0700 From: Craig Cowen X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Eli Dart Cc: freebsd-security@FreeBSD.ORG Subject: Re: Good practice for /tmp References: <20010904195037.C7CF02B@usul.nersc.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Solaris mounts it's swap on /tmp while FBSD does not make this available. Why not use the Solaris way of doing things? Eli Dart wrote: > In reply to Matt Dillon : > > > 'man tuning' (with a recent -stable). In it I talk about /tmp vs > > /var/tmp and why it doesn't make sense to keep them separate any more. > > And these days people generally do not rm -rf /tmp at boot either. > > Using an mfs /tmp has the side effect of clearing /tmp at boot. > > --eli > > > > > -Matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message