From: "Gerrit Kühn" <gerrit.kuehn@aei.mpg.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /var/tmp on tmpfs
Date: Fri, 9 Feb 2018 11:58:13 +0100 [thread overview]
Message-ID: <20180209115813.50e10cf8e99b028f76960f1a@aei.mpg.de> (raw)
In-Reply-To: <CA+t6X7cYJJhcrwdOSOi93HK72mmAOmW1jaZChVkY8emirMaL9w@mail.gmail.com>
On Fri, 9 Feb 2018 12:30:21 +0200 gevisz <gevisz@gmail.com> wrote about
Re: [gentoo-user] /var/tmp on tmpfs:
> > Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in
> > make.conf. Job done!
>
> It is an interesting idea. But why it is not done by default then?
>
> Can somebody think of a situation when it should not be done?
/var/tmp/portage may take up quite some space, and not everybody will want
to have that on a RAM-based fs.
cu
Gerrit
next prev parent reply other threads:[~2018-02-09 10:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:11 [gentoo-user] /var/tmp on tmpfs gevisz
2018-02-08 17:47 ` [gentoo-user] " Nikos Chantziaras
2018-02-08 18:13 ` Rich Freeman
2018-02-08 19:05 ` Nikos Chantziaras
2018-02-08 19:42 ` Rich Freeman
2018-02-08 21:52 ` gevisz
2018-02-08 21:57 ` Rich Freeman
2018-02-08 22:16 ` gevisz
2018-02-09 1:50 ` Dale
2018-02-09 11:52 ` gevisz
2018-02-08 22:32 ` Nikos Chantziaras
2018-02-08 21:31 ` gevisz
2018-02-08 22:19 ` Nikos Chantziaras
2018-02-08 22:32 ` gevisz
2018-02-08 22:38 ` Rich Freeman
2018-02-08 22:50 ` Tsukasa Mcp_Reznor
2018-02-09 10:07 ` gevisz
2018-02-09 11:00 ` Neil Bothwick
2018-02-08 23:42 ` Grant Taylor
2018-02-10 18:56 ` Kai Krakow
2018-02-10 19:38 ` Wols Lists
2018-02-10 19:52 ` Kai Krakow
2018-02-10 20:06 ` Rich Freeman
2018-02-10 21:13 ` Kai Krakow
2018-02-10 21:20 ` Wol's lists
2018-02-10 22:17 ` Kai Krakow
2018-02-08 19:17 ` [gentoo-user] " Dale
2018-02-08 19:41 ` [gentoo-user] " Nikos Chantziaras
2018-02-09 1:31 ` Dale
2018-02-08 19:50 ` [gentoo-user] " Rich Freeman
2018-02-09 1:24 ` Dale
2018-02-09 10:55 ` gevisz
2018-02-10 19:01 ` [gentoo-user] " Kai Krakow
2018-02-08 21:57 ` [gentoo-user] " gevisz
2018-02-09 1:35 ` Dale
2018-02-08 20:56 ` Grant Taylor
2018-02-08 23:18 ` Wol's lists
2018-02-08 23:28 ` Grant Taylor
2018-02-09 0:02 ` Rich Freeman
2018-02-09 1:15 ` Wol's lists
2018-02-09 2:15 ` [gentoo-user] " Ian Zimmerman
2018-02-09 11:57 ` gevisz
2018-02-10 19:11 ` Kai Krakow
2018-02-09 8:11 ` [gentoo-user] " Neil Bothwick
2018-02-09 10:12 ` Peter Humphrey
2018-02-09 10:58 ` Neil Bothwick
2018-02-10 19:06 ` [gentoo-user] " Kai Krakow
2018-02-09 10:30 ` [gentoo-user] " gevisz
2018-02-09 10:57 ` Neil Bothwick
2018-02-09 10:58 ` Gerrit Kühn [this message]
2018-02-09 22:03 ` Grant Taylor
2018-02-10 19:08 ` [gentoo-user] " Kai Krakow
2018-02-10 18:02 ` Kai Krakow
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=20180209115813.50e10cf8e99b028f76960f1a@aei.mpg.de \
--to=gerrit.kuehn@aei.mpg.de \
--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