| 1 |
Peter Humphrey wrote: |
| 2 |
> On Sunday, 5 January 2020 10:01:23 GMT Philip Webb wrote: |
| 3 |
> |
| 4 |
>> If you try to emerge LO or FF using a tmpfs , Portage tells you not to. |
| 5 |
> I just thought I'd say that I haven't had any warnings not to use tmpfs when |
| 6 |
> emerging LO or FF. I do have 32GB RAM though, which I dare say makes a |
| 7 |
> difference. Maybe portage is even cleverer than I thought! |
| 8 |
> |
| 9 |
> # grep tmpfs /etc/fstab |
| 10 |
> tmpfs /var/tmp/portage tmpfs noatime,uid=portage,gid=portage,mode=0775 0 0 |
| 11 |
> tmpfs /tmp tmpfs noatime,nosuid,nodev,noexec,mode=1777 0 0 |
| 12 |
> # ls /etc/portage/*env |
| 13 |
> /etc/portage/env: |
| 14 |
> /etc/portage/package.env: |
| 15 |
> |
| 16 |
|
| 17 |
|
| 18 |
When emerging some of the packages, FF, LOo and a few others, emerge |
| 19 |
runs a precheck for space. If it doesn't see enough space, it spits out |
| 20 |
a warning. At one point I think it would stop but not sure what it does |
| 21 |
now. Like you, I have 32GBs of ram. Space for tmpfs isn't much of a |
| 22 |
problem. I can't recall the last time I saw that error message. Even |
| 23 |
when I had 16GBs of memory, it would pass the test. 8GBs may trigger |
| 24 |
issues tho. |
| 25 |
|
| 26 |
The bad thing is, emerge doesn't seem to take into account when emerging |
| 27 |
more than one at a time. If you for example need to upgrade FF and LOo |
| 28 |
at the same time, it may have enough for one to compile but not both at |
| 29 |
the same time. With 16GBs in the past, I've had issues with that. |
| 30 |
Since the default is half of memory, it may pass the precheck but run |
| 31 |
out of tmpfs when doing both. For some reason, that happens often. :/ |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives