I haven't used RHN/up2date in quite a while, but these directions from
Carl Reynolds seem sensible:
http://linux.derkeiler.com/Mailing-Lists/RedHat/2005-08/0237.html
"Since you are using up2date, you could also run
up2date-config
--> Retrieval/Installation
check "After installation, keep binary packages on disk"
This will cause up2date to keep any rpms it downloads in your "Package
storage directory" (usually /var/spool/up2date).
You can then copy these to the other machines or tell them to look on
the machine you're running as the repository and update their own
systems from there. "
Randy
Paul Beltrani wrote:
We have a large number of Cent/RHEL systems which we maintain with
Cobbler, Puppet and YUM. For performance, security and control
reasons we maintain local mirrors of the package repositories. This
is extremely easy to do for CentOS. A simple "reposync" or "cobbler
reposync" in a cron job keeps our local repository up to date.
Unfortunately, there doesn't appear to be a simple way to do this for
our Red Hat systems.
I'm aware of RHN/up2date/Satellite, but these aren't appropriate in
this instance for several reasons which I will not waste time on here.
Does anyone have a suggestions how to do this? If I can't find
anything simple, we'll most likely fall back to just pulling down the
ISOs at every point release.
- Paul Beltrani
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa
