-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-05-05 23:04, I wrote:
On 2010-05-05 20:24, j debert wrote:
...
Has anyone using 11.2 successfully tried to copy the zypper cache directory from one box to another? Does anyone know whether or not the existing files will be overwritten or deleted?
I intend to try that, but I haven't done so yet. My intention is to export the directory via nfs on one machine, and use it on another. Perhaps somebody has done it and documented the process? :-?
Well, it works. I have tried two methods, both work (in oS 11.2) The first point to notice is where are the packages stored; they are under a directory per repo, named as the "alias" name listed by "zypper lr" bellow /var/cache/zypp/packages/. Interestingly, if we change the "alias" name, the old directory is left alone, and a new one is created, the moment some package is downloaded. Ah, each repo we want to share has to be marked in zypper to "keep downloaded packages". Or change the default for all of them. Well, one procedure is keeping in sync the equivalent directory on both computers. I like "unison" for this. For example, I can run 'you' on the laptop, and after it finishes run 'unison' to sync /var/cache/zypp/packages/updates in the laptop to /var/cache/zypp/packages/repo-updates in the server, then run 'you' in the server (and 'unison' again). I can do the update in any machine first, and I don't need both machines running, not even interconnected. If needed, I could update the machines independently, and then sync them the day I'm back on the same network. It is more flexible. The disadvantage is that we waste storage, we keep two copies - or more if we have several computers. Another procedure is to export /var/cache/zypp/packages/ in the server (via nfs), and import it in the other machines, as /var/cache/zypp/packages_nfs/ (for example). As it is probable that you don't have the same names on both sides for all repos, that's why I import the server dir with a different name, then I symlink each repo, like: /var/cache/zypp/packages/updates --> /var/cache/zypp/packages_nfs/repo-updates This method saves storage space, doesn't need to run a unison process, but it requires the server to be running each time we run an update in any machine. And I think that we can not update two machines simultaneously, in case they try to download and write the same file to the server. And then, of course, there is the other method described in "http://www.3111skyline.com/linux/openSuSE-LocalUpdate.php", which is more general (and preferable for a group of computers). - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkvjb3wACgkQU92UU+smfQW7ZwCghxQNqROCeWXJzPPmHwphL8rL EzcAn1oe95FjpK7nlWe+nBzpE/hYsPDp =lbyc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org