1 |
I believe you will still need a tree either way. |
2 |
|
3 |
I would just have the master server share it's portage tree over nfs, |
4 |
and then when you update the nodes of the cluster, just mount the nfs |
5 |
share, run your emerge system or world or whatever, and then when you |
6 |
are finished umount the nfs share. |
7 |
|
8 |
I imagine this could be done easily via scripts, complete with error |
9 |
checking for bad mounts bad emerges etc. |
10 |
|
11 |
Ronan Mullally wrote: |
12 |
> Hi Karl, |
13 |
> |
14 |
> On Mon, 21 May 2007, Karl Holz wrote: |
15 |
> |
16 |
> |
17 |
>>> Is there a way to run gentoo without a portage tree on each box? |
18 |
>>> |
19 |
>> yes, if you setup a build system, using a stage3 tarball, and build your |
20 |
>> system into a directory. Portage will only be under your /usr/portage and not |
21 |
>> into the system image you're building. the good thing about using a Stage3 |
22 |
>> tarball is you can build you system on any linux system, build your system |
23 |
>> image, tarball the image, deploy and install grub on x86, yaboot on Mac PPC, |
24 |
>> silo on Sparc64. |
25 |
>> |
26 |
> |
27 |
> How are updates handled? "emerge -uD <pkg|world>" isn't going to work |
28 |
> without a portage tree, so I presume I'd need to tell each server which |
29 |
> packages need to be updated with "emerge <pkg1> <pkg2> ... <pkgn>" to have |
30 |
> it download them from the binhost? |
31 |
> |
32 |
> |
33 |
> -Ronan |
34 |
> |