search for: cent6u5

Displaying 5 results from an estimated 5 matches for "cent6u5".

Did you mean: cent5
2016 Jun 15
2
Pulling in broadwell support for cent6u5
Hello, all. Hope all is well Is it possible to install kernel and support files from 6u7 into a base 6u5 image to achieve full broadwell support in 6u5? We are "locked", clearly not fully since willing to up jump kernels, on 6u5. Thanks for any and all help
2016 Jun 15
0
Pulling in broadwell support for cent6u5
On 6/15/2016 2:48 PM, jsl6uy js16uy wrote: > Hello, all. Hope all is well > Is it possible to install kernel and support files from 6u7 into a base 6u5 > image to achieve full broadwell support in 6u5? > We are "locked", clearly not fully since willing to up jump kernels, on 6u5. "Locked", meaning you're running a ~3 old OS with no security or bugfix updates?
2016 Jun 19
1
Pulling in broadwell support for cent6u5
On 16/06/16 13:18, Johnny Hughes wrote: > > .. the actual definition of a > 'CRITICAL' update from Red Hat's perspective is: > > "This rating is given to flaws that could be easily*exploited by a remote unauthenticated attacker and lead to system > compromise (arbitrary code execution) without requiring user interaction*. These are the types > of
2016 Jun 16
0
Pulling in broadwell support for cent6u5
On 06/15/2016 05:10 PM, jsl6uy js16uy wrote: > Thanks much for the the reply! > Some sec updates/bug fixes have been applied thru the run of 6u5 and after, > but yes, still firmly in 6u5 land. Guess will have to test. > Broadwell cpus do run in the OS, but "6u5" is stated as not supporting > 26XXv4 chipsets. > Theoretically, it should be possible to run the latest
2016 Jun 15
4
Pulling in broadwell support for cent6u5
Thanks much for the the reply! Some sec updates/bug fixes have been applied thru the run of 6u5 and after, but yes, still firmly in 6u5 land. Guess will have to test. Broadwell cpus do run in the OS, but "6u5" is stated as not supporting 26XXv4 chipsets. regards On Wed, Jun 15, 2016 at 4:56 PM, John R Pierce <pierce at hogranch.com> wrote: > On 6/15/2016 2:48 PM, jsl6uy