I'm doing a 4.0.4 -> 4.2.1 upgrade tonight. It is a 64 Bit machine. I was contemplating updating the kernel. Kernel is currently 2.6.18-194.8.1.el5 The patched kernel version is 2.6.18-194.11.4.el5 It doesn't seem like too big of a change, but I haven't tested anything at all with 2.6.18-194.11.4.el5. For all I know, it would blow up the HP Proliant management tools or something along those lines. I guess I will hold off patching the kernel until I can do a little testing.
On 9/22/2010 3:50 PM, Douglas Hubler wrote: > On Wed, Sep 22, 2010 at 4:18 PM, Tony Graziano > <tgrazi...@myitdepartment.net> wrote: >> Yeah. I think when they build the ISO it would be nice to have it already on >> there. In the meantime, it's nice to be able to do a base OS update without >> someone saying "that's not supported" anymore. > ;) Yeah, the thought of saying "sipXecs is only compatible w/security > vulnerable releases" was top on my list to address. Those that stood > thru the stunnel fiasco on early 4.2.1 releases, this is fruit of our > labours! > > FYI: We can build off a new CentOS ISO easily so if CentOS spins a new > ISO we can get it. I have not implemented the ability to build an > sipXecs ISO from updates at any given moment from CentOS. The sipXiso > project has all the scripts if anyone wanted to add this option > > http://github.com/dhubler/sipxiso > > Like Tony said, nice if it was up-to-date, but quick yum update after > system install should resolve that. > > Thanks for the heads up Matthew > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
