Wendall Cada wrote:
>> Consider a binary server. Build on one machine, install on many.
>>
>> emerge -gK world
>>
>> will use the binary server to intelligently fetch updates
>> and use HTTP/FTP for the process. It will merge extactly
>> what is posted on the server based on the metadata in the
>> binaries.
>>
>> --NJ
>>
>
> I use this setup all the time. I maintain 14 Gentoo boxes, seven of
> which are off site using this method.
I have 2 issues with this:
1.) Updates are one way. This is both good and bad. Good in that it's
more secure. Bad in that you have to either use the server machine
to build a package, or else build the package somewhere else and
upload it to the server machine. I'm lazy. That's a hassle, particularly
if I use quickpkg to initially populate the server machine's packages
directory, then find that I need to rebuild a lot of those packages.
2.) You're storing binary packages on each client. With an NFS setup,
you only store them on one machine. Network trashing is probably
actually BETTER if they're all stored locally on each machine though.
I originally didn't think this would be the case, but see below:
However, having said the above, I have tested out my NFS setup with
the primary portage tree sync'd via gentoo-rsync-mirror to my remote server,
and with /usr/portage/packages and /etc/portage shared via NFS over
ADSL. It isn't much faster, if at all, than sharing the whole /usr/portage
via NFS over ADSL. I'm not sure why portage crunches so much on
/usr/portage/packages, but it really slows the beast down. So I'm definitely
considering `emerge -g`.
--
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v) 423-559-5145 (f)
http://www.wingnet.net
--
[email protected] mailing list
