Discuss

discuss@lists.centos.org

8 participants
34745 discussions

CentOS-announce Digest, Vol 197, Issue 1
by centos-announce-request＠centos.org 10 Aug '21

10 Aug '21

Send CentOS-announce mailing list submissions to centos-announce(a)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(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2021:1002 Important CentOS 7 flatpak Security Update (Johnny Hughes) 2. CESA-2021:3028 Important CentOS 7 microcode_ctl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 9 Aug 2021 15:29:20 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2021:1002 Important CentOS 7 flatpak Security Update Message-ID: <20210809152920.GA13355(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2021:1002 Important Upstream details at : https://access.redhat.com/errata/RHSA-2021:1002 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ac621916b414525cdb8e9a02b622a0b85c0f539979311abe60541cc0da534032 flatpak-1.0.9-11.el7_9.x86_64.rpm aeadded2fd899332eca7c3d0d69c10f06ba09b988bbb0be751dfc6ea05b1a753 flatpak-builder-1.0.0-11.el7_9.x86_64.rpm 1979501bae62e6070c0c6037b5547a69c4342485df1f9dd821ad18a174b0bd48 flatpak-devel-1.0.9-11.el7_9.x86_64.rpm e251fe0d7ffbb8b51c6644310756c5ea0a0ea8d5282cb0ecda819c8ff161dfec flatpak-libs-1.0.9-11.el7_9.x86_64.rpm Source: b370bbea447786abdcf03a57a462ba72d2fa235bd255bcdc74be873e55b25424 flatpak-1.0.9-11.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 9 Aug 2021 15:29:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2021:3028 Important CentOS 7 microcode_ctl Security Update Message-ID: <20210809152953.GA13461(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2021:3028 Important Upstream details at : https://access.redhat.com/errata/RHSA-2021:3028 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 68b647f3d90f5828c04a513b4561ba0866363b42452fbf73668418e2faa06983 microcode_ctl-2.1-73.11.el7_9.x86_64.rpm Source: e53891c0f92e021a87e8bda5e3ec6b66e6b05ca2c4eed2267de314c906cc7623 microcode_ctl-2.1-73.11.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 197, Issue 1 ***********************************************

1 0

Freeipa sssd service
by Gokan Atmaca 10 Aug '21

10 Aug '21

Hello I started using freeipa. Users I have given "SUDO" right cannot use this right after logging out and logging in. For the solution, I need to restart the "SSSD" service. How can I solve this? Thanks.

2 2

centos 8 stream / last yum update / VirtualBox 6.1.26
by Mathy Froeyen 06 Aug '21

06 Aug '21

Hi all Till this morning, I ran Windows 10 client on VirtualBox 6.1.24 on host Centos 8 stream kernel 4.18.0-315.el8 without problem (desktop). I took the risk to do a "yum update" and as well as the kernel as the VirtualBox were updated: kernel going from 4.18.0-315.el8 to 4.18.0-326.el8 VirtualBox going from 6.1.24 to 6.1.26 But yum complained already : ... Installing: Package Arch Version Repository Size ================================================================================ VirtualBox-6.1 x86_64 6.1.26_145957_el8-1 virtualbox 86 M ... Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : SDL-1.2.15-39.el8.x86_64 1/2 Running scriptlet: SDL-1.2.15-39.el8.x86_64 1/2 Running scriptlet: VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 2/2 Installing : VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 2/2 Running scriptlet: VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 2/2 Creating group 'vboxusers'. VM users must be member of that group! depmod: ERROR: fstatat(4, nvidia-drm.ko.xz): No such file or directory depmod: ERROR: fstatat(4, nvidia-modeset.ko.xz): No such file or directory depmod: ERROR: fstatat(4, nvidia-peermem.ko.xz): No such file or directory depmod: ERROR: fstatat(4, nvidia-uvm.ko.xz): No such file or directory depmod: ERROR: fstatat(4, nvidia.ko.xz): No such file or directory Verifying : SDL-1.2.15-39.el8.x86_64 1/2 Verifying : VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 2/2 Installed products updated. Installed: SDL-1.2.15-39.el8.x86_64 VirtualBox-6.1-6.1.26_145957_el8-1.x86_64 Complete! Vbox did not start my Windows 10 when I tried. I also tried to install VirtualBox 6.0 and 5.2 with the same kind of error in yum. I rebooted then the computer and started a previous kernel 4.18.0-310.el8 and reinstalled Virtualbox 6.1.26 now without those errors and it runs smooth as before. (Kernel 315 had the same vbox errors.) However, when I went back to kernel 4.18.0-326 and tried starting there VirtualBox 6.1.26 again, he complained with : ... Failed to open a session for the virtual machine Windows10. Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing '/sbin/vboxconfig' as root. ... (I tried that "/sbin/vboxconfig" but that tells me nonsense about registering because of EFI secure boot, but I did not change anything in the BIOS.) or there is some conflict between the last kernels and VirtualBox? cheers mathy

1 0

Transition test report going from CentOS8 to Debian 10.
by Lamar Owen 06 Aug '21

06 Aug '21

Sorry for the length.... I'm posting this here since this particular transition has been mentioned on-list as one possibility for a path forward for current CentOS Linux users. AlmaLinux, the Developer Subscription RHEL, Rocky, CentOS Stream, Springdale, upgrading to full RHEL; all these are also possibilities, too, and all have different strengths and weaknesses. The transition to Debian has a lot of strengths, including a long track-record of support (even if the support time for a particular release is shorter), a fully-open development model with no 'corporate overlord' that I know of, a large set of supported packages, and a huge community of developers and users. For the CentOS user the main weakness is having to learn a few areas of difference in the way the system is setup and maintained; of course, if a ten-year 'stable' timeframe is really that important to you the lack of that is also a weakness. So, last week I transitioned, as a test of sorts, my working CentOS 8 main laptop to Debian 10. I kept a complete backup of the C8 install should I wish to go back to it, and installed Buster to a new mSATA SSD, but ported the two SATA drives (Dell Precision M6700 - has an mSATA slot plus two SATA bays) straight over after making full backups. I posted a pretty complete rundown on the scientific linux users mailing list, so I won't recap it all here. The bottom line was the the transition was not any more difficult, really, than moving from CentOS 7 to CentOS 8. The software versions in Buster are pretty close to what is in CentOS 8, although I have yet to need any third-party repository (PPA) for anything I've needed to install. All the packages I have worked with so far have worked fine with a little bit of massaging. These include commercial (and costly) software such as Harrison Consoles' Mixbus32C, Qoppa's PDFStudio2019 Professional, and others. So if you were to decide that this is the route for you to take, it does work and I found it to be not nearly as hard as I had thought it might be. If you install GNOME 3 you get GNOME 3; it feels pretty much the same as a non-Classic CentOS GNOME 3, just with a different set of extensions installed by default. That's on the workstation. On the server side, I'm evaluating Proxmox for the virtualization solution, and so far I'm finding it to be a pretty easy migration. I'm using the 'non-subscription' repository, so this is a no-cost option. Even getting the box registered to our EMC Clariion SAN was relatively easy; EMC provides the Unisphere Server Utility for Linux x64 in RPM form; the latest I have is "ServerUtil-Linux-64-x86-en_US-1.0.55.1.0044-1.x86_64.rpm" (which is fairly old, but I did say Clariion arrays, so they're pretty old, too). Debian has provided the 'alien' tool for some time; after installing alien, a simple 'alien -i ServerUtil-Linux-64-x86-en_US-1.0.55.1.0044-1.x86_64.rpm' installed the EMC RPM in the correct place. Proxmox already included everything that serverutilcli requires; on a plain Buster install I had to install dm-multipath and the device mapper libraries and tools before serverutilcli would find the arrays; but it ran just like it did on CentOS 8 (and 7). I haven't decided whether to stay on Debian or not; too early to tell. I have time to test and evaluate. My CentOS 7 installs aren't goin anywhere, though, at least until late 2023. And I've registered for a Developer subscription of RHEL so that I can properly evaluate that option, too. This is the beauty of open source: we have OPTIONS.

11 23

kernel command line
by Jerry Geis 05 Aug '21

05 Aug '21

I am trying to install on a NUC7C with 32G of eMMC showing up as /dev/sdb Is there a way I can tell the kernel boot line or command line to MASK /dev/sdb ? Make it look like it does not exist ? It has windows pre-installed - I dont want to mistake it. Thanks Jerry

2 2

virt-manager and windows quest
by Jerry Geis 05 Aug '21

05 Aug '21

I am trying to get a windows guest on CentOS 7.9 to have more than 800x600 display. I started the Windows client, I downloaded Virtio 0.1.196.iso, went to the Device Manager, Display, right clicked - updated the driver - installed the qxldod driver, Rebooted. The Device Manager shows RedHat QXL Controller but I still only get 800x600 ghosted on Display Settings. Properties - shows "Windows has stopped this device as it reported a problem (Code 43)". What do I do with that ? This is the same error I had with I first tried VirtIO 0.1.185.iso Thanks, Jerry

2 1

unable to connect to the guest VM instance running Ubuntu 18.04
by Kaushal Shriyan 05 Aug '21

05 Aug '21

Hi, #cat /etc/redhat-release CentOS Linux release 7.8.2003 (Core) #virt-install --version 1.5.0 #virt-install -n snipeitassetmanagementubuntu --ram 8096 --vcpus 2 --virt-type kvm --os-type linux --os-variant ubuntu18.04 --graphics none --location 'http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/' --extra-args "console=tty0 console=ttyS0,115200n8" --disk path=/linuxkvmguestosdisk/snipeitassetmanagementubuntu.img,size=30 I am unable to connect to the guest VM instance. Any clue and i look forward to hearing from you. Thanks in advance. Best Regards, Kaushal

1 1

Trying out CentOS Stream 9
by Thomas Stephen Lee 05 Aug '21

05 Aug '21

Hi, How do I go about installing CentOS Stream 9 daily build in a VirtualBox VM? --- Lee

1 0

hosts.deny, fail2ban etc.
by H 04 Aug '21

04 Aug '21

|Running CentOS 7. I was under the impression - seemingly mistaken - that by adding a rule to /etc/hosts.deny such as ALL: aaa.bbb.ccc.* would ban all attempts from that network segment to connect to the server, ie before fail2ban would (eventually) ban connection attempts. This, however, does not seem correct and I could use a pointer to correct my misunderstanding. How is hosts.deny used and what have I missed? Is it necessary to run: iptables -I INPUT -s aaa.bbb.ccc.0/24 -j DROP to drop incoming connection attempts from that subnet? Thank you! |

9 17

vinagre from Ubuntu to CentOS 7.9
by Jerry Geis 04 Aug '21

04 Aug '21

I am trying to use vinagre (vncviewer type program) from Ubuntu 20.04 going to CentOS 7.9. I get prompted for the password. I enter it - then it says Authentication failed. I can connect with this program to other windows and Ubuntu machines no problem. Just having issue with CentOS. I can use vncviewer from CentOS to centOS. What's up ? Thanks, Jerry

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss