On Fri, 2013-03-29 at 15:22 +0200, Andreas K. wrote:
On 29-03-2013 14:59, Stephen Harris wrote:
On Fri, Mar 29, 2013 at 02:54:58PM +0200, Andreas K. wrote:
baseurl=ftp://yum.xx.xx.xx.xx/pub/linux/centos/$releasever/os/$basearch/ Is there a way to force a 6.3 machine to remain at 6.3 until a human being decides that is is time to do so?
Change releasever to 6.3 for base and updates and any other repo that might refer to it.
thanks for replying. I was hoping ot a more dynamic approach though since the number of affected machines is in excess of 150.
If you're dealing with that number of machines you may wish to consider setting up your own internal repo. Then you can sync your repo to the mirrors on your schedule, move to a later version on your schedule, and so on.
For example simply changing the $releasever to 6.3 and then to 6.4 and then to 6.5 every time a new version come along is not practical. Looking into the 'man yum.conf' I find that
$releasever This will be replaced with the value of the version of the package listed in distroverpkg. This defaults to the version of ‘redhat-release’ package.
distroverpkg The package used by yum to determine the "version" of the distribution. This can be any installed package. Default is ‘redhat-release’. You can see what provides this manually by using: "yum whatprovides redhat-release".
Doing
[root@cs6979 yum.repos.d]# yum whatprovides redhat-release ................. centos-release-6-4.el6.centos.10.x86_64 : CentOS release file Repo : CS-base Matched from: Other : redhat-release
centos-release-6-3.el6.centos.9.x86_64 : CentOS release file Repo : installed Matched from: Other : Provides-match: redhat-release
So the installed package is version 6.3. Am I overlooking/misinterpreting something?
Andreas _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos