Hello Don't worry and about the best practice, don't put your server in a channel which receive all updates all days! :-), imagine a package with a problem and without a previews test, you can get trouble ... or better, you will get a trouble :-)))
Take care and tell me if I can help you! ______________ Atenciosamente Waldirio msn: [email protected] Skype: waldirio Site: www.waldirio.com.br Blog: blog.waldirio.com.br LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 PGP: www.waldirio.com.br/public.html On Fri, Nov 21, 2014 at 4:54 PM, Net Warrior <[email protected]> wrote: > Hi Waldirio, > > Yes, we have some applications that needs to be tested before going into > 6.6 Release just in case, I've read that lots of things have changed, so do > not want to make a mess!!! By now, I think I will stay with 6.5, and test > the application against 6.6 with a stand alone server with access to > intenet, then I have to review my repository configuration based on what I > was told on first place by Madey and decice if I want to be able to get > always to the latest releases whenerver they come out, or just to stick to > one in particular. > > Thanks for the advice, really appreciated. > Regards > > 2014-11-21 15:38 GMT-03:00 Waldirio Manhães Pinheiro <[email protected]>: > > Warrior, good afternoon >> >> You can proceed by 2 ways: >> >> 1. Create a repo/channel of major release, CentOS6 for example, and >> create a cloned channel, just to keep up to date when necessary, you can >> compare your freezed channel with base channel (channel which receive data >> daily) and add difference or what you really need. >> >> 2. Create a channel by version, 6.5, now with 6.6, if you don't have >> necessity do still in the version 6.5, you (admin) can create a new channel >> 6.6, create a new test machine and test your applications, if all of them >> works fine, you can just switch your machines from channel 6.5 to 6.6 and >> update. Pay attention, just after tests and ok from IT / Application team. >> >> Choose the best way for your environment and enjoy! >> >> Let me know if you need some more info. >> >> B'Regards >> >> ______________ >> Atenciosamente >> Waldirio >> msn: [email protected] >> Skype: waldirio >> Site: www.waldirio.com.br >> Blog: blog.waldirio.com.br >> LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 >> PGP: www.waldirio.com.br/public.html >> >> On Fri, Nov 21, 2014 at 3:28 PM, Net Warrior <[email protected]> >> wrote: >> >>> Thanks for the tip, very kind of you. >>> Regards >>> >>> 2014-11-21 13:04 GMT-03:00 Stuart Green <[email protected]>: >>> >>> >>>> If you just use the major release link's >>>> >>>> http://mirror.centos.org/centos/6/os/x86_64/ >>>> >>>> http://mirror.centos.org/centos/6/updates/x86_64/ >>>> >>>> >>>> You'll get the minor updates automatically as they are released. >>>> >>>> BR, >>>> Stuart >>>> >>>> On 21/11/2014 15:52, Net Warrior wrote: >>>> > Hi there community. >>>> > I'd like an advice or suggestion regarding repository configuration, >>>> so let >>>> > me tell you what my issue is. >>>> > I have a couple of repo configured, and one of them is a centos one, >>>> with >>>> > the following configuration: >>>> > >>>> > Centos 6.5 Main >>>> > http://mirror.centos.org/centos/6.5/os/x86_64/ >>>> > The updates: >>>> > http://mirror.centos.org/centos/6.5/updates/x86_64/ >>>> > >>>> > So far so good, now as all we know CentOS has a new Release 6.6, what >>>> I >>>> > notice is that I did not get any other update to the channel, so all >>>> my >>>> > clients will be stuck with 6.5. >>>> > >>>> > My question is, is it sane to configure the channel that way and >>>> create >>>> > another one for the 6.6 ? or should I configure the channel to >>>> > automatically update to 6.6, for example, I have a server for testing >>>> > purposes conected directly to internet, and when the new 6.6 was >>>> released >>>> > when I performed a yum update I was told there was a new release >>>> update, >>>> > so , how can I configure my channels to behave that way , if it the >>>> right >>>> > way to go or what it the best practice for this matter. >>>> > >>>> > Thank for your time and support. >>>> > Best regards. >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Spacewalk-list mailing list >>>> > [email protected] >>>> > https://www.redhat.com/mailman/listinfo/spacewalk-list >>>> > >>>> >>>> >>>> _______________________________________________ >>>> Spacewalk-list mailing list >>>> [email protected] >>>> https://www.redhat.com/mailman/listinfo/spacewalk-list >>>> >>> >>> >>> _______________________________________________ >>> Spacewalk-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/spacewalk-list >>> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
