Rahul Sundaram <sundaram@xxxxxxxxxxxxxxxxx> wrote: [...] > Have you looked at mrepo? http://dag.wieers.com/home-made/mrepo/ Interesting, but it doesn't look exactly like what was asked... I'd like to do the following: Net-installing machine #1 gets the stuff required for that install (only!) and caches it, from cache install machines #2 .. #30. Now update machine #1, cache updates (so they can be used to update #2 .. #30, or even for fresh installs of #31 .. #35). If machine #20 needs some extra package, get and cache that one. If some machine asks for a package, look if what is up to date and hand that over; if not, get the last version. Sort of local-net /var/cache/yum (with a bit smarter handling ;-). Sure, it'll need some smarts to figure out that a package is obsoleted by another (version) to free space, but this might be handled by hand. Disk space is inexpensive, international network access is limited and expensive here (and it is probably much worse elsewhere). And it is not fun downloading the same files 30 times, or mirroring 10 files that aren't used locally to get the one you'll install 30 times. -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
