| 1 |
> I guess I have to run emerge sync and emerge -uD world on each client |
| 2 |
> still, |
| 3 |
> but they use the http replicator instead of gentoo servers.... for both |
| 4 |
> updating the portage/rsync files and downloading the distfiles (via the |
| 5 |
> http |
| 6 |
> replicator)? |
| 7 |
|
| 8 |
In the case of distfiles and sync's, you're still using primary gentoo |
| 9 |
servers for the first fetch; the cached files are used after that. |
| 10 |
|
| 11 |
Basically emerge is going to want a file foo.tar.bz2 to complete an ebuild; |
| 12 |
it builds a url in the form of http://gentoo.mirror.com/gentoo/ that comes |
| 13 |
from /etc/make.conf and adds the necessary components |
| 14 |
"/distfiles/foo.tar.bz2". It then calls wget to retrieve the components. |
| 15 |
Since the http-replicator proxy is in use, when wget calls through the proxy |
| 16 |
it will see if foo.tar.bz2 is in the cache; if so it returns the cached |
| 17 |
copy. If not it is retrieved from the url provided by wget so |
| 18 |
gentoo.mirror.com is used for the retrieval. |
| 19 |
|
| 20 |
For sync the primary server handles the emerge --sync against the official |
| 21 |
gentoo mirror; internal systems sync against the local server, but the data |
| 22 |
still originates from the official gentoo mirrors. |
| 23 |
|
| 24 |
> I still have to run 'emerge -uD world' on the server/workstation |
| 25 |
> manually each day? |
| 26 |
|
| 27 |
Each system is still administrated as if it is a standalone box; so you can |
| 28 |
choose to or not to "emerge -uD world" on a system by system basis. |
| 29 |
|
| 30 |
My primary rsync/http-replicator server is also my mail server, web server, |
| 31 |
firewall, etc. I try not to "emerge -uD world" on it until I really have |
| 32 |
to. It's your decision on your end when to do it on the server. |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives