| 1 |
On Tue, 17 Apr 2007 00:01:24 +0200, Michal 'vorner' Vaner wrote: |
| 2 |
|
| 3 |
> > > Now you can mount /var remotely (portage compiles there and needs |
| 4 |
> > > lots of space) - this way you need only the space for installed |
| 5 |
> > > programs, not compiling and compile on other machine using distcc. |
| 6 |
> > |
| 7 |
> > portage can use any directory you like for its workspace, you don't |
| 8 |
> > have to remote mount /var to achieve this. You could mount /var/tmp |
| 9 |
> > over NFS, but setting PORTAGE_TMPDIR is less kludgy. |
| 10 |
> |
| 11 |
> Well, seems on the same level for me, but that is only personal |
| 12 |
> preference. |
| 13 |
|
| 14 |
It's not the same at all. you are advocating mounting the whole of /var |
| 15 |
on a networked filesystem, which could affect the performance of the |
| 16 |
system as a whole. |
| 17 |
|
| 18 |
> But the point with this one is - PORTAGE_TMPDIR (besides, |
| 19 |
> isn't it PORTAGE_WORKDIR?) |
| 20 |
|
| 21 |
No, it's PORTAGE_TMPDIR, check your make.conf. |
| 22 |
|
| 23 |
> is gentoo specific, but you can do the |
| 24 |
> mounting just anywhere. |
| 25 |
|
| 26 |
The last time I looked, portage compiles were Gentoo-specific too. If you |
| 27 |
want to change where portage uses for its workspace, it is much safer to |
| 28 |
use the provided configuration settings than move the whole of a |
| 29 |
system-critical directory to an unreliable medium. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
User-friendly: (adj.) trivialized, slow, incapable, and boring. |
Archives