On Fri, 2010-09-17 at 13:06 -0700, Aaron Burt wrote: > On Wed, Sep 15, 2010 at 01:19:29PM -0700, website reader wrote: > > I would appreciate hearing from anyone who has built a network source > > repository server and upgrades their systems via a LAN, and does NOT > > rely upon online updates to speak directly to the client machine. > > I do that when I set up a net-install system. Usually, I set up a basic > install dir using an install CD, and then make a cache of remote network > repos using Squid, apt-cacher-ng or something similar. > > I highly recommend caching package repos.
Basic answer -- you can mirror just about any public repo with rsync. apt-mirror is an excellent tool for said purpose. If you do any custom repo, you'll need to rebuild the package database. the yum-arch or dpkg-scanpackages command can be helpful there. Both collect package headers. You can even apply such commands to packages downloaded on a single system, such as those in the /var/cache directory tree. Some distros have their own tools for custom repos and mirrors -- I think the Red Hat Proxy (and Satellite) servers costs a bit of money. Someone mentioned Cobbler, which I think is a free option. SUSE has Zenworks. Both SUSE and Red Hat have front-ends that allow update management from a custom repo. I gather that SUSE Zenworks can also be used for Windoze updates. I think Spacewalk is an open source option to Red Hat Network, but haven't tried it. On the Ubuntu side, I don't know if Landscape can be pointed to custom mirrors either. Thanks, Mike _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
