Mick wrote:
On Sunday 21 Jul 2013 10:40:11 Dale wrote:
Actually, portage looks for enough space before even starting and still
does. However, when I force it to ignore it, it stops and says it ran
out of space. I'd just rather it didn't use swap anyway. Either way,
OOo and LOo used to need lots of space. I think there was some code
cleanup and maybe some other changes that reduced that a lot. I think
there was also some gcc changes to but not sure on that.
I did some more searching after my last post, at one point it looked for
at least 12GBs from what I found. That was the largest setting I found.
Right, so running /var/tmp/portage on a tmpfs definitely won't work on an old
box of mine with only a few MB of memory.
Not likely. It may for some smaller packages but not for the large ones
for sure.
When I first built this rig, I only had 8GBs of ram and I could only use
it when all the packages to update were smaller ones. Generally, I just
left it on a HDD.
The biggest issue that I run into still, failed emerges are left on
there and take up space that the next packages may need. Thing is, they
have to be there to see what caused it to fail. Of course, the same
thing can happen when on a HDD as well.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how
you interpreted my words!
