From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /var/tmp on tmpfs
Date: Thu, 8 Feb 2018 19:02:10 -0500 [thread overview]
Message-ID: <CAGfcS_mftPorirSC_eOnVD2vbjNf7W3fxs+JmX9BVyEypcSmJg@mail.gmail.com> (raw)
In-Reply-To: <63b383d1-e75d-097a-593a-6b955b482676@youngman.org.uk>
On Thu, Feb 8, 2018 at 6:18 PM, Wol's lists <antlists@youngman.org.uk> wrote:
>
> /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.
>
Care to cite an example of such a program in the Gentoo repo? I
certainly can't think of any, and I've been running with /var/tmp on
tmpfs for over a decade.
/var/cache strikes me as a much better place for some kind of recovery
file. While /var/tmp is typically less volatile than /tmp, it isn't
really something that software should just rely on.
Perhaps FHS says otherwise, but anybody relying on FHS is going to get
burned because lots of distros purge /var/tmp. The problem with FHS
is that nobody really bothers to try to update it any longer.
Certainly people think twice before deviating it, but they still do
from time to time, usually in the same ways that other distros
deviate.
--
Rich
next prev parent reply other threads:[~2018-02-09 0:02 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 [this message]
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
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=CAGfcS_mftPorirSC_eOnVD2vbjNf7W3fxs+JmX9BVyEypcSmJg@mail.gmail.com \
--to=rich0@gentoo.org \
--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