Noticed C6 had a kernel update on Friday.
2.6.32-696.18.7.el6.x86_64
What is the flag in /proc/cpuinfo that indicates the KPTI patch for
Meltdown CVE-2017-5754 for C6?
Some distros are using "kaiser" some like Fedora are using "pti". Also
noticed some (like Fedora) are displaying "cpu_insecure"
On 08/01/18 10:22, Danny Smit wrote:
On Sat, Jan 6, 2018 at 2:27 PM, Phil Perry wrote:
I've just built and released 384.111 to the elrepo main repository, so it
should show up on the mirrors shortly.
As expected, the 384.111 also solves the problem in my case.
Thanks for
While installing the experemental kernel on a CentOS 7 PV the following
happened. After a reboot of the PV the kernel looks to be installed but
there is no option for booting it in grub. I attempted to run yum
reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but
still no
4.9.75-30 works in my dev environment for CentOS 6.
[root@devhost1 ~]# uname -a
Linux devhost1.servers.provps.com 4.9.75-30.el6.x86_64 #1 SMP Fri Jan 5
20:58:49 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
Shaun Reitan
NDCHost.com
-- Original Message --
From: "Johnny Hughes"
CentOS Errata and Bugfix Advisory 2018:0042
Upstream details at : https://access.redhat.com/errata/RHBA-2018:0042
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
CentOS Errata and Security Advisory 2018:0061 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2018:0061
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On 01/08/2018 12:38 AM, Akemi Yagi wrote:
> On Sun, Jan 7, 2018 at 12:07 PM, David Groep wrote:
>
>> Dear all,
>>
>> Maybe I'm the only one - so before filing it as a bug: it appears that
>> the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue
>> 0013763 "CentOS
On Sat, Jan 6, 2018 at 2:27 PM, Phil Perry wrote:
>
> I've just built and released 384.111 to the elrepo main repository, so it
> should show up on the mirrors shortly.
As expected, the 384.111 also solves the problem in my case.
Thanks for the support everyone.
Regards,
8 matches
Mail list logo