1 |
On Friday, 9 February 2018 08:11:29 GMT Neil Bothwick wrote: |
2 |
> On Thu, 8 Feb 2018 23:18:19 +0000, Wol's lists wrote: |
3 |
> > > More specifically, /var/tmp is traditionally supposed to be |
4 |
> > > non-volatile (across reboots). |
5 |
> > > |
6 |
> > > Comparatively the contents of /tmp can be volatile (across reboots). |
7 |
> > > |
8 |
> > > I would advise against mounting /var/tmp on tmpfs. |
9 |
> > |
10 |
> > EMPHATICALLY YES. |
11 |
> > |
12 |
> > /tmp is defined as being volatile - stuff can disappear at any time. |
13 |
> > |
14 |
> > /var/tmp is defined as the place where programs store stuff like crash |
15 |
> > recovery files. Mounting it tmpfs is going to screw up any programs |
16 |
> > that reply on that *defined* behaviour to recover after a crash. |
17 |
> > |
18 |
> > Mounting /var/tmp/portage as tmpfs is perfectly fine as far as I know - |
19 |
> > I do it myself. |
20 |
> |
21 |
> Why mess around with another tmpfs? Just set PORTAGE_TMPDIR="/tmp" in |
22 |
> make.conf. Job done! |
23 |
|
24 |
Acting on the advice of various Gentoo guides, I have this: |
25 |
|
26 |
# grep tmp /etc/fstab |
27 |
tmpfs /var/tmp/portage tmpfs noatime,uid=portage,gid=portage,mode=0775 0 0 |
28 |
tmpfs /tmp tmpfs noatime,nosuid,nodev,noexec,mode=1777 0 0 |
29 |
|
30 |
Are you saying I don't gain anything from it? |
31 |
|
32 |
-- |
33 |
Regards, |
34 |
Peter. |