1 |
2018-02-09 10:11 GMT+02:00 Neil Bothwick <neil@××××××××××.uk>: |
2 |
> On Thu, 8 Feb 2018 23:18:19 +0000, Wol's lists wrote: |
3 |
> |
4 |
>> > More specifically, /var/tmp is traditionally supposed to be |
5 |
>> > non-volatile (across reboots). |
6 |
>> > |
7 |
>> > Comparatively the contents of /tmp can be volatile (across reboots). |
8 |
>> > |
9 |
>> > I would advise against mounting /var/tmp on tmpfs. |
10 |
>> > |
11 |
>> EMPHATICALLY YES. |
12 |
>> |
13 |
>> /tmp is defined as being volatile - stuff can disappear at any time. |
14 |
>> |
15 |
>> /var/tmp is defined as the place where programs store stuff like crash |
16 |
>> recovery files. Mounting it tmpfs is going to screw up any programs |
17 |
>> that reply on that *defined* behaviour to recover after a crash. |
18 |
>> |
19 |
>> Mounting /var/tmp/portage as tmpfs is perfectly fine as far as I know - |
20 |
>> I do it myself. |
21 |
> |
22 |
> Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in |
23 |
> make.conf. Job done! |
24 |
|
25 |
It is an interesting idea. But why it is not done by default then? |
26 |
|
27 |
Can somebody think of a situation when it should not be done? |
28 |
|
29 |
My /tmp is not on tmpfs currently. Only /run |
30 |
|
31 |
May be, it is not a good idea to put /mnt on tmpfs at the time of |
32 |
Spector and Meltdown? |