At 01:33 PM 2/20/2004, Hamilton Andrew wrote: >This solution may or may not work for you depending on what you want to do, but it may give you some other ideas. I do something like this because I have servers that don't ever connect to the internet and they have to updated as well. > >I have up2date configured to save the rpms after the install, I do an up2date -u via a cronjob, which works just fine. I then have the job move the newly installed rpms into a repository that is then transferred into my interior nework. I then have jobs that update my interior hosts, and I never lift a finger. You might get some use out of that and you might not or as they say "your mileage may vary...". Yes, that's more or less what I do now. Except I used wget instead of up2date. The real questions is: How do we get RPMs without the use of up2date? Why do this? Because up2date is a functionally delinquent application. It is incomplete and inefficient. One can not download past or specific RPMs, or event all RPMs, for/from a given channel. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
