951965 wrote:Nope. The base repository is what ships on the DVD for each update release. There is also a patch repository for each update release which are the patches that were published after the update was released but before the next update.
We have a set of machines running OL6 that we want to keep at the same update level. Is there a page that describes the differences between what is in ol6_ga_base vs. ol6_u1_base vs. xxx.
We have been using ol6_latest, but that has lead to having inconsistent rpm versions in a few cases, which causes us issues. So we would like to stick to a specific update, and then update everything at ones, but want to know what the differences between updates is.The difference is the point-release of each package. Note that major/minor versions do not change throughout the life of a major release. This the point of enterprise Linux distributions. The updates are bug fixes and/or security back ports only. In rare cases, new major versions are released, but are named specifically, i.e. in OL5, there are php and php53 RPMs, so you need to consciously upgrade from the original major/minor PHP release to 5.3
951965 wrote:Actually, your best bet is to setup a local yum server using http://www.oracle.com/technetwork/topics/linux/yum-repository-setup-085606.html and then lock the repository used by the downstream servers by sending your own .repo file during the kickstart. The yum server can then periodically update itself and when you've completed testing on a particular upstream repository, you can then release that to your downstream servers.
Okay, I think that answers my question. I think what we want to do then is enable something like ol6_u2_base (6.2) and maybe ol6_UEK_base, and stick with that until ol6_u3_base is available. At that time, pull down a new repo file, enable _u4, and yum upgrade everything at the same time.