From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about compilation
Date: Sun, 16 Feb 2025 13:12:17 -0600 [thread overview]
Message-ID: <a064ca47-d222-a12a-d3b0-96143ebf992a@gmail.com> (raw)
In-Reply-To: <19034639-6ae2-4d88-bcfb-a00d6bbd1803@youngman.org.uk>
Wols Lists wrote:
> On 09/02/2025 05:28, Dale wrote:
>> Oops. I didn't think about it being on tmpfs.
>
> /var/tmp should not be on tmpfs. /tmp may or may not survive a reboot,
> /var/tmp is exlicitly where applications are supposed to store their
> crash recovery stuff, and so it is explicitly defined as surviving a
> reboot.
>
> Doesn't stop people who don't know this from setting their systems up
> wrong - I did that initially :-)
>
> Cheers,
> Wol
>
>
I have mine set up this way.
tmpfs on /var/tmp/portage type tmpfs (rw,noatime,size=73400320k)
It's not /var/tmp that is on tmpfs but /var/tmp/portage that is. That
way OS related stuff is fine but portage stuff that isn't really needed
in most cases is gone. I also manually clean it sometimes because
failures can sometimes build up and take up to much space. On my old
rig, this is really true since it is more limited on memory than the new
rig. Going from 32GBs to 128GBs is a big increase in options.
Good thing to check and mention tho. If not done correctly, it could
cause issues.
Dale
:-) :-)
next prev parent reply other threads:[~2025-02-16 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 14:47 [gentoo-user] Question about compilation Jacques Montier
2025-02-08 19:00 ` Filip Kobierski
2025-02-08 23:07 ` Jack
2025-02-09 0:11 ` Michael
2025-02-09 0:20 ` Dale
2025-02-09 0:23 ` Matt Jolly
2025-02-09 5:28 ` Dale
2025-02-16 17:22 ` Wols Lists
2025-02-16 19:12 ` Dale [this message]
2025-02-09 0:46 ` [gentoo-user] " Nuno Silva
2025-02-09 10:23 ` [gentoo-user] " MLR
2025-02-09 14:36 ` Håkon Alstadheim
2025-02-09 16:44 ` Jacques Montier
2025-02-09 17:06 ` Michael
2025-02-09 17:22 ` Jacques Montier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a064ca47-d222-a12a-d3b0-96143ebf992a@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox