-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-07-13 at 10:22 +0100, Kevin Donnelly wrote:
It seems like this would be a sensible addition to SUSE for those of us with multiple machines, (applying to virtual ones too.)
I agree entirely. I think it's weird that something like this, which would be really handy in a small office setup, for instance, is not a YaST module - it's almost as if people are assuming that you will either have a lonely Linux server on you LAN, or an enterprise-level 800-desk setup, but nothing in between.
Me too
If you are using Smart, one thing you could do is set it not to remove packages after download: smart config --set remove-packages=false and then share that PC's /var/lib/smart/packages over NFS. Then, on the other PCs, symlink their /var/lib/smart/packages dirs to that NFS share. Everything downloaded by any PC will then be in the source PC's /var/lib/smart/packages dir, and any package slated for update on a PC will be fetched from there if it exists, rather than being downloaded.
That reminds me. Previously, in 9.3, all updates were locally stored in "/var/lib/YaST2/you/mnt/i386/update/9.3", but in 10.1 I can't find where they are, that directory tree no longer exists. Where are patches stored now? The trick you mention for smart should be possible with yast, too. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEti5JtTMYHG2NR9URAthvAJ9k0qZq+gXhxz3XHjcCFe/iz+W2qACdEBNJ aKa0sregTvkFUXYoxRHANr4= =RTdA -----END PGP SIGNATURE----- -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com