On Sat, 2 Apr 2011 16:19:45 +0100, Peter Humphrey wrote: > > I've found there's just too much overhead with distcc, plus much of > > the work is still done locally. I have a couple of Atom boxes, a > > server and a netbook, and I've set up a chroot for each on my > > workstation. In the chroot I have FEATURES=buildpkg, using an NFS > > mounted PKGDIR available to both computers, then I emerge -k on the > > Atom box. > > Just to confirm, and to save me having to think more deeply than I'm > able pro tem, does each chroot have identical make.conf and package.use
Yes. the script that I use to start up and enter the chroot for each system not only does the usual mounting of /dev/ and /proc in the chroot, it also rsyncs /etc/portage and /var/lib/portage/world* with the real target. Make.conf has to be maintained manually, because there are settings in the two that need to be different, although I suppose I could split out the common settings, USE, CHOST etc, into a separate file and source that. > to those on its target? And do you nfs-mount only the PKGDIR, or the > whole of /usr/portage/ ? Just PKGDIR and DISTDIR, I have an NFS exported directory that contains a global DISTDIR and individual PKGDIRS, as well as my and layman's overlays. -- Neil Bothwick We can sympathize with a child who is afraid of the dark, but the tragedy of life is that most people are afraid of the light.
signature.asc
Description: PGP signature
