similar to: CentOS-announce Digest, Vol 178, Issue 2

I have a question to this update: Is the Kernel full open source? So i can review the kernel updates ?? I want to know the exact changes- like a merged "change paper", to show the differences clearly. Is this possible for Kernel updates? Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Saturday, 7. December 2019 07:00, <centos-announce-request at

CentOS Errata and Bugfix Advisory 2019:4106 Upstream details at : https://access.redhat.com/errata/RHBA-2019:4106 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 7c0f528358d229f5d8a4943732c64c291eb4d622282a67211267f9848771e739 bpftool-3.10.0-1062.9.1.el7.x86_64.rpm

CentOS Errata and Security Advisory 2019:4024 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:4024 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e3e9919525fe486bdd22e798d6ca8111312381f94fd884f2954496ec730d2ee1 SDL-1.2.15-15.el7_7.i686.rpm

On 1/22/20 3:57 PM, Gary Stainburn wrote: > I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated > > The log below shows: > > [root at vps2 ~]# yum history info 22 > Loaded plugins:

I have a VPS running C7. I ran a 'yum update' which included a kernel update. The yum update wasn't a total success because mariadb updates failed. However everything else appeared to work. However, when I rebooted the server it did not restart. I have managed to get the ISP's support desk to boot the server by selecting the previous kernel, and I now have access to my box again.

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Note, first of all I haven't actually updated, I'm just running "yum update" to see what conflicts, if any, I get so I can be prepared when the final 7.7 release happens. I've traditionally used the nvidia packages from elrepo, but recently enabled rpmfusion (back when I started using 7.x, I disabled rpmfusion because it took them a looooong time to get a EL7 repository up).

On Sat, Sep 14, 2019 at 07:20:35PM +0100, Phil Perry wrote: > On 14/09/2019 19:06, Fred Smith wrote: > >Note, first of all I haven't actually updated, I'm just running "yum update" > >to see what conflicts, if any, I get so I can be prepared when the final > >7.7 release happens. > > > >I've traditionally used the nvidia packages from elrepo,

I was in the middle of a yum update on physical box over teh weekend and power died. Ssytem came pack up. But now when I run yum-complete-transaction I get all kinds of errors (these are just the last 4, there are many) systemtap-runtime-4.0-10.el7_7.x86_64 has installed conflicts systemtap-devel < ('0', '4.0', '10.el7_7'): systemtap-devel-4.0-9.el7.x86_64

On 25/08/2019 02:28, Gregory P. Ennis wrote: > > On Sat, Aug 24, 2019 at 3:21 PM Ian Mortimer <i.mortimer at uq.edu.au> wrote: >> >> On Sat, 24 Aug 2019, Gregory P. Ennis wrote: >> >>> On August 2, my desktop unit updated with >>> kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 >>> which broke yum having a multiple of dependencies not being

On Sat, Aug 24, 2019 at 3:21 PM Ian Mortimer <i.mortimer at uq.edu.au> wrote: > > On Sat, 24 Aug 2019, Gregory P. Ennis wrote: > > > On August 2, my desktop unit updated with > > kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 > > which broke yum having a multiple of dependencies not being present. > > The latest from elrepo -

On 25/08/2019 15:50, Gregory P. Ennis wrote: > > On 25/08/2019 02:28, Gregory P. Ennis wrote: >> >> On Sat, Aug 24, 2019 at 3:21 PM Ian Mortimer <i.mortimer at uq.edu.au> wrote: >>> >>> On Sat, 24 Aug 2019, Gregory P. Ennis wrote: >>> >>>> On August 2, my desktop unit updated with >>>>

I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated The log below shows: [root at vps2 ~]# yum history info 22 Loaded plugins: fastestmirror, langpacks Repository mariadb is listed more than once in

> On 1/22/20 3:57 PM, Gary Stainburn wrote: >> I have managed to find out what happened in the yum update and it turns >> out it was a mess. It looks like the server ran out of memory in the >> middle and things then started to fail. Any advice on how to recover >> from this would be greatly appreciated >> >> The log below shows: >> >> [root at

Hi list, today I tried to update my centos workstation (7.6.1810). My problem concerns kmod-nvidia update. Nvidia driver where installed by elrepo. During running yum update I get: kmod-nvidia.x86_64 430.40-2.el7_7.elrepo elrepo and I also get several statements like this: Errore: Pacchetto: kmod-nvidia-430.40-2.el7_7.elrepo.x86_64 (elrepo) Richiede:

Everyone, On August 2, my desktop unit updated with kmod-nvidia-430.40-1.el7_6.elrepo.x86_64nnn which broke yum having a multiple of dependencies not being present. I uninstall kmod- dvidia with the hopes that a fresh install would fix the provlem, but it did not. nvidia-detect returns : kmod-nvidia An Intel display controller was also detected I was hoping that this was a repository problem

I'm trying to figure out a puzzling thing that we are seeing with some recently joined or re-joined samba servers. Our linux servers are in a different DNS domain than our AD machines (nwra.com or cora.nwra.com vs ad.nwra.com for the AD machines). Generally when we've joined a machine to AD the DNS name recorded in AD is their regular linux FQDN. But a couple machines have ended up with

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Le 26/04/2020 ? 11:43, Nicolas Kovacs a ?crit?: > I investigated this some more. Here's what I found. > > Installed a vanilla CentOS 7 GNOME desktop. > > Activated EPEL and installed 389-ds. > > Launched the setup script for 389 DS. > > Works perfectly bot locally and from my remote workstation with ssh -X. After some more experimenting, I can confirm this is a

Joining member Centos 7.8 Linux server with 4.10.4-10.el7 or higher appears to ignore client FQDN when AD domain does not match client domain name.? For example Active Directory Domain is ad1.testdomain.com and the client member server FQDN is? testhost.clients.testdomain.com.? When joining the domain? DNSHostName attribute in AD shows testhost.ad1.testdomain.com when it should be