On Fri, Mar 29, 2013 at 11:08 AM, <m.roth@xxxxxxxxx> wrote:
> Ron Loftin wrote:
> >
> > 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.
>
Configuration management. ex: puppet
> >
> > 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.
> <snip>
> Seconded.
> And in the repo, all you'd have to do is have a symlink of 6 -> 6.3.
>
An internal repo would suffice, but arguably not the simplest. But for
150+ machines the OP should have one.
>
> mark
>
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
--
---~~.~~---
Mike
// SilverTip257 //
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
