I have run a local repo for Centos updates for some time.
I suppose, at this point I could just delete the 5.3 update directory and rsync the 5.4 directory...
But how large is the 5.4 update directory?
Oh, just for i386, without /debug and is there anything else I should not include? For example for my FC11 update repo I also exclude drpms.
So it looks like it is a download of the OS tree, not the UPDATES tree.
Great, and how large will that be?
Robert Moskowitz wrote:
I have run a local repo for Centos updates for some time.
I suppose, at this point I could just delete the 5.3 update directory and rsync the 5.4 directory...
But how large is the 5.4 update directory?
Oh, just for i386, without /debug and is there anything else I should not include? For example for my FC11 update repo I also exclude drpms.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi Robert,
I have run a local repo for Centos updates for some time.
You actually bring up a good item here. I am starting to learn more and deploy CentOS. I should run a local repo too, save bandwidth, etc.
Do you have a tutorial for setting up a local repository? Can one store, say multiple versions , just in case?
Best, -Jason
ML wrote:
Hi Robert,
I have run a local repo for Centos updates for some time.
You actually bring up a good item here. I am starting to learn more and deploy CentOS. I should run a local repo too, save bandwidth, etc.
Do you have a tutorial for setting up a local repository? Can one store, say multiple versions , just in case?
I have never automated my process, and I have as many versions as I want to blow disk space on.
For the base OS, the script that is running right now is:
# cat basesync.sh #!/bin/sh rsync -avu rsync://mirrors.kernel.org/centos/5.4/os/i386/ \ --delete --exclude=debug/ /repos/centos/5.4/os/i386
For updates:
# cat updatesync.sh #!/bin/sh rsync -auv rsync://mirrors.kernel.org/centos/5.4/updates/i386/ \ --delete --exclude=debug/ /repos/centos/5.4/updates/i386
'Traditionally' I run the updates script whenever I see a Centos Annoucement of new rpms.
I have a symlink of /repos/centos to /var/www/html so I then setup my /etc/yum.repos.d/CentOS-Base.repo to have:
[base] name=CentOS-$releasever - Base baseurl=http://repo.htt-consult.com/centos/5.n/os/$basearch/
Where 5.n is the version I am running on that box. I also have a symlink of the current version to /repos/centos/5 so I can just use /centos/5/.... for the current version. I have to update that symlink today from 5.3 to 5.4...
Oh there is a similar line for [updates].
I recently deleted my repos for FC9 and rsynced the repos for FC11. There I have a bit more to exclude.
On a fresh install I boot into 'linux askmethod' off CD 1, and provide the URL for the base repo to install off my local repo which is faster than flipping through 6 CDs (and more reliable). I suspect it would even be faster than the 1 DVD, if I had servers here with DVD drives on them!
On Sun, 2009-10-25 at 21:08 -0700, ML wrote:
Hi Robert,
I have run a local repo for Centos updates for some time.
You actually bring up a good item here. I am starting to learn more and deploy CentOS. I should run a local repo too, save bandwidth, etc.
Do you have a tutorial for setting up a local repository? Can one store, say multiple versions , just in case?
The Wiki is (or at least should be) your friend:
http://wiki.centos.org/HowTos/CreateLocalMirror
and for your locally built packags
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
ML wrote:
You actually bring up a good item here. I am starting to learn more and deploy CentOS. I should run a local repo too, save bandwidth, etc.
I use mrepo. It automates creating and updating the repo for you.
http://dag.wieers.com/home-made/mrepo/
Bowie Bailey wrote:
ML wrote:
You actually bring up a good item here. I am starting to learn more and deploy CentOS. I should run a local repo too, save bandwidth, etc.
I use mrepo. It automates creating and updating the repo for you.
The thing is, that rsync is all you need in a crontab. The setup is rather simple at first and the rsync script is straightforward.
mrepo is for grander things, IMHO.
From: Robert Moskowitz rgm@htt-consult.com
I have run a local repo for Centos updates for some time. I suppose, at this point I could just delete the 5.3 update directory and rsync the 5.4 directory... But how large is the 5.4 update directory?
I mirror both os and updates, since when you upgrade, you need os rpms too... So far, updates is small.
3.8G /IOL/CENTOS_repo/centos/5/os/i386 4.3G /IOL/CENTOS_repo/centos/5/os/x86_64 92K /IOL/CENTOS_repo/centos/5/updates/i386 96K /IOL/CENTOS_repo/centos/5/updates/x86_64 8.1G total
JD
John Doe wrote:
From: Robert Moskowitz rgm@htt-consult.com
I have run a local repo for Centos updates for some time. I suppose, at this point I could just delete the 5.3 update directory and rsync the 5.4 directory... But how large is the 5.4 update directory?
I mirror both os and updates, since when you upgrade, you need os rpms too... So far, updates is small.
3.8G /IOL/CENTOS_repo/centos/5/os/i386 4.3G /IOL/CENTOS_repo/centos/5/os/x86_64 92K /IOL/CENTOS_repo/centos/5/updates/i386 96K /IOL/CENTOS_repo/centos/5/updates/x86_64 8.1G total
Thanks for the info. I only need the i386 part, and I see that updates/i386 is just a repo structure, no rpms yet. So the download of os/i386 is in process...
-
Bowie Bailey -
John Doe -
ML -
Phil Schaffner -
Robert Moskowitz