On Wed, 2002-10-23 at 23:05, Joe Emenaker wrote: > Some of my coworkers want to dabble in grid computing, so they got themselves about >7 old PC's and they wanted to set them up. > > I put Debian on all of them, but I wanted to be able to keep them up-to-date without >having all 7 hit the package servers. Since they are all configured the same, I >figure, if one of them needs a new package, then they'll all need it. > > So, I got to thinking... why can't machine "A" do a normal upgrade and save all of >its .deb packages. Then, all of the other machines would have their sources.list file >pointed to machine "A" and they'd just hit *that* machine for their updates. > > I know that apt saves its packages in /var/cache/apt, so that's not a problem. The >problem, to me, is in generating the Packages and Release files. Is there an easy way >to do this? > > - Joe
I'd suspect that isn't a *great* idea - you'd need to regenerate the packages and release files after each upgrade of the primary machine. An alternative: use the same sources.list files, and export /var/cache/apt from the primary machine. When you run apt-get upgrade on each of the other machines, they will see the packages and release files for the various source servers as up-to-date, and all of the requested files as already downloaded, and proceed to install them from the lan - no need to worry about regenerating local files then. -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
