From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 903751382C5 for ; Fri, 9 Feb 2018 10:12:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5F31DE0BB5; Fri, 9 Feb 2018 10:12:04 +0000 (UTC) Received: from smarthost03a.mail.zen.net.uk (smarthost03a.mail.zen.net.uk [212.23.1.20]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EA8BFE0AF7 for ; Fri, 9 Feb 2018 10:12:03 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03a.mail.zen.net.uk with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1ek5f0-0003yp-7E for gentoo-user@lists.gentoo.org; Fri, 09 Feb 2018 10:12:02 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /var/tmp on tmpfs Date: Fri, 09 Feb 2018 10:12:01 +0000 Message-ID: <253051741.PjgAUXto2j@peak> In-Reply-To: <20180209081129.685e8b1a@digimed.co.uk> References: <63b383d1-e75d-097a-593a-6b955b482676@youngman.org.uk> <20180209081129.685e8b1a@digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03a-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: 605f1f15-5be9-4b3e-9c72-cd2710f3a54c X-Archives-Hash: 208e20156d0629024d5cc52b53b95e4b On Friday, 9 February 2018 08:11:29 GMT Neil Bothwick wrote: > On Thu, 8 Feb 2018 23:18:19 +0000, Wol's lists wrote: > > > More specifically, /var/tmp is traditionally supposed to be > > > non-volatile (across reboots). > > > > > > Comparatively the contents of /tmp can be volatile (across reboots). > > > > > > I would advise against mounting /var/tmp on tmpfs. > > > > EMPHATICALLY YES. > > > > /tmp is defined as being volatile - stuff can disappear at any time. > > > > /var/tmp is defined as the place where programs store stuff like crash > > recovery files. Mounting it tmpfs is going to screw up any programs > > that reply on that *defined* behaviour to recover after a crash. > > > > Mounting /var/tmp/portage as tmpfs is perfectly fine as far as I know - > > I do it myself. > > Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in > make.conf. Job done! Acting on the advice of various Gentoo guides, I have this: # grep tmp /etc/fstab tmpfs /var/tmp/portage tmpfs noatime,uid=portage,gid=portage,mode=0775 0 0 tmpfs /tmp tmpfs noatime,nosuid,nodev,noexec,mode=1777 0 0 Are you saying I don't gain anything from it? -- Regards, Peter.