I have already 6 Centos machines here and it is getting strange having to pull down updates to each system.
Seems like I should set up one system to pull updates and then all other systems to point to it.
How?
Plus then I would want to add to this repository.
Say that a number of my systems use tomcat which is only available via rpm. I would like to be able to add it to my repository, and if even manually, to keep it current. This way, when I build a new system, after the build I would do a yum update (from my server), then a yum install of all of the extras that particular system needs.
On Mon, 2006-01-30 at 10:12, Robert Moskowitz wrote:
I have already 6 Centos machines here and it is getting strange having to pull down updates to each system.
Seems like I should set up one system to pull updates and then all other systems to point to it.
You can make this more reasonable by simply pointing all of them to a common squid proxy that has the maximum_object_size bumped suitably high. This is low-maintenance but doesn't protect against the chance of the remote repository being changed between runs when you expect all your machines to get the same updates.
Plus then I would want to add to this repository.
Or you can add a separate one.
On 1/30/06, Robert Moskowitz rgm@htt-consult.com wrote:
I have already 6 Centos machines here and it is getting strange having to pull down updates to each system.
Seems like I should set up one system to pull updates and then all other systems to point to it.
How?
Plus then I would want to add to this repository.
Say that a number of my systems use tomcat which is only available via rpm. I would like to be able to add it to my repository, and if even manually, to keep it current. This way, when I build a new system, after the build I would do a yum update (from my server), then a yum install of all of the extras that particular system needs.
Yam, available from DAG, would get you started faily easily increating an internal repository for yourself. I believe that there is a createrepo or repobuild for creating your customized repository for self created rpms or rpms that do nat reside in any repositiry.
-- Leonard Isham, CISSP Ostendo non ostento.
On Mon, 30 Jan 2006, Robert Moskowitz wrote:
I have already 6 Centos machines here and it is getting strange having to pull down updates to each system.
Seems like I should set up one system to pull updates and then all other systems to point to it.
How?
Plus then I would want to add to this repository.
Say that a number of my systems use tomcat which is only available via rpm. I would like to be able to add it to my repository, and if even manually, to keep it current. This way, when I build a new system, after the build I would do a yum update (from my server), then a yum install of all of the extras that particular system needs.
Use yam to maintain your local repositories. Once you get started with YAM you will see that you can create you own repository for custom packages. You can also define your own groupsets which will download packages from your custom repository
In order to have a custom repostory you will then need to edit /etc/yum.r/myrepo.repo
-
Leonard Isham -
Les Mikesell -
Robert Moskowitz -
Robin Mordasiewicz