On 09/05/2015 08:30 AM, Dale wrote: [snip] > > > Well, you can leave that in fstab for when you can use it. This is my > understanding. Putting portage's work directory on tmpfs speeds up the > compile because it is done in memory instead of a hard drive. Thing is, > there may be times when some packages don't have enough space to > compile, you run out of tmpfs basically. One example, libreoffice which > uses a lot. I've also found that Firefox also uses a lot of space too. > Of course, I have enough memory at the moment for both to compile. You > may not tho. > > When you don't have enough for say Libreoffice to compile on tmpfs, you > then set a exception for that package. That is where notmpfs comes in. > That allows you to use tmpfs for all the other packages but puts it back > on spinning rust for that package, and any other package you set it for > such as Firefox. > > So, if you have the memory even for large packages like Libreoffice, > just remove the notmpfs part and leave fstab like it was. Basically, > ignore that part of the wiki since you don't need to set that. If you > have say 6GBs of ram, you would need that line in fstab AND the part > about notmpfs. You would not be able to compile Libreoffice with that > small amount of ram and even Firefox may not either. > > Does that clear up the muddy waters any or am I making it worse? Maybe > the better question would be, how much memory does your rig have on it? > Then folks can advise on where to go based on that. ;-) > > Dale
Thanks Dale for explanation. I have 8GB RAM and with fstab: tmpfs /var/tmp/portage tmpfs defaults 0 0 it creates 3.9Gb ram disk but that is not enough for firefox I think my default setup was OK with: /etc/portage/package.env /etc/portage/env/notmpfs.conf Thelma
