Re: yum updates on Enterprise Linux ES 3

James Harrison wrote:
> I would download all the RPM updates from Redhat then use Yum from a local
> trusted machine.... 
> 
> Do periodical downloads using up2date from one machine in your organisation
> and dont delete the RPMS when they are installed (or just download them). 
> Save the RPMS to disk.
> 
> On this machine set up an nfs or http server locally then get your machines to
>  use yum to look at the downloaded RPMS. 
> 
> This way you know your RPMS are wont contain 'unwanted' software - only RPMS
> from Redhat.
> 
> This is the way I do it.

I also do it that way.

It saves the long download times via up2date for each individual server.

I use one master server which gets its fresh rpms via up2date (it has to 
be configured in such a way that it subscribes to the superset of all 
installed packages which one of the other server's might want).

After up2date, I run yum-arch on the rpm repository, to update the yum 
database.

Then, on the other servers, 'yum update' will update these very quickly.
After running 'yum update', I run 'up2date -p' to informa RHN about the 
new update status of each individual server, so that RHN does not
display them as needing updates.

--
Taroon-beta-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/taroon-beta-list