| 1 |
On Thu, 13 Oct 2005 12:52:40 +0000 (UTC), James wrote: |
| 2 |
|
| 3 |
> I need to keep 2 portables synchronzied, particularly the /home/* files |
| 4 |
> and the various ebuilds that are installed need to be the same. |
| 5 |
|
| 6 |
> To Sychronize the /home/ files, I found unison. Any commnents |
| 7 |
> or other recommendations? |
| 8 |
|
| 9 |
I'd go with Unison, it's ideal for this sort of thing. |
| 10 |
|
| 11 |
> AS far as keeping the installed packages /ebuilds/ concurrent, |
| 12 |
> in some sort of semi-automated method, I'd settle for a script |
| 13 |
> I could run that would check the installed packages, on both |
| 14 |
> portablesand give a list of packages on the one that are not |
| 15 |
> ont he second machine. Kind of like a 'diff for ebuilds' that |
| 16 |
> would list the missing packages on the second portable. |
| 17 |
|
| 18 |
Is the first portable always updated first? If so, I'd add buildpkg to |
| 19 |
FEATURES in /etc/make.conf and make PKGDIR a directory accessible to |
| 20 |
both, possibly via NFS. Then, provided your USE and CFLAGS are the same |
| 21 |
(running the same make.conf on both would be easiest) to can synchronise |
| 22 |
the second box with the first by copying over /var/lib/portage/world and |
| 23 |
doing "emerge -uavDNk world". |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Neil Bothwick |
| 28 |
|
| 29 |
There is so much sand in Northern Africa that if it were spread out it |
| 30 |
would completely cover the Sahara Desert. |
Archives