[gentoo-user] Re: synchronizing 2 portables

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


> I'd go with Unison, it's ideal for this sort of thing.
OK
 
> > AS far as keeping the installed packages /ebuilds/ concurrent,
> > in some sort of semi-automated method, I'd settle for a script
> > I could run that would check the installed packages, on both
> > portablesand give a list of packages on the one that are not
> > ont he second machine. Kind of like a 'diff for ebuilds' that
> > would list the missing packages on the second portable.

> Is the first portable always updated first? If so, I'd add buildpkg to
> FEATURES in /etc/make.conf and make PKGDIR a directory accessible to
> both, possibly via NFS. Then, provided your USE and CFLAGS are the same
> (running the same make.conf on both would be easiest) to can synchronise
> the second box with the first by copying over /var/lib/portage/world and
> doing "emerge -uavDNk world".


Well, OK.  But if I want to try this method manually first, then I'd:
1. scp the var/lib/portage/world to the second system.
2.  ensure the make.conf USE setting are identical (they are)
3. "emerge -uavD world"
4. No need for the PKGDIR is I duplicate packages on both systems?

???

If this works resonable well, then I'll write a script to
use scp to routinely transfer over the world file. That way
I can do updates and testing on one (master) portable only.
I do not want to use NFS, and duplicating the 
packages is preferable, as their is a good chance the
excessive vibration from industrial environments is going to 
kill a portable, eventually. At that point I want the second
portable ready to go as it becomes the primary portable,
giving me time to purchase and installed a secondary backup
portable, minimizing panic. These machines are absolutely
critical for supporting clients, particulary in remote harsh
locations where no internet exist.

James





-- 
gentoo-user@g.o mailing list