[CentOS-announce] CESA-2018:0122 Critical CentOS 7 firefox Security Update

CentOS Errata and Security Advisory 2018:0122 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:0122 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64:

[CentOS-announce] CESA-2018:0122 Critical CentOS 6 firefox Security Update

CentOS Errata and Security Advisory 2018:0122 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:0122 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386:

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

> Am 24.01.2018 um 22:22 schrieb Chris Adams : > > Once upon a time, Chris Murphy said: >> "We recommend that OEMs, cloud service providers, system >> manufacturers, software vendors and end users stop deployment of >> current versions." Current

[CentOS] In /etc/auto.master, why "+auto.master"?

Why is the line "+auto.master" present in the /etc/auto.master file? Does this not create a loop, and perhaps is the reason why, on every boot, I see the message, "automount[3260]: problem reading master map, maximum wait exceeded"? This is in an unmodified /etc/auto.master from

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

Once upon a time, Chris Murphy said: > "We recommend that OEMs, cloud service providers, system > manufacturers, software vendors and end users stop deployment of > current versions." Current versions of what? Microcode? Well, that's the only thing Intel provides for

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

Leroy Tennison wrote: > What's amazing to me is, after "Intel Inside - don't divide" (their 486 > debacle), they didn't learn and have a better plan for addressing these > kinds of things. > Or, as some of us back then referred to it, the RePentium chip (think again...) mark > - Original

Re: [CentOS] Centos´s way of handling mdadm

> Am 24.01.2018 um 20:37 schrieb Leon Fauster : > > >> Am 24.01.2018 um 19:17 schrieb hw : >> >> Hi, >> >> what´s the proposed way of handling mdadm in Centos 7? I did not get >> any notification when a disk in a RAID1 failed, and now that the

Re: [CentOS] Centos´s way of handling mdadm

> Am 24.01.2018 um 19:17 schrieb hw : > > Hi, > > what´s the proposed way of handling mdadm in Centos 7? I did not get > any notification when a disk in a RAID1 failed, and now that the > configuration has changed after resolving the problem, I might be > supposed to somehow

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

On Wed, January 24, 2018 12:38 pm, Leroy Tennison wrote: > What's amazing to me is, after "Intel Inside - don't divide" (their 486 > debacle), they didn't learn and have a better plan for addressing these > kinds of things. It probably would be fair to conclude that they didn't plan to address

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

What's amazing to me is, after "Intel Inside - don't divide" (their 486 debacle), they didn't learn and have a better plan for addressing these kinds of things. - Original Message - From: "Chris Murphy" To: "centos" Sent: Wednesday, January

[CentOS] Centos´s way of handling mdadm

Hi, what´s the proposed way of handling mdadm in Centos 7? I did not get any notification when a disk in a RAID1 failed, and now that the configuration has changed after resolving the problem, I might be supposed to somehow update /etc/mdadm.conf. Am I not supposed to be notified by default

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

On Tue, Jan 23, 2018 at 4:26 AM, Johnny Hughes wrote: > > Here are a couple of posts for our reading pleasure: > > Intel recommends not installing the microcode now: > http://intel.ly/2DsL9qz Except this doesn't mention microcode at all. I can't even tell WTF they're

Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation) packages making their way to centos-virt-xen-testing

> -Original Message- > From: CentOS-virt [mailto:centos-virt-boun...@centos.org] On Behalf Of > Johnny Hughes > Sent: Wednesday, January 24, 2018 6:39 AM > To: centos-virt@centos.org > Subject: Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation) > packages making their way to

[CentOS-virt] CentOS 7 AMI missing ENA support

Getting this API error trying to launch CentOS 7 (x86_64) - with Updates HVM AMI with AWS c5.large instance type in us-west-2: ==> amazon-ebs: Error launching source instance: InvalidParameterCombination: Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'c5.large'

Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation) packages making their way to centos-virt-xen-testing

On 01/24/2018 01:01 AM, Pasi Kärkkäinen wrote: > On Tue, Jan 23, 2018 at 06:20:39PM -0600, Kevin Stange wrote: >> On 01/23/2018 05:57 PM, Karl Johnson wrote: >>> >>> >>> On Tue, Jan 23, 2018 at 4:50 PM, Nathan March >> > wrote: >>> >>> Hi, >>> >>> >

Re: [CentOS] Unrar not extracting archive

On 01/23/2018 08:50 PM, Alexander Dalloz wrote: > Am 23.01.2018 um 20:23 schrieb H: >> I received a rar-archive, probably created on Win10, that I could not >> extract with unrar on CentOS 6. > > CentOS does not provide unrar. You must have it from a third party repository > and we don't know

Re: [CentOS] best centos server setup for graphics intensive kvm vms?

Yes -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Morgan Read" > To: "CentOS mailing list" > Sent: Tuesday, 23 January, 2018 23:30:57 > Subject: Re: [CentOS] best centos server setup for