-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have never tried something similar to this, but if you added any packages installed on the clients manually (or through some automated script) to the world file, after backing up the original and remembering to replace it when you want to do an update to the server. Then the 'emerge sync && emerge - -fud' should retreive all the files needed by all clients, no?
Paul. On Tuesday 23 Sep 2003 7:18 pm, Michael Schreckenbauer wrote: > Am Dienstag, 23. September 2003 18:46 schrieb Stroller: > > > I feel unhappy with automatic system updates. Should etc-update be ... > > systems - it only updates the local portage database & fetches the > > updates you require. It would, I would think, be quite easy to unshare > > the NFS export before getting the files, and reshare it afterwards, as > > part of the cron job. If this is done at 4am, then it is likely to > > cause little interruption to service in most environments. > > Besides I share your opinion, that shell-scripting is an adequate way of > cleaning distfiles, I must admit, that a cron-job, which calls emerge sync > && emerge -fud world only makes sense on a shared .../distfiles, if and > only if all machines sharing this, have the same packages installed. Given > I have a server w/o X and such and some desktop machines naturally with > this things. The share resides on the server, because this is the only > machine 24/7 up. How could an update of X, KDE etc happen and use already > downloaded files? When the desktops call emerge -ud world parallel, > wouldn't that cause problems? Am I missing something? I'd love to do it > this way, but I found no workaround for this problem yet. > > > Stroller. > > -- > > [EMAIL PROTECTED] mailing list > > Michael > > > -- > [EMAIL PROTECTED] mailing list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/cKfnB7nyD0FFN/MRArPdAJ9w28fy0x/L6aon6zrCgpWD9lGOJQCg3tz2 ZD5+1HlWuXO7nRuooUZANu8= =C1wo -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
