[Gllug] Repository expansion approach
GLLUG at GetAroundToIt.co.uk
Fri Jul 16 05:23:31 UTC 2010
Can I 'seed' my 5.5 repo with the previous version's files and perhaps
save some rsync time/traffic; or is this is bad idea?
A bit of 'Friday finking' by a non-SysAdmin:
I have local repositories for CentOS 5.3 and 5.4. rsync is utilised to
pull down a copy from my closest CentOS 'mirror' site. Thereafter this
is fed into my LAN's Cobbler server. All local installs and updates run
from there; saving multiple update downloads, my systems don't have to
run yum-updatesd, ...
Now that CentOS 5.5 has been released, the repo/Cobbler server needs to
be expanded. Given that some files will not have changed between 5.4 and
5.5, if I were to rename my 5.4 directories to 5.5 (and update the rsync
command accordingly) might this save me some download traffic? (before
feeding the combination into Cobbler as "5.5")
Conversely, would the older version be a faulty foundation for the new
Anyone thought this one through, been-there-done-that?
Gllug mailing list - Gllug at gllug.org.uk
More information about the GLLUG