[CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

Wed Jan 4 18:52:35 UTC 2017
Locane <locane at gmail.com>

Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff
through organic interactions like this.

Still though - someone manages the default repositories - so my question
is, who decides when a package gets an update from whatever CentOS ships
with default to a newer version?  How does that process take place, and,
can I affect it by adding microcode_ctl-2.1-18 ?

On Wed, Jan 4, 2017 at 10:00 AM, Paul Heinlein <heinlein at madboa.com> wrote:

> On Wed, 4 Jan 2017, Locane wrote:
> My questions are, who decides what packages are current for CentOS when I
>> "yum upgrade"?
> That's determined by the repositories defined and enabled in /etc/yum.conf
> and /etc/yum.repos.d/*.repo. To see the repositories enabled by your
> system, ask yum:
> yum repolist
> Each repository maintains a different set of packages. For any given
> package, order is determined by
> epoch > version > release
> To see those values for the packages installed on your system:
> rpm -qa --qf '%{name}\t\t%{epoch}\t%{version}\t%{release}\n' | sort
> Epoch is essentially a hack that can override a change in a package's
> version numbering. Most packages don't have an epoch number, but check out
> the epochs on bind-libs and (32!) and dhclient (12).
> So for each package name, the package with the highest
> epoch:version:release is "current." That allows a package in the updates
> repository to be installed over one currently installed on your system.
> --
> Paul Heinlein <> heinlein at madboa.com <> http://www.madboa.com/
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos