- Discuss - lists.centos.org

Table *** is marked as crashed and should be repaired
by Александр Кириллов 03 Dec '20

03 Dec '20

Hi, I've started migrating my sites to mariadb which is supposed to be a drop-in replacement of mysql. Both run on the same C6 box. DB folders were moved to a new location after both DB servers were stopped and properly upgraded. There were no reboots or power failures. Nevertheless I see these error messages in the logs: # cat /var/opt/rh/rh-mariadb102/log/mariadb/mariadb.log ... 2020-11-29 16:38:23 139882501732320 [Note] /opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: '10.2.22-MariaDB' socket: '/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock' port: 3307 MariaDB Server 2020-11-29 16:38:23 139882394105600 [Warning] Access denied for user 'UNKNOWN_MYSQL_USER'@'localhost' (using password: NO) 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table 'wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [ERROR] mysqld: Table 'wp_wc_customer_lookup' is marked as crashed and should be repaired 2020-11-29 16:39:37 139882394105600 [Warning] Checking table: './wordpress@002dstorefront/wp_wc_customer_lookup' ... 2020-11-29 17:16:17 140059421116384 [Note] /opt/rh/rh-mariadb102/root/usr/libexec/mysqld: ready for connections. Version: '10.2.22-MariaDB' socket: '/var/opt/rh/rh-mariadb102/lib/mysql/mysql.sock' port: 3307 MariaDB Server 2020-11-29 17:16:18 140059356550912 [Warning] Access denied for user 'UNKNOWN_MYSQL_USER'@'localhost' (using password: NO) 2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_options' is marked as crashed and should be repaired 2020-11-29 17:20:01 140059356550912 [ERROR] mysqld: Table 'wp_options' is marked as crashed and should be repaired 2020-11-29 17:20:01 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_options' 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_posts' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table 'wp_posts' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_posts' 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_actionscheduler_claims' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [ERROR] mysqld: Table 'wp_actionscheduler_claims' is marked as crashed and should be repaired 2020-11-29 17:20:02 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_actionscheduler_claims' 2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_usermeta' is marked as crashed and should be repaired 2020-11-29 17:22:28 140059356550912 [ERROR] mysqld: Table 'wp_usermeta' is marked as crashed and should be repaired 2020-11-29 17:22:28 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_usermeta' 2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356550912 [ERROR] mysqld: Table 'wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table './wordpress@002dstorefront/wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356247808 [ERROR] mysqld: Table 'wp_woocommerce_sessions' is marked as crashed and should be repaired 2020-11-29 17:22:31 140059356550912 [Warning] Checking table: './wordpress@002dstorefront/wp_woocommerce_sessions' ... Note that after the crashed table was repaired mariadb reported multiple crashed tables in the same DB after restart. Any pointers? Never had such problems with mysqld. Is mariadb reliable and stable at all? # cat /etc/centos-release CentOS release 6.10 (Final) # rpm -qa '*maria*' rh-mariadb102-mariadb-server-utils-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-common-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-server-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-config-10.2.22-1.el6.x86_64 rh-mariadb102-mariadb-errmsg-10.2.22-1.el6.x86_64 rh-mariadb102-runtime-3.0-5.el6.x86_64 TIA, AK

1 1

Thunderbird 78
by Gerhard Schneider 03 Dec '20

03 Dec '20

The upstream provider decided to remove OpenGPG support in its thunderbird-78 packages, see https://bugzilla.redhat.com/show_bug.cgi?id=1886962 https://bugzilla.redhat.com/show_bug.cgi?id=1886958 https://bugzilla.redhat.com/show_bug.cgi?id=1837512 recommending to either use Mozilla binaries, use Flatpak or switch to Evolution Is there any plan to provide thunderbird-78-full packages in e.g. EPEL, ELRepo or somewhere else (like firefox-esr in Ubuntu) or should we use Mozilla binaries? Thank you in advance! Gerhard Schneider -- Gerhard Schneider Institute of Lightweight Design and e-Mail: gs(a)ilsb.tuwien.ac.at Structural Biomechanics (E317) Tel.: +43 1 58801 31716 TU Wien / Vienna / Austria Fax: +43 1 58801 31799 A-1060 Wien, Gumpendorfer Straße 7 http://www.ilsb.tuwien.ac.at/~gs/

2 1

firewall-cmd - bug or bad design
by Jon LaBadie 03 Dec '20

03 Dec '20

In my firewall I use an ipset as a geographical blacklist. A single addresses can be entered into the blacklist using CIDR notation or not, i.e. 111.222.111.222/32 OR 111.222.111.222 while a block of IP addresses can be entered using CIDR notation: 111.222.111.0/24 Both the ipset and firewall-cmd commands have ways to ask if an address has already been entered into the blacklist. The basic syntax is ipset test <blacklist> <ip_addr> firewall-cmd --ipset=<blacklist> --query-entry=<ip_addr> With ipset I can test a single address using CIDR or not regardless of how it was entered. If the entry was a block of addresses, any address within the block is reported as "in the ipset". firewall-cmd responds differently. If I entered "111.222.111.222/32" (i.e. using CIDR) into the list, firewall-cmd reports the address as "NOT entered" if I query the simple form "111.222.111.222" even though they are the same single address. Conversely, if the original entry was simple, the CIDR form is reported as "NOT entered". With block entries like 111.222.111.0/24, any address within the block is reported as "NOT entered"! Only the actual string entered, 111.222.111.0/24, is considered "entered". I use these types of queries to decided whether an ip address is already being blocked. Clearly relying the firewall-cmd query would lead to unnecessary entries. What do you think, Should I consider this simply a poor design decision or a reportable "bug"? -- Jon H. LaBadie jcu(a)labadie.us

1 0

Reminder: CentOS 6 EOL on 30 November 2020
by Johnny Hughes 02 Dec '20

02 Dec '20

All, This is a friendly reminder. CentOS 6.10 will EOL at the end of November 2020. During the first week in December 2020, the 6.10 directory will move to vault.centos.org Packages will still be available at: http://vault.centos.org/centos/6.10/ However, once moved, there will be no more updates pushed to vault.centos.org. Therefore, security issues will no longer be fixed, etc. You should take the rest of the month to either move to a newer versoin of CentOS Linux ... or to procure Extended el6 support from Red Hat (EUS RHEL 6). Thanks, Johnny Hughes

3 2

[rdo][centos8][repos] CentOS8 RDO-USSURI repo missing openvswitch2.13
by Ruslanas Gžibovskis 02 Dec '20

02 Dec '20

Hi all, I have an issue, in CentOS8 repos for RDO. It is refering to openvswitch2.13 name, but in the repos I can see openvswitch packages with version in version field, looks like in dependency field it is missing dash (-) or smth... here is a paste of repos and error message [0]. Or any other way how this could be fixed? thanks. and packages I can see [1] here. [0] http://paste.openstack.org/show/xEalilL1rRJSDTzNCGt1/ [1] http://paste.openstack.org/show/VLWrNFpRLatwq5qXP2kD/ -- Ruslanas Gžibovskis +370 6030 7030

1 0

Firefox, C-7, and... reboot?
by mark 02 Dec '20

02 Dec '20

Last night, for the second or third time since I upgraded from C6 to c7 this summer, I did something on firefox - I think it was reload a page, and my system rebooted. Yes, I have a ton of tabs open. I see nothing suspicious in /var/log/messages, or in /var/log/dmesg.old. I saw a mention of boltd? I think, but nothing more. Has anyone else had this problem? mark

1 0

Problem upgrading from 8.0 to 8.1
by Michael Schwartzkopff 02 Dec '20

02 Dec '20

Hi, I want to upgrade from 8.0 to 8.1 but yum update does not work. Still 8.0 Probably the cause is that I compiled DRBD myself because it was not available for 8.0 when I set up the machine. Now yum update says: Error: Problem 1: cannot install the best update candidate for package drbd-pacemaker-9.11.0-1.el8.x86_64 - nothing provides pacemaker needed by drbd-pacemaker-9.13.1-1.el8.x86_64 Problem 2: cannot install both drbd-utils-9.13.1-1.el8.x86_64 and drbd-utils-9.11.0-1.el8.x86_64 - package drbd-heartbeat-9.11.0-1.el8.x86_64 requires drbd-utils = 9.11.0-1.el8, but none of the providers can be installed - cannot install the best update candidate for package drbd-utils-9.11.0-1.el8.x86_64 - problem with installed package drbd-heartbeat-9.11.0-1.el8.x86_64 Problem 3: cannot install both drbd-utils-9.13.1-1.el8.x86_64 and drbd-utils-9.11.0-1.el8.x86_64 - package drbd-pacemaker-9.11.0-1.el8.x86_64 requires drbd-utils = 9.11.0-1.el8, but none of the providers can be installed - package drbd-9.13.1-1.el8.x86_64 requires drbd-utils = 9.13.1, but none of the providers can be installed - problem with installed package drbd-pacemaker-9.11.0-1.el8.x86_64 - cannot install the best update candidate for package drbd-9.11.0-1.el8.x86_64 - nothing provides pacemaker needed by drbd-pacemaker-9.13.1-1.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) with --nobest yum update runs through without doing anything and I sill have kernel 4.18.0-80.11.2.el8_0.x86_64 Any ideas how to update my server? Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 1

CentOS 7, as a 6in4 server
by Walter H. 02 Dec '20

02 Dec '20

Hello, I have a VPS at a hoster where I got 3 /64 ipv6 prefixes/subnets, that are routed; one for the VPS itself - let us call this srvprefix one for the tunnel, only ::1 (server side) and ::2 (home side) are used - let us call this tunnelprefix and one for my network at home - let us call this homeprefix now I'm just in test state, a CentOS VM is the other end of the tunnel; (when the server runs well, my CentOS ZBOX will become the other end of the tunnel) at the server the eth0 device has serverprefix::1, the sit1 device has tunnelprefix::1 the routing is set with /etc/sysconfig/network-scripts/route6-sit1 tunnelprefix::2 dev sit1 homeprefix::/64 via tunnelprefix::2 dev sit1 in sysctl.conf these are set net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 now I have to do these ip -6 neigh add proxy homeprefix::1 dev eth0 ip -6 neigh add proxy homeprefix::### dev eth0 the question, can I do something to avoid these "ip -6 neigh ..."? if yes, what? and how? can the hoster do something? if yes, what? Thanks, Walter my ISP told me that he won't deploy IPv6 within the next 5 years;

2 3

Re: [CentOS] Reminder: CentOS 6 EOL on 30 November 2020
by Fabian Arrotin 02 Dec '20

02 Dec '20

On 30/11/2020 13:39, Fabian Arrotin wrote: > On 30/11/2020 11:18, Manuel Wolfshant wrote: >> On 11/30/20 10:25 AM, Fabian Arrotin wrote: >>> On 09/11/2020 14:24, Johnny Hughes wrote: >>>> All, >>>> >>>> This is a friendly reminder. >>>> >>>> CentOS 6.10 will EOL at the end of November 2020. >>>> >>>> During the first week in December 2020, the 6.10 directory will move to >>>> vault.centos.org >>>> >>>> Packages will still be available at: >>>> >>>> http://vault.centos.org/centos/6.10/ >>>> >>>> However, once moved, there will be no more updates pushed to >>>> vault.centos.org. Therefore, security issues will no longer be fixed, >>>> etc. >>>> >>>> You should take the rest of the month to either move to a newer versoin >>>> of CentOS Linux ... or to procure Extended el6 support from Red Hat (EUS >>>> RHEL 6). >>>> >>>> Thanks, >>>> Johnny Hughes >>>> >>> As announced multiple times (on list[s], twitter, glog.centos.org and >>> even https://c6eol.centos.org) , CentOs 6 is now EOL and so is being >>> retired from mirror network. >>> It's currently being moved to (capped and limited bandwidth) >>> vault.centos.org and will be removed from mirror.centos.org (and so >>> external mirrors in the next hours/days). >>> mirrorlist.centos.org will also (like we do for all >>> outdated/unmaintained and unsecured releases) start answering "invalid >>> release" >>> >>> Kind Regards, >> >> Just to let you all know that starting from today, mirrorlist.centos.org nodes answer "Invalid release/repo/arch combination" and also that content was removed from mirrors. Johnny pushed the last updates yesterday, that went out to external mirrors . These mirrors will also delete all that content so if your *really* need to find such content, https://vault.centos.org is the only way to to go, but due to reduced bandwidth, capacity, we encourage you to use one of the external mirrors listed on vault.centos.org, with probably more resources/bandwidth that we currently have. Some of these mirrors also continue to offer rsync access. Cheers, and time to have a drink and celebrate 10 years of CentOS 6 : you served us all well ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Upgrade OpenSSH version to the latest stable version on CentOS Linux release 7.9.2009 (Core).
by Kaushal Shriyan 01 Dec '20

01 Dec '20

Hi, I am running CentOS Linux release 7.9.2009 (Core). Is there a way to upgrade OpenSSH version openssh-7.4p1-21.el7.x86_64 to the latest stable version openssh-server 8.4 using yum repositories or rpm binaries? Best Regards, Kaushal

4 3

CentOS and mdadm
by Nicolas Kovacs 01 Dec '20

01 Dec '20

Hi, I'm regularly using software RAID for my CentOS storage servers, either with RAID 1 or RAID 6 depending on the number of disks. Here's two questions about mdadm I've always been wondering about. 1. I'm not sure about the --metadata option. Let's say I want to create a simple RAID 1 setup, I'm usually doing it like this: # mdadm --create /dev/md/boot --level=1 --raid-devices=2 \ --metadata=1.2 /dev/sda1 /dev/sdb1 If anyone can explain the exact meaning of --metadata, I'd be grateful. Oh, and is it OK to use --metadata=1.2 in CentOS 7.x and 8.x ? 2. I'm regularly encountering the mdadm --misc option in various tutorials on the Internet. I looked it up in mdadm's manpage, but it doesn't seem to be documented. Any idea what this option does ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 1

Physical position of swap partition on the disk
by Nicolas Kovacs 01 Dec '20

01 Dec '20

Hi, Here's a question to the fine-tuning gurus. Yesterday while installing a fresh CentOS server, I wondered how big of a deal the physical position of the swap partition on the disk is. Here's an example of a simple MBR partitioning scheme on a legacy BIOS machine with a 60 GB SSD: * /dev/sda1: 500 MB /boot ext2 * /dev/sda2: 4 GB swap * /dev/sda3: 55 GB / ext4 In the old (Slackware) days, I created the partitions manually using fdisk. Now when I do something similar in Anaconda, I have to reason in terms of mount points. So in a similar order I create the /boot partition, the swap partition and the root partition. What happens here is that Anaconda will always invert the root and swap partitions and put the swap partition at the end of the disk. So my setup looks like this: * /dev/sda1: 500 MB /boot ext2 * /dev/sda2: 55 GB / ext4 * /dev/sda3: 4 GB swap I'd be curious to know what's the reason behind this, and if this kind of configuration detail is really significant. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

5 5

Anaconda : MBR vs. GPT
by Nicolas Kovacs 28 Nov '20

28 Nov '20

Hi, I've always been a bit puzzled by the fact that Anaconda provides no option to manually create a partition table and specify if it's MBR or GPT. >From what I can tell - at least under CentOS 7.x - Anaconda will default to MBR, even if I specify a BIOS Boot partition. Maybe it switches automatically to GPT if the disk size requires it ( > 2 TB IIRC) though I don't have any corresponding hardware here to test it. Is this documented somewhere? Or is there a nifty little trick to tell Anaconda to prefer GPT partition tables? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 2

Emulate Ghost4Linux with standard Linux commands?
by Nicolas Kovacs 28 Nov '20

28 Nov '20

Hi, I'm currently trying to solve a tricky problem, and I don't even know if it's possible. Let me describe the situation with a practical example. In my office I have a sandbox PC for testing various setups that can't be tested in a virtual machine. I'm using this machine to test various setups with the Linux distributions I'm using, namely CentOS 7, CentOS 8 and OpenSUSE Leap 15. I have a series of Ghost images of these systems on a local FTP server, and I'm using G4L (Ghost4Linux) to transfer these images to and from the server. * https://sourceforge.net/projects/g4l/ On a side note, I take care of zeroing unused disk space in order to get relatively compact disk images like this: # dd if=/dev/zero of=/0bits bs=20M ; rm -f /0bits Besides my local sandbox machine, I also have a sandbox server in a datacenter, which I'm using for testing Internet-facing stuff. I'd like to be able to do something similar with this public machine, e. g. backup the whole disk content completely agnostic in terms of partitions and file systems and send it to a public FTP server. Unfortunately I can't boot G4L on this server, since I don't have physical access to the machine. The datacenter is about 700 km from where I can live. What I can do: fire up a rescue console via an administration web interface and boot a live Linux system, either Ubuntu 16.04 or 18.04. Now here's the question. From within my live system, how could I compress my system into a compact image and then send it to a distant FTP server? And once this is done, how could I get my image back from the server? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 2

dnf via ansible fails if baseurl is used on CentOS 8
by Thomas Eriksson 26 Nov '20

26 Nov '20

Hi, I ran into an odd issue on CentOS 8, anyone seen this? When repos are configured to use baseurl instead of mirrorlist, the ansible dnf module fails. It is as if it is ignoring the baseurl configuration. #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=BaseOS&infra=$infra baseurl=http://my.local.repo.server/$contentdir/$releasever/BaseOS/$basearch/os/ If trying to use the dnf module in ansible, dnf is still trying to find a mirror to use and fails. ansible test-build-0 -m dnf -a "name=zsh state=present" test-build-0 | FAILED! => { "changed": false, "msg": "Failed to download metadata for repo 'BaseOS': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": [] } Using dnf locally from the command line works fine with baseurl If I re-configure with repos using mirrorlist again, ansible dnf works as expected. Just looking for ideas... /Thomas

2 2

Replacing SW RAID-1 with SSD RAID-1
by Frank Bures 26 Nov '20

26 Nov '20

Hi, I want to replace my hard drives based SW RAID-1 with SSD's. What would be the recommended procedure? Can I just remove one drive, replace with SSD and rebuild, then repeat with the other drive? Thanks Frank -- <listfrank1(a)gmail.com>

12 23

Xorg --configure
by Michael Hennebry 24 Nov '20

24 Nov '20

I'm currently running Centos 8 off an SD card. It, unlike F32, lets me use my monitor's full 1440 x 900. Both seem to use defaults and EDID, but F32 gets it wrong and saddles me with 640 x 480 when I can find the incantation to have it run at all. The configuration files and directories I can find are pretty much empty. How do I add --configure to the Xorg command line? 'Tis my understanding that would generate a configuration file that I could port to F32. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

2 3

Update from 7 to 8
by Jerry Geis 24 Nov '20

24 Nov '20

I stumbled on this today. https://www.hostwinds.com/guide/upgrading-from-centos-7-to-8/ I understand the best is always a re-install.... But are these steps the next best thing to update from 7 to 8 ? Thanks, Jerry

3 2

installing Centos 8 to an SD card
by Michael Hennebry 24 Nov '20

24 Nov '20

I'm trying to install Centos 8 from a CD burned with Centos-8-2-2004-x86_64-boot , to an SD card in a USB SD card reader. The installer appears not to notice the card reader. Doing a df from tty2 also provides no notice of the card reader. Can what I am trying to do be done? The card currently has a German Knoppix on it. I know from experience that my machine can boot from it. How do I make this happen? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

1 1

Password manager for the command line ?
by Nicolas Kovacs 24 Nov '20

24 Nov '20

Hi, On my workstation and my laptop I'm using KeePassXC to store login credentials for my websites. The database is stored in my OwnCloud share, so it's synchronized between my two computers. Ideally I'd like to have something similar for my servers, but command-line driven. I know these tools exist but I haven't tested them yet. What I have in mind is a command-line password manager that stores the database in an encrypted database - like KeePassXC - and then I could eventually store this file in a private Gitlab repo to centralize it and access it from all my servers. Can you recommend any particular command line password manager ? Any recommendations / caveats for this kind of setup ? Cheers from the locked down South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

7 7

Thunderbird 78.4.0 after update
by R C 23 Nov '20

23 Nov '20

Hello, after an update I ended up with Thunderbird 78.4.0, it looks a little different, which is ok, but it seems that all my descriptions and also alerts disappeared. Is that a known problem? If so, how to fix that. (btw; I am not sure if I ever installed/used lightning, but that addon/extension doesn't seem to be there anymore.) If it is a known problem, is there a way to fix that? thanks, Ron

2 1

X defaults
by Michael Hennebry 23 Nov '20

23 Nov '20

I've been trying to move from Centos 7 to fedora. My monitor is 1440x900, but fedora only believes it's 640x480. Grrrr. xrandr has not helped. I've been trying to write X configuration files to tell fedora 1440x900, but no joy. Is there a way to get X to tell me its current beliefs, very preferably in configuration file format? According to the log file on Centos, everything was defaulted or probed. It contains no numbers. My guess is that fedora has different defaults and they are wrong for me. I've had problems like this before, so I'm unwilling to install until I know I can run a live version. That makes life clunky. I have to boot to non-graphics, do my editing and change the runlevel. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 6

Desktop Over NFS Home Blocked By Firewalld
by Michael B Allen 22 Nov '20

22 Nov '20

Hi, Just installed CentOS 7 that serves a home dir automounted over nfs. SELinux is disabled. If I go to the client (oldish version of Fedora) doing su - username works fine and the nfs export is mounted and I can see all files and everything seems well. But trying to actually login to the desktop from the client machine does not work. It starts to login but then just hangs with a black screen. Trying to just launch libreoffice --writer from a terminal as the nfs mounted user also hangs on the spash screen. If I then go to the server and 'systemctl stop firewalld', the desktop instantly logs in fine and libreoffice works from the term. So firewalld is blocking something that the Fedora desktop needs. What is it? What services do I need to add to firewalld? Thanks, Mike

5 12

selinux policy (& engine) broken in C7
by lejeczek 22 Nov '20

22 Nov '20

hi guys I've just gotten a bunch of updates via yum and something weird seems to be going on after the update. System has: selinux-policy-3.13.1-268.el7_9.2.noarch selinux-policy-targeted-3.13.1-268.el7_9.2.noarch actually three different boxes, all the same: $ semodule -l No modules. and an attempt to install modules fails: $ semodule -i openvpn.pp Failed to resolve typeattributeset statement at /etc/selinux/targeted/tmp/modules/400/pe-openvpn/cil:1 semodule: Failed! Does above "usual" work for you? many thanks, L.

3 2

CentOS-announce Digest, Vol 188, Issue 4
by centos-announce-request＠centos.org 20 Nov '20

20 Nov '20

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. CEBA-2020:5154 CentOS 7 gnome-shell BugFix Update (Johnny Hughes) 2. CEBA-2020:5154 CentOS 7 mutter BugFix Update (Johnny Hughes) 3. CEBA-2020:5154 CentOS 7 gdm BugFix Update (Johnny Hughes) 4. CESA-2020:5083 Moderate CentOS 7 microcode_ctl Security Update (Johnny Hughes) 5. CESA-2020:5099 Critical CentOS 7 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 19 Nov 2020 13:47:14 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 gnome-shell BugFix Update Message-ID: <20201119134714.GA25005(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 68b19039b1e53465dc3f08f0e56e24f7e1672b449a51dd05f8ae10ff49416b66 gnome-shell-3.28.3-32.el7.x86_64.rpm Source: 09eaee6b53a8debe898a03e6cbb1a0af1167a5e73d999abb4e5e8cc4de21829a gnome-shell-3.28.3-32.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 19 Nov 2020 13:47:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 mutter BugFix Update Message-ID: <20201119134726.GA25114(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: eb48815ca014d65a115c0ac9dba6f0c28dc765fbc161fc9ac11d3573786c6b4a mutter-3.28.3-30.el7.i686.rpm 42bfea454da2eacfb32d84a41908a2e6d89c8e46d04ea6a5ccefa5e251b3f3f9 mutter-3.28.3-30.el7.x86_64.rpm ca6edad606ed1ae0aad8a9ae177f501264d15718f85d304957942d0ed5768647 mutter-devel-3.28.3-30.el7.i686.rpm 2b4e66ff61ba4a7722ed44b9ca9487b146ddcbe7bc27c08a8b07be8049b546e7 mutter-devel-3.28.3-30.el7.x86_64.rpm Source: 82a4e302b32ea01c09871d4ecca9b3c7a43c555ad56b6805d4bb3f9699c0178f mutter-3.28.3-30.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Thu, 19 Nov 2020 13:47:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:5154 CentOS 7 gdm BugFix Update Message-ID: <20201119134740.GA25234(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:5154 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5154 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: aa4d5c25ee0ab0c6200041d7babcc2186123b17af2126662b27bed0013787faa gdm-3.28.2-26.el7.i686.rpm d9df089dfd6da09a0d335f5f7217eb49fb786af4bc6bdc86f8f5780e9588cb54 gdm-3.28.2-26.el7.x86_64.rpm b3523f6bd479abca1bc4c70f870af2423e9747ad2cb185692334588138742f50 gdm-devel-3.28.2-26.el7.i686.rpm 9a97f6e2d20a2e98ad20844706c47bf2fc689c6975c67067aa46d4ab03c1e47a gdm-devel-3.28.2-26.el7.x86_64.rpm 570aef75009a72d1f785eeeb0cf1e9b1c5113c73c46a3a7c2eebe0f87a44655b gdm-pam-extensions-devel-3.28.2-26.el7.i686.rpm 9b205c9658e9caf5ecd6d928179b7e7b36aa629b18e33540805f21a0d0b9f939 gdm-pam-extensions-devel-3.28.2-26.el7.x86_64.rpm Source: 7299b27241d70ab051693e3987cc595e044eb8061493cd6809befd2e25892119 gdm-3.28.2-26.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 19 Nov 2020 13:47:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5083 Moderate CentOS 7 microcode_ctl Security Update Message-ID: <20201119134747.GA25323(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5083 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:5083 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 09b0a412ef431cf5907e6d41f5bf960d051927c73b0a292dea9a52585f306e01 microcode_ctl-2.1-73.2.el7_9.x86_64.rpm Source: d7e8ae266d767b1645e22f0b18f229df0ef8289c742b7b3e7b434047a1270a7c microcode_ctl-2.1-73.2.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 19 Nov 2020 13:49:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:5099 Critical CentOS 7 firefox Security Update Message-ID: <20201119134909.GA25485(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:5099 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2020:5099 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 54c6e6aa53fe175c25dc35fe3f6476d9b195d85a4fc5e64d5625d1731cc5b1ce firefox-78.4.1-1.el7.centos.i686.rpm d8f95fca6716286e91c7ab7b9be9bd359800c870cc0bdb90128bf93397e9352d firefox-78.4.1-1.el7.centos.x86_64.rpm Source: 48cf4a93202542b3895382c41bdb9659a38b32186aca558fd35b15d62ddafafe firefox-78.4.1-1.el7.centos.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 188, Issue 4 ***********************************************

1 0

server rebooted email
by Kenneth Porter 19 Nov '20

19 Nov '20

I used to put a line in rc.local to email root that my server rebooted. Does anyone have a nice systemd unit file to do the same? Also useful would be a shutdown email with the output of uptime. (I usually do that manually when rebooting for a kernel update.)

3 2

Help with VirtualBox on CentOS 7
by Jerry Geis 19 Nov '20

19 Nov '20

Any Virtualbox on CentOS guru's out there? I only have 1 VM on my linux host. in the update process to virtualbox 6.1.16 my config was lost. When I run Virtualbox my VM does not show. So I desire to add it back. My structure is this. ls -l /home/silentm/vmware/CentOS\ 64-bit\ LSI/ -rw------- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram -rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd -rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx -rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf -rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit LSI.vmdk -rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx -rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log -rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log -rw-r--r-- 1 silentm silentm 256013 May 31 10:09 vmware-2.log -rw-r--r-- 1 silentm silentm 322239 Aug 13 08:31 vmware.log When I click add and goto the directory above - IT ONLY wants to add *.xml and *.vbox. So that is no good. When I click New and Enter my name, and use existing disk - it does not like that either. How can I get this same VM to be in my menu and run again ? Thanks, Jerry

3 3

(C8) root on mdraid
by Łukasz Posadowski 18 Nov '20

18 Nov '20

Hello everyone. I'm trying to install CentOS 8 with root and swap partitions on software raid. The plan is: - create md0 raid level 1 with 2 hard drives: /dev/sda and /dev/sdb, using Linux Rscue CD, - install CentOS 8 with Virtual Box on my laptop, - rsync CentOS 8 root partition on /dev/md0p1, - chroot in CentOS 8 root partition, - configure /etc/mdadm.conf, grub.cfg, initramfs, install bootloader on both sda and sdb drives. I think I can do first four of the above, but my CentOS installation acts strange after rebooting the server. It recognizes the raid, but boots randomly with root on /dev/sda1 (and recognizes raid with /dev/sdb disk), or with root on /dev/sdb1 (and recognizes raid with /dev/sda disk). When booting from Linux Rescue CD, the raid with two disk is recognized. Creating md0 wth Linux Rescue CD. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk sdb 8:16 0 232.9G 0 disk sr0 11:0 1 871M 0 rom # mdadm --create /dev/md0 --level=1 --raid-devices=2 --metadata=0.9 /dev/sda /dev/sdb mdadm: array /dev/md0 started. # mdadm --detail --scan --verbose ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda,/dev/sdb # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb[1] sda[0] 244198464 blocks [2/2] [UU] [>....................] resync = 1.9% (4682944/244198464) finish=52.2min speed=76356K/sec bitmap: 2/2 pages [8KB], 65536KB chunk unused devices: <none> (1 hour later) # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb[1] sda[0] 244198464 blocks [2/2] [UU] bitmap: 0/2 pages [0KB], 65536KB chunk unused devices: <none> # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 sdb 8:16 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 sr0 11:0 1 871M 0 rom --------------------------------- So far so good. Now partitions: # fdisk /dev/md0 Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x64998720. Command (m for help): o Created a new DOS disklabel with disk identifier 0xfe784f57. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): p Partition number (1-4, default 1): First sector (2048-488396927, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-488396927, default 488396927): +220G Created a new partition 1 of type 'Linux' and of size 220 GiB. Command (m for help): n Partition type p primary (1 primary, 0 extended, 3 free) e extended (container for logical partitions) Select (default p): p Partition number (2-4, default 2): First sector (461375488-488396927, default 461375488): Last sector, +/-sectors or +/-size{K,M,G,T,P} (461375488-488396927, default 488396927): +4G Created a new partition 2 of type 'Linux' and of size 4 GiB. Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs sda 8:0 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 ├─md0p1 259:0 0 220G 0 part └─md0p2 259:1 0 4G 0 part sdb 8:16 0 232.9G 0 disk └─md0 9:0 0 232.9G 0 raid1 ├─md0p1 259:0 0 220G 0 part └─md0p2 259:1 0 4G 0 part sr0 11:0 1 871M 0 rom # mkfs -t ext4 /dev/md0p1 mke2fs 1.44.5 (15-Dec-2018) Creating filesystem with 57671680 4k blocks and 14417920 inodes Filesystem UUID: 511d0d07-4d55-4b6c-939e-d23ae2da1ce0 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (262144 blocks): done Writing superblocks and filesystem accounting information: done # mkswap /dev/md0p2 Setting up swapspace version 1, size = 4 GiB (4294963200 bytes) no label, UUID=5667d007-0d3e-4b54-8a72-6ade52609adc -------------------------------------- Mount would be root partition: # mkdir /mnt/centos8 # mount -t ext4 /dev/md0p1 /mnt/centos8/ -------------------------------------- OK, I have what I need. Now log into virtualised CentOS 8 in Virtual Box. # rpm -q rsync rsync-3.1.3-7.el8.x86_64 # rpm -q mdadm mdadm-4.1-13.el8.x86_64 # rsync -vaxAXHSz --delete / 192.168.111.167:/mnt/centos8/ The authenticity of host '192.168.111.167 (192.168.111.167)' can't be established. ECDSA key fingerprint is SHA256:HukswAQlarthYqbpVHIHm80JaWHKX12AxgOn8UuKQxk. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.111.167' (ECDSA) to the list of known hosts. root(a)192.168.111.167's password: sending incremental file list ./ bin -> usr/bin lib -> usr/lib lib64 -> usr/lib64 sbin -> usr/sbin [lots and lots of files...] var/yp/ sent 694,980,592 bytes received 745,802 bytes 1,795,422.95 bytes/sec total size is 1,558,934,091 speedup is 2.24 -------------------------------------- Chrooting time: # mount --types proc /proc /mnt/centos8/proc # mount --rbind /sys /mnt/centos8/sys # mount --make-rslave /mnt/centos8/sys # mount --rbind /dev /mnt/centos8/dev # mount --make-rslave /mnt/centos8/dev # chroot /mnt/centos8 /usr/bin/bash # source /etc/profile Configure raid: # mdadm --detail --scan --verbose ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda,/dev/sdb # mdadm --detail --scan --verbose > /etc/mdadm.conf Edit /etc/fstab: # cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Nov 8 10:05:31 2020 # # Accessible filesystems, by reference, are maintained under # '/dev/disk/'. See man pages fstab(5), findfs(8), mount(8) and/or # blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update # systemd units generated from this file. # #UUID=36c5a887-79c3-4b6a-b433-0e4d7574b1e4 / #ext4 defaults 1 1 /dev/md0p1 / ext4 defaults 1 1 Configure and install bootloader: # cat /etc/default/grub GRUB_TIMEOUT=8 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true # grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... done # grub2-install /dev/sda Installing for i386-pc platform. Installation finished. No error reported. # grub2-install /dev/sdb Installing for i386-pc platform. Installation finished. No error reported. Configure initramfs: # dracut -f /boot/initramfs-4.18.0-193.28.1.el8_2.x86_64.img # 4.18.0-193.28.1.el8_2.x86_64 -------------------------------- Reboot and login to my new CentOS 8 installation: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232.9G 0 disk sdb 8:16 0 232.9G 0 disk ├─sdb1 8:17 0 220G 0 part / └─sdb2 8:18 0 4G 0 part sr0 11:0 1 871M 0 rom # mdadm --detail --scan --verbose INACTIVE-ARRAY /dev/md127 num-devices=1 metadata=0.90 UUID=fef2f68b: 1a462c80:c44c77eb:7ee19756 devices=/dev/sda # cat /proc/mdstat Personalities : md127 : inactive sda[0](S) 244198464 blocks unused devices: <none> I can live with md127, because it happens constantly on multiple distributions, but why root is on /dev/sdb1 (and sometimes it's /dev/sda1)? I'm running out of spells now. :) Do anyone can suggest what else I forgot to do? thanks -- Łukasz Posadowski

5 8

Intel RST RAID 1, partition tables and UUIDs
by H 18 Nov '20

18 Nov '20

I have been having some problems with hardware RAID 1 on the motherboard that I am running CentOS 7 on. After a BIOS upgrade of the system, I lost the RAID 1 setup and was no longer able to boot the system. Testdisk revealed that the partition tables had been damaged and because I had earlier saved information from fdisk, I was able to recreate the partitions. However, booting into the BIOS and recreating/synchronizing the RAID from one of the disks (took around 20 hours for 256 GB disks), I again lost the ability the boot and the partition tables were similarly damaged. Eventually I was able to boot the system again from one of the two disks and it is now up and running, now running without RAID. - Should I expect that the Intel RAID 1 setup changes the partition tables? I should add that the disks were originally created after the RAID 1 was setup. - After fooling around with testdisk (and prior to that, parted), it turned out that I had lost the disk UUID for both disks, they were both set to 000... Partition UUIDs seemed unchanged from before, including the LUKS partitions. Are disk UUIDs (not partition UUIDs) not used by Linux since I have not - yet - seen any effects of the missing disk UUIDs? Because there seems to be a couple of other issues with the motherboard, I expect to have it replaced early this week but I am still interested in learning more. Thanks.

5 8

Best practice preparing for disk restoring system
by H 18 Nov '20

18 Nov '20

Short of backing up entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. So far I am collecting information from: - fdisk -l - blkid - lsblk - grub2-efi.cfg - grub - fstab Hoping that this would supply me with /all/ information to restore a system - with the exception of installed operating system, apps and data. I would appreciate any and all thoughts on the above!

6 9

why does virtual console start affect graphical start up?
by Kay Schenk 17 Nov '20

17 Nov '20

Hello all-- I have 3 CentOs 8 kernels insalled on my new machine -- 1. 4.18.0-193.14.2.el8_2.x86_6 2. 4.18.0-193.19.1.el8_2.x86_64 << using this one for this graphical boot 3. 4.18.0-193.28.1.el8_2.x86_64 Only #3 will boot without a *Virtual console can not start *error message but it hangs up trying to get into graphical mode, although it will boot to multi-user. The first 2 seem to work reaosnably well in either graphical or multi-user but I get a *Virtual console can not start *in boot messages with both of these. Does anyone know anything about this? Having a heck of a time trying to prevent lock ups. Thanks. **

1 1

Apologies - possible hardware problem?
by Jeffrey Layton 16 Nov '20

16 Nov '20

Good afternoon, I have a home workstation with an AMD CPU, Titan V GPU, 32 GB of memory, and a root SSD and /home on spinning disks. Right now it has xubuntu 18.04 on it and it would boot fine. I shut it down and restarted it to get an inventory before I put CentOS 8.2 on it. It won't boot now. It gets to the grub menu and freezes. I can't use the keyboard to select an item in the menu and I can't press enter to make it boot or press "e" to edit the boot line. It just sits there (seemingly forever). Here's what I've tred: 1. New keyboard/mouse - no change 2. Different monitor - no change 3. Booting from the CentOS 8.2 iso on a USB stick - no change 4. Replacing the TItan V card with a GT 1030 NV card - no change When booting from a USB stick, I get the BIOS splash screen and press "DEL" to get to the menu, but the menu never shows up. It just freezes. This one has me stumped. Not being able to boot from a USB stick is really puzzling. I've never seen that before. Possible bad MB? My apologies for using the list to help debug problems but since I'm moving to CentOS 8.2 I thought people might have some ideas. TIA! Jeff

4 6

mdadm raid-check
by hw 16 Nov '20

16 Nov '20

Hi, is it required to run /usr/sbin/raid-check once per week? Centos 7 does this. Maybe it's sufficient to run it monthly? IIRC Debian did it monthly. I just checked on Fedora 32. It does not run raid-check at all, at least not via a cron entry. /usr/sbin/raid-check is available, though. Is that an oversight? (I started it manually now and will check if it's run once I update to 33.)

3 4

ssacli start rebuild?
by hw 15 Nov '20

15 Nov '20

Hi, is there a way to rebuild an array using ssacli with a P410? A failed disk has been replaced and now the array is not rebuilding like it should: Array A (SATA, Unused Space: 1 MB) logicaldrive 1 (14.55 TB, RAID 1+0, Ready for Rebuild) physicaldrive 1I:0:1 (port 1I:box 0:bay 1, SATA HDD, 4 TB, OK) physicaldrive 1I:0:2 (port 1I:box 0:bay 2, SATA HDD, 4 TB, OK) physicaldrive 1I:0:3 (port 1I:box 0:bay 3, SATA HDD, 4 TB, OK) physicaldrive 1I:0:4 (port 1I:box 0:bay 4, SATA HDD, 8 TB, OK) physicaldrive 2I:0:5 (port 2I:box 0:bay 5, SATA HDD, 4 TB, OK) physicaldrive 2I:0:6 (port 2I:box 0:bay 6, SATA HDD, 4 TB, OK) physicaldrive 2I:0:7 (port 2I:box 0:bay 7, SATA HDD, 4 TB, OK) physicaldrive 2I:0:8 (port 2I:box 0:bay 8, SATA HDD, 4 TB, OK) I'd expect the rebuild to start automatically after 1I:0:4 was replaced. Is the new drive being larger than the old one (4-->8) causing issues?

6 27

Centos 8 and logwatch
by Blaž Bogataj 14 Nov '20

14 Nov '20

Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz

4 3

yum update security updates only
by Eric Chennells 14 Nov '20

14 Nov '20

Hello, I'm trying to do a yum update and only apply the security patches. I'm aware of yum update --security , however when I do that it fails to install any updates. I've tried this on a fresh 7.8.2003 (core) system, as well as the Centos 7 AMI on AWS, specifically ami-04a25c39dc7a8aebb and I get the same results. There are definitely security updates to apply. For each package which needs to be updated, it lists "<package name>" from updates removed (updateinfo). Does anyone know what's going on here? Thanks, Eric

5 5

CentOS-announce Digest, Vol 188, Issue 2
by centos-announce-request＠centos.org 13 Nov '20

13 Nov '20

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. Release for CentOS Linux 7 (2009) on armhfp aarch64 i386 ppc64 ppc64le and power9 (Pablo Sebasti?n Greco) 2. Release for CentOS Linux 7 (2009) on the x86_64 Architecture (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Nov 2020 09:31:25 -0300 From: Pablo Sebasti?n Greco <pgreco(a)centosproject.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Release for CentOS Linux 7 (2009) on armhfp aarch64 i386 ppc64 ppc64le and power9 Message-ID: <9f9bc188-2372-b845-e424-0d9e30c74d53(a)centosproject.org> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the general availability of CentOS Linux 7 (2009) for across our alternative architectures. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trimmed off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. ---------- Special notes Altarch kernel: After RedHat's decision to deprecate power9 and aarch64 releases during the 7.7 cycle, and our decision to keep building them with the others (using the kernel from RHEL8), we decided to keep down this road. As 7.x and 8.x releases are not in sync, released kernel is 4.18.0-193.28.1 (8.2), but we're working on updating it to 4.18.0-240 (8.3) soon. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors in a file called 0_README.txt next to the isos. That file clearly highlights the difference in the images, and when one might be more suitable than the others. Altarch images can be downloaded at : http://mirror.centos.org/altarch/7/isos/ sha256sum for ppc64 1f53ccce8867412a91eca3d0dd99333ebef871ffba3b6fb3af7eb14e280dc653 CentOS-7-ppc64-Everything-2009.iso dbc2d0609140f5d689dd16cdb64bfa181bf2c31f72ff41b9ab9dd5241dd74e0e CentOS-7-ppc64-NetInstall-2009.iso 2cae62d1e24965de6d62c8031d0be745f836c99f9640184055fc4d99e29be966 CentOS-7-ppc64-Minimal-2009.iso sha256sum for ppc64le 1e1f4a7cebd9fa99af5de34543ae8d874c2fa2ac9ca16b17dbef85a7f36f8ea4 CentOS-7-ppc64le-Everything-2009.iso 76423e534281666d00c0989ab7e4cb48e0b412207a9e8fd6269bfef23a7e71c7 CentOS-7-ppc64le-NetInstall-2009.iso 145286cee095acc549b6fb9ebcaa394bb6d4919b7f95a0b0aa4a707a57ea80ed CentOS-7-ppc64le-Minimal-2009.iso sha256sum for power9: d7b93fe2c33dd4ed01c1b83c7abd20d20e5a46e9da469c1df1f506f19f1278b3 CentOS-7-power9-Everything-2009.iso 4795492d5361268aad79be27123c78909925f5648489f790718df6d6b7c0b039 CentOS-7-power9-NetInstall-2009.iso e4bd38480e65a4462004f30f69c4b193c687e77b7ad96d567c33581a64873568 CentOS-7-power9-Minimal-2009.iso sha256sum for i386: dd238357e1750cfb25fc87e5c21891598599bf5df3ee2a749a6fd1a8fe5ec937 CentOS-7-i386-Everything-2009.iso 96c3ae101f200cac2c0d6d03a1642d69cc8f501a568ce2cc3e5ffdfdc090145f CentOS-7-i386-NetInstall-2009.iso bcbde5d345c5013fa618c38380765547be01a354883b3055f32d7067dd7b5bca CentOS-7-i386-Minimal-2009.iso shasum256 for aarch64 / ArmServer: b898822822fd5ffacc8da074adcd6b882ac0f73a269111b15871e16c2ce9d774 CentOS-7-aarch64-Everything-2009.iso 3c53c686d72649adc9afde1865b3f7fa79212966f387634eaf249a66fccfec53 CentOS-7-aarch64-NetInstall-2009.iso 1bef71329e51f9bed12349aa026b3fe0c4bb27db729399a3f9addae22848da9b CentOS-7-aarch64-Minimal-2009.iso 54951b0ba40065931d39c6051a1c91cedebd6e2a0694242595faa39424a25e1b images/CentOS-Userland-7-aarch64-generic-Minimal-2009-sda.raw.xz 99ef70e48d0499e2b59ab45eafe67581bcc8fa997638e936852f0f6255995faf images/CentOS-Userland-7-aarch64-RaspberryPI-Minimal-4-2009-sda.raw.xz sha256sums for armhfp: d2c647d265c075727714fc30b916a6f5a48ec54e980d75807c4cfdfc31da0e13 CentOS-Userland-7-armv7hl-generic-GNOME-2009-sda.raw.xz 339f9ead25bde5433a6146e05ad87f29a0ac0bd83a927e7b827177897e24208c CentOS-Userland-7-armv7hl-generic-KDE-2009-sda.raw.xz 1b99b4e73427e3e4973a358271e8d1582c23eb31c21fbd732762488bec366348 CentOS-Userland-7-armv7hl-generic-Minimal-2009-sda.raw.xz e83bc778d41221b575066f14e9aa42c47cdb64e4bf6df48d790d438766a41275 CentOS-Userland-7-armv7hl-generic-Minimal-lpae-2009-sda.raw.xz f45fcaabf55e3453ac37faed76b201716e4585a5de049b56dac81dbd36496d64 CentOS-Userland-7-armv7hl-RaspberryPI-GNOME-2009-sda.raw.xz 96b27c95f9b81f68db8e6ebeb3a3ef38daf4da88f82f47e64e1b1b9c2574c982 CentOS-Userland-7-armv7hl-RaspberryPI-KDE-2009-sda.raw.xz 38953b1c8580fe9a7ed740960a3965b378e7be56dc4b1563b3b329b3614a03c4 CentOS-Userland-7-armv7hl-RaspberryPI-Minimal-2009-sda.raw.xz dd5e038337fb564b2f6cb45302c8d5aa1c7b92e8e67655d42b9368426a5d05b9 CentOS-Userland-7-armv7hl-RaspberryPI-Minimal-4-2009-sda.raw.xz a6555b0754b119c1ee15f81ae258c9deb8e89cf0aec8e679b660a42d67c75b8f CentOS-Userland-7-armv7hl-RootFS-Minimal-2009-sda.raw.xz -------- Additional Images The container, Vagrant, Cloud and Atomic Host images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at? : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel ). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! -- Pablo Greco ------------------------------ Message: 2 Date: Thu, 12 Nov 2020 06:41:38 -0600 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 (2009) on the x86_64 Architecture Message-ID: <2a5ce9c6-5e2c-2aa7-f2c8-afb508a1ec65(a)centos.org> Content-Type: text/plain; charset="utf-8" Release for CentOS Linux 7 (2009) on the x86_64 Architecture We are pleased to announce the general availability of CentOS Linux 7 (2009) for the x86_64 architecture. Effectively immediately, this is the current release for CentOS Linux 7 and is tagged as 2009, derived from Red Hat Enterprise Linux 7.9 Source Code. As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 7 machine by just running 'yum update'. As with all CentOS Linux 7 components, this release was built from sources hosted at git.centos.org. In addition, SRPMs that are a byproduct of the build (and also considered critical in the code and buildsys process) are being published to match every binary RPM we release. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at : http://wiki.centos.org/Sources Debuginfo packages are also being signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 7, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like Extras/ and Plus/ However this time we have also extended this to the SIG content hosted at mirror.centos.org, and some older End of Life content has been dropped. Everything we ever release, is always available on the vault service for people still looking for and have a real need for it. ---------- Download In order to conserve donor bandwidth, and to make it possible to get the mirror content sync'd out as soon as possible, we recommend using torrents to get your initial installer images: Details on the images are available on the mirrors at http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file clearly highlights the difference in the images, and when one might be more suitable than the others. sha256sum x86_64: e33d7b1ea7a9e2f38c8f693215dd85254c3a4fe446f93f563279715b68d07987 CentOS-7-x86_64-DVD-2009.iso 689531cce9cf484378481ae762fae362791a9be078fda10e4f6977bf8fa71350 CentOS-7-x86_64-Everything-2009.iso 07b94e6b1a0b0260b94c83d6bb76b26bf7a310dc78d7a9c7432809fb9bc6194a CentOS-7-x86_64-Minimal-2009.iso b79079ad71cc3c5ceb3561fff348a1b67ee37f71f4cddfec09480d4589c191d6 ? CentOS-7-x86_64-NetInstall-2009.iso Information for the torrent files and sums are available at http://mirror.centos.org/centos/7/isos/x86_64 -------- Additional Images The Cloud images are posted here: https://cloud.centos.org/centos/7/images/ The container and Vagrant images are being prepared and will be released in the next few days. Look for an announcement posted to the centos-announce list for more information on availability for these in the coming days. ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at? : http://twitter.com/CentOSProject on Facebook at : https://www.facebook.com/groups/centosproject/ on LinkedIn at : https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on freenode.net in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list ( http://lists.centos.org/mailman/listinfo/centos-devel ). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! Thanks, Johnny Hughes

1 0

Using anaconda gui without mouse
by Gianluca Cecchi 13 Nov '20

13 Nov '20

Hi, I should use Anaconda gui in CentOS 8.2 graphical way but the idrac doesn't map the mouse. What are the shortcuts for using only a keyboard? In particular it seems I'm blocked in the partitions page Any time I select one and press enter to configure the right side details/parameters, I don't find a way then to come back to the left side and move up/down to select another partition and configure its parameters. I would like to use it and not text install. Thanks, Gianluca

1 0

Re: [CentOS] MIDI on a VM
by J Martin Rushton 13 Nov '20

13 Nov '20

On 13/11/2020 07:01, Simon Matter wrote: >> On 12/11/2020 17:26, Ralf Prengel wrote: >>> Hallo, >>> witch virtualizer are you using. >> >> KVM/QEMU >> >>> Sure that the virtual sound-device is connected with the right hardware? >> >> I can play CDs and listen to YouTube on the host, so I'm assuming the >> hardware is fine. > > I don't know how this works here but doesn't playing MIDI files mean you > need a MIDI capable sound card which generates the sound? Maybe the > virtual sound-device is only capable to play audio? > > Regards, > Simon > Very good point. I will investigate further. I had two models in my head: 1) The Frescobaldi playback module did the MIDI-> sound conversion. 2) The virtual card passed the signals on to the physical card. Perhaps your third model is correct. -- J Martin Rushton MBCS

1 1

Unable to get dummy interfaces to persist across reboots in CentOS 8
by Frank Even 13 Nov '20

13 Nov '20

Hello all, hoping someone can help me out here. I cannot get dummy interfaces on a new Cent8 build to persist across reboots. On Cent7 - this is the process I use: Create Dummies: # cat /etc/modules-load.d/dummy.conf dummy # cat /etc/modprobe.d/dummyopts.conf options dummy numdummies=4 # ip link add dummy0 type dummy ## - repeating a/ ascending dummyN adapters for as many needed # service network start # dracut -f Now this was different than even how 6 handled it, forget how I finally dug that up (possible I even asked here). I've applied this same configuration to a Cent8 box I'm trying to stand up and it all appears to work fine, but unlike the Cent7 boxes, when the Cent8 box comes back up, all the dummy adapters are missing. I've been searching all over trying to find some documentation on this to no avail. I'm hoping someone has some suggestions here to help out. Thanks, Frank

3 8

crontab query
by Frank M. Ramaekers Jr. 12 Nov '20

12 Nov '20

I need to schedule a process/program every hour on the hour between 9am and 4pm on the 2nd through the 9th of each month except on Saturday and Sunday. So, I tried this entry: 0 9-16 2-9 * 1-5 ./myprog.sh Unfortunately it runs outside of the 2nd through the 9th and still runs on Sat. through Sun. Is there a way to do this (outside the program itself)? -Frank

4 4

run firefox via an ssh tunnel
by S Bob 12 Nov '20

12 Nov '20

Hi all; I'm trying to setup an ssh tunnel so I can run firefox on a remote laptop and have the display locally. I have 2 laptops local = CentOS 7 remote = mac OSX 10.15.7 I want to create an ssh tunnel on the local CentOS 7 laptop, then run firefox on the mac with the display showing up on the CentOS laptop. Is this doable? Thanks in advance

6 12

MIDI on a VM
by J Martin Rushton 12 Nov '20

12 Nov '20

I have an application (Frescobaldi/Lilypond) that generates and plays MIDI files. Due to problems with flatpak I can only run it on C8 or Fedora, both of which live on VMs. The host is running C7. I've tried "adding hardware", specifically a virtual sound card, to the VMs, but still they remain silent. How do I connect the virtual sound cards to the physical sound card so that I can hear the music? Thanks, Martin -- J Martin Rushton MBCS

2 2

CentOS 8 vncserver
by Jerry Geis 12 Nov '20

12 Nov '20

I am trying to get vncserver working on CentOS 8. Fully updated. On the console - logged in as a normal user I run: export DISPLAY=:0.0 xhost + /usr/bin/x0vncserver -display :0 -rfbport 5901 -passwordfile /home/silentm/.vnc/passwd I get this error: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/x0vncserver: unable to open display ":0" Based on the error I changed the DISPLAY=:0 and tried again - but same error. Am I doing something wrong? I dont really need this to start as a service was just trying to start by hand. Thanks Jerry

2 1

centos8 / anaconda EFI regression / HFS+ ESP
by Leon Fauster 12 Nov '20

12 Nov '20

Hi folks, years ago I had no problem installing CentOS7 on my iMac workstation (iMac Late 2015). The installation worked out of the box. Today I wanted to upgrade to CentOS8 and while configuring the partitions I get an error that the installation can not start because: "HFS+ ESP needed and mounted on /boot/efi". In fact they are the same partition as for CentOS7. Is this a regression of anaconda, implying that the EFI partition must be HFS based? I can boot CentOS7 with the vfat EFI partition ... -- Leon

2 2

BIOS RAID0 and differences between disks
by H 12 Nov '20

12 Nov '20

My computer running CentOS 7 is configured to use BIOS RAID0 and has two identical SSDs which are also encrypted. I had a crash the other day and due to a bug in the operating system update, I am unable to boot the system in RAID mode since dracut does not recognize the disks in grub. After modifying the grub command line I am able to boot the system from one of the harddisks after entering the LUKS password, seemingly without any problems but am obviously not running in RAID0 mode. When I booted in single-disk mode I am sure there were some new files created on the single SSD the system sees but I fairly quickly shut it down until this can be fixed. My question is: once the operating system fix has been released and I can once again boot in BIOS RAID0 mode and decrypting both SSDs (same password entered only once of course), how will the BIOS RAID0 react? How will it handle new files on one disk, altered timestamps etc.? Thanks.

3 5

Error from unix_chkpwd
by Sergio Belkin 10 Nov '20

10 Nov '20

Hi, On CentOS 7.7.1908 I've got the following error message: unix_chkpwd[1026]: could not obtain user info (root) I dont' know why... There are no SELinux errors, and the permissions of relevant files are: ls -Z /etc/shadow /etc/passwd /usr/sbin/unix_chkpwd -rw-r--r--. root root system_u:object_r:passwd_file_t:s0 /etc/passwd ----------. root root system_u:object_r:shadow_t:s0 /etc/shadow -rwsr-xr-x. root root system_u:object_r:chkpwd_exec_t:s0 /usr/sbin/unix_chkpwd Any idea? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

1 0

CentOS-announce Digest, Vol 188, Issue 1
by centos-announce-request＠centos.org 10 Nov '20

10 Nov '20

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-2020:4348 Moderate CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 2. CESA-2020:4182 Important CentOS 6 kernel Security Update (Johnny Hughes) 3. CESA-2020:4953 Important CentOS 6 xorg-x11-server Security Update (Johnny Hughes) 4. CESA-2020:4056 Important CentOS 6 qemu-kvm Security Update (Johnny Hughes) 5. CESA-2020:4183 Moderate CentOS 6 bind Security Update (Johnny Hughes) 6. CEBA-2020:4329 CentOS 6 tzdata BugFix Update (Johnny Hughes) 7. CESA-2020:4946 Important CentOS 6 libX11 Security Update (Johnny Hughes) 8. CESA-2020:4330 Important CentOS 6 firefox Security Update (Johnny Hughes) 9. CESA-2020:4947 Important CentOS 6 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 9 Nov 2020 13:12:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4348 Moderate CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20201109131226.GA28275(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4348 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:4348 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d6f1995389f355c6291086ed05cfa7a943175fc2db4fc614998a0a792a13978b java-1.8.0-openjdk-1.8.0.272.b10-0.el6_10.i686.rpm 1c679e4feeb281e86de6485e7c1d0d9876a0324ef20ffb10c49562257cbb38c9 java-1.8.0-openjdk-debug-1.8.0.272.b10-0.el6_10.i686.rpm 17907b3347b984f6d7b2a48d869889bc761e320f55200ad879f2600b029fd081 java-1.8.0-openjdk-demo-1.8.0.272.b10-0.el6_10.i686.rpm 63cf7fa5a0c8b2efc656abaa5ffa34b49bce61f3b438532d8fdacfef2ed19de1 java-1.8.0-openjdk-demo-debug-1.8.0.272.b10-0.el6_10.i686.rpm 902a8f2197e5b646323f94e4861f6663039f8908d14a514db2ca5a1df2b1ce9e java-1.8.0-openjdk-devel-1.8.0.272.b10-0.el6_10.i686.rpm eaa4953f323d0056c9b1e7abd4d7cf7cc1c3e57f120294cdf4f42185fcae2759 java-1.8.0-openjdk-devel-debug-1.8.0.272.b10-0.el6_10.i686.rpm b44b74493ee7c9b191179434ddcd64e0ea4d370084068ef04377f2fb7c7bd594 java-1.8.0-openjdk-headless-1.8.0.272.b10-0.el6_10.i686.rpm 498beb8ec88ab3442fce4293243448a833dbe7838733d2b15943a1876021bce5 java-1.8.0-openjdk-headless-debug-1.8.0.272.b10-0.el6_10.i686.rpm 934dafde9d638ea7f4be80af346353bae41f5da4f93f4e9790cf3acc1209568a java-1.8.0-openjdk-javadoc-1.8.0.272.b10-0.el6_10.noarch.rpm 9c442e876ad729790037fdbcd8b8dc9e3dd001f09798af0f5255de0cdca84dc0 java-1.8.0-openjdk-javadoc-debug-1.8.0.272.b10-0.el6_10.noarch.rpm 45b7eb3de69dcbf495215b7765cbe98c272ba573625edf3392478a736f7e9729 java-1.8.0-openjdk-src-1.8.0.272.b10-0.el6_10.i686.rpm d0420495ed95d46e96352cdddc2e45562567b723b6ca4736e6bd38786f21d14d java-1.8.0-openjdk-src-debug-1.8.0.272.b10-0.el6_10.i686.rpm x86_64: 1aee939598243dd6a4587cd5dc1e534135cccba73f48f9e0ad4d8294b8c74c1e java-1.8.0-openjdk-1.8.0.272.b10-0.el6_10.x86_64.rpm 62228500650393a9cae1c8bf84dd401d063bf4008bd249e3f10fc5e6647a37d2 java-1.8.0-openjdk-debug-1.8.0.272.b10-0.el6_10.x86_64.rpm e4b2ebbf20219b870e76522851382efb08d22aa7ec725dda8aca5368302bd8de java-1.8.0-openjdk-demo-1.8.0.272.b10-0.el6_10.x86_64.rpm 334513c5a45c586372033f025df50423f3aedcada5c45f28ea5d14799db38cc7 java-1.8.0-openjdk-demo-debug-1.8.0.272.b10-0.el6_10.x86_64.rpm 93ac31af6e0f817200367b635555699d594a61c7275dc3882238b67659e48915 java-1.8.0-openjdk-devel-1.8.0.272.b10-0.el6_10.x86_64.rpm c8322c3034d823d2539d36fe8c7ab9c4d24c586d5585639defeeb11a6bee7b96 java-1.8.0-openjdk-devel-debug-1.8.0.272.b10-0.el6_10.x86_64.rpm 4e1c702d9605fda135ae544fced1ef01a339307022027779d1187a4ccb04d505 java-1.8.0-openjdk-headless-1.8.0.272.b10-0.el6_10.x86_64.rpm 87bc9dbee88c76d9c485bb91f42e42a7fdde97eb3fc368ad91b53260a8f3256f java-1.8.0-openjdk-headless-debug-1.8.0.272.b10-0.el6_10.x86_64.rpm 934dafde9d638ea7f4be80af346353bae41f5da4f93f4e9790cf3acc1209568a java-1.8.0-openjdk-javadoc-1.8.0.272.b10-0.el6_10.noarch.rpm 9c442e876ad729790037fdbcd8b8dc9e3dd001f09798af0f5255de0cdca84dc0 java-1.8.0-openjdk-javadoc-debug-1.8.0.272.b10-0.el6_10.noarch.rpm d27f253a11e46e76643aa79f37b33e9b8b45086ab2c8747dd9ac68653aa8c5e3 java-1.8.0-openjdk-src-1.8.0.272.b10-0.el6_10.x86_64.rpm 4c1702e43be36980f02cd49b5bdaec66269939ad72800a8bf2a2a1fdc19ba078 java-1.8.0-openjdk-src-debug-1.8.0.272.b10-0.el6_10.x86_64.rpm Source: 8f509a705d1ddb1c414715f05ea5521b1a8b7e5598f21f542cb7fab94f045533 java-1.8.0-openjdk-1.8.0.272.b10-0.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 9 Nov 2020 13:13:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4182 Important CentOS 6 kernel Security Update Message-ID: <20201109131323.GA28567(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4182 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4182 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a4324ccfcccc4613bed19100b711a36789a0d46b84392b4eda6c4d0a434c2b08 kernel-2.6.32-754.35.1.el6.i686.rpm ce8a1790390c1920d3b3cfe0540658499009c2f2fe9bfaf990fec534197c877b kernel-abi-whitelists-2.6.32-754.35.1.el6.noarch.rpm 4abfa019519d1b3bfe8f1018850719b377f992fababb4e33fa9307dfd1194ba0 kernel-debug-2.6.32-754.35.1.el6.i686.rpm 7c74392f0655952951c5db0299e59c117691b6139d82ea75b9ba01d80fd97684 kernel-debug-devel-2.6.32-754.35.1.el6.i686.rpm 0bec59f403abcfc4f91800ad426675b14c39bd4993f8768a2b244b6c2c4f8313 kernel-devel-2.6.32-754.35.1.el6.i686.rpm 5068119f93e2d71d2a00ee107db9576671cc73816b7aa80d4020b62db91f0216 kernel-doc-2.6.32-754.35.1.el6.noarch.rpm 21129fbdc585f999c9771847ba5772dbdefd13a825ec0bd979c6806fe216a04b kernel-firmware-2.6.32-754.35.1.el6.noarch.rpm 8487b3aecd533f3f9ebef48d8c5f060ad05ae1b6c9cb94a6279789fce1afa56f kernel-headers-2.6.32-754.35.1.el6.i686.rpm a5484c9851f17971a0563b2f554b4d695bc7e39318705a101f8829d9642d029b perf-2.6.32-754.35.1.el6.i686.rpm a7844297446da4c5a1a70bea318189b25b9b47c9bedc836dfc3e7bb3cd0f15c5 python-perf-2.6.32-754.35.1.el6.i686.rpm x86_64: 866c2af102c93903443d089ba441788ac36a22d6099b81d91f8ea83bea918ead kernel-2.6.32-754.35.1.el6.x86_64.rpm ce8a1790390c1920d3b3cfe0540658499009c2f2fe9bfaf990fec534197c877b kernel-abi-whitelists-2.6.32-754.35.1.el6.noarch.rpm ca8cf592e13cadd33b5e02b06d0ea52bfd9d451cc9cf01f69e45ffefc985f7dc kernel-debug-2.6.32-754.35.1.el6.x86_64.rpm 7c74392f0655952951c5db0299e59c117691b6139d82ea75b9ba01d80fd97684 kernel-debug-devel-2.6.32-754.35.1.el6.i686.rpm 43fb1f3768d6b5ca543fd050a6e61a2a9ecc116c632b3d33811a054169c93e82 kernel-debug-devel-2.6.32-754.35.1.el6.x86_64.rpm 8cc67aafc0843ca61779e133ec697eaf6f188ecc2fad73c3bd302f612685413c kernel-devel-2.6.32-754.35.1.el6.x86_64.rpm 5068119f93e2d71d2a00ee107db9576671cc73816b7aa80d4020b62db91f0216 kernel-doc-2.6.32-754.35.1.el6.noarch.rpm 21129fbdc585f999c9771847ba5772dbdefd13a825ec0bd979c6806fe216a04b kernel-firmware-2.6.32-754.35.1.el6.noarch.rpm 0e40d0c49d1cf244bed0fda5862d835fe4d67ad75e43ea17723fc4ee2ae8655b kernel-headers-2.6.32-754.35.1.el6.x86_64.rpm fde565954c781bf973bc60b19073dee20c5b91abc5ea374e3ebd00cf5e21aa7b perf-2.6.32-754.35.1.el6.x86_64.rpm e35e2899063cab918a971e79d6e048bc4742163056a031a49e40b64178c6aa0d python-perf-2.6.32-754.35.1.el6.x86_64.rpm Source: 094ad6a7e4512f8b440f8b86e956d1c0d5c7eb7841593ba0d587869c19348a6b kernel-2.6.32-754.35.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Mon, 9 Nov 2020 13:15:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4953 Important CentOS 6 xorg-x11-server Security Update Message-ID: <20201109131506.GA28851(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4953 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4953 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5059ab54170412872f88d5ab194293493b2b765f573fc6f78c0d9ace9f8d2b66 xorg-x11-server-common-1.17.4-18.el6.centos.i686.rpm b37dff9ea4ac00896a290053c3144b2f8690f62e3b23ecac6180b02ec988a5cd xorg-x11-server-devel-1.17.4-18.el6.centos.i686.rpm 75a7add7ad8244095ad2e8700ed2c350aea28ed0e485d1f02e9e3482a3512b4d xorg-x11-server-source-1.17.4-18.el6.centos.noarch.rpm 77101c53e1cc3c2b6b305bf654160798a94a57a76ef9d78c387f82f89a2fb8c7 xorg-x11-server-Xdmx-1.17.4-18.el6.centos.i686.rpm ac9a5141b765d2806881825618cc6e4d0e616598d06ecc299d475df3dd659840 xorg-x11-server-Xephyr-1.17.4-18.el6.centos.i686.rpm 9e064fdb6b18af8f4cc7cc899f39afcddf7998c4e8dd40aa3e39755bd038faca xorg-x11-server-Xnest-1.17.4-18.el6.centos.i686.rpm 60b79c706f5135af0aa04ba11e5c1285be3c8bddcbe41be35137c219b4624e88 xorg-x11-server-Xorg-1.17.4-18.el6.centos.i686.rpm fee0a25a98d360e906683c7370f6a5a8b378ad29a257ae44d1cfde5dc6faccff xorg-x11-server-Xvfb-1.17.4-18.el6.centos.i686.rpm x86_64: e1d71fc00e3ba9364d4d54b30335f5444d9497f0d16bfed52f4b7bd3e9fd5e76 xorg-x11-server-common-1.17.4-18.el6.centos.x86_64.rpm b37dff9ea4ac00896a290053c3144b2f8690f62e3b23ecac6180b02ec988a5cd xorg-x11-server-devel-1.17.4-18.el6.centos.i686.rpm df8d9928f6cdd1cf9fcf0d5fba99f313385e47c6084056ddbf547b1b29e21c78 xorg-x11-server-devel-1.17.4-18.el6.centos.x86_64.rpm 75a7add7ad8244095ad2e8700ed2c350aea28ed0e485d1f02e9e3482a3512b4d xorg-x11-server-source-1.17.4-18.el6.centos.noarch.rpm a9f913a126351611356eeb49a93d39dac03dd6e30b495c709027185f1f1459a7 xorg-x11-server-Xdmx-1.17.4-18.el6.centos.x86_64.rpm 9fcb2539a63002eada6c265e9bd1382847d7546f70ba619228933b89eb4d60e4 xorg-x11-server-Xephyr-1.17.4-18.el6.centos.x86_64.rpm ccb1c58a72bd32faf005e31fb4a5a86bfebe7c9be9cc42095252f5a461dd968b xorg-x11-server-Xnest-1.17.4-18.el6.centos.x86_64.rpm 8f8fcc4e08eb21a9cbd85b98e6d77aab5562a0fc770a54d1cc479c000ff6d1cf xorg-x11-server-Xorg-1.17.4-18.el6.centos.x86_64.rpm f9e253496ee6c40f20c21240a247cb8ad9d17f5be102ce8fc37da84e994e6b89 xorg-x11-server-Xvfb-1.17.4-18.el6.centos.x86_64.rpm Source: 779305950f0a46d80e819083c60ea97e78b6fe9a71d55f29a3c9e67bf1c8ef58 xorg-x11-server-1.17.4-18.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Mon, 9 Nov 2020 13:15:26 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4056 Important CentOS 6 qemu-kvm Security Update Message-ID: <20201109131526.GA28988(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4056 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4056 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 110ff2997980505e2c755ad69dc69c16bb5c233bbcd00c2526ea651016daee45 qemu-guest-agent-0.12.1.2-2.506.el6_10.8.i686.rpm x86_64: a4fd9d13950bd622a0349d761f720561d2837a4d81bba234a59b735b27049627 qemu-guest-agent-0.12.1.2-2.506.el6_10.8.x86_64.rpm 88b1f7d416a92562d3865f3ef460923ca3297f6ab5da6fc1b3e88477fddf31c1 qemu-img-0.12.1.2-2.506.el6_10.8.x86_64.rpm 49da23eb27685168ab6afd80055eefa09fe2c0698c67f71572041aac19e6de94 qemu-kvm-0.12.1.2-2.506.el6_10.8.x86_64.rpm c870e3965e0ef57010331aa8745056aecfa1ecc5688543a1f8bfcdab7fec27fa qemu-kvm-tools-0.12.1.2-2.506.el6_10.8.x86_64.rpm Source: c274069cbe1d9c56734995fb975a166328fab9e017a2727e39267934d0d88741 qemu-kvm-0.12.1.2-2.506.el6_10.8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Mon, 9 Nov 2020 13:16:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4183 Moderate CentOS 6 bind Security Update Message-ID: <20201109131602.GA29212(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4183 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:4183 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 005bce6ed62ad05eb4697d75f3b8e181eba99dd1fce71862efb805d94e6340ae bind-9.8.2-0.68.rc1.el6_10.8.i686.rpm 1a6cd4a05aceb72fad7e3e8ec4498d0163e10789508827d40ca8c30ab2e59ec3 bind-chroot-9.8.2-0.68.rc1.el6_10.8.i686.rpm 1e6db87ec42332ffce17fc56e826634a8bae22a2051b0b1c712588b46c050156 bind-devel-9.8.2-0.68.rc1.el6_10.8.i686.rpm dbc488b4d284cb27407a048a238b1ce875237f0bd77cf652e42e5665efa05b0a bind-libs-9.8.2-0.68.rc1.el6_10.8.i686.rpm 422dbf2898b00c170e44c71945c0f741c3dc7431cd8c6a72afdc13625aca92bd bind-sdb-9.8.2-0.68.rc1.el6_10.8.i686.rpm 64f21d31c6f75149ac5d67928f8ad65a1826a10bffe742cbef95fae0f9e00591 bind-utils-9.8.2-0.68.rc1.el6_10.8.i686.rpm x86_64: 336fdfe427c36ebb58869a32f443fbc9c28631f5732deb2bf375052f7b2d2fb7 bind-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm f2caf6a7899aed82a91d101959b8854a268ed672dd7a003721740160aedf02f7 bind-chroot-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm 1e6db87ec42332ffce17fc56e826634a8bae22a2051b0b1c712588b46c050156 bind-devel-9.8.2-0.68.rc1.el6_10.8.i686.rpm eebc1e9b30eae9aeca2d5959d2bd4512cd48e81c8b94075c5e30e33b0fd17abc bind-devel-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm dbc488b4d284cb27407a048a238b1ce875237f0bd77cf652e42e5665efa05b0a bind-libs-9.8.2-0.68.rc1.el6_10.8.i686.rpm 2977f6759d853ebd83889582bf47f449ccf66545d8f5da4247b0cdbacaef9a9a bind-libs-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm 77b2d4d6aa7275f303891c82ee8e353bd7dd0f670d8b984b30fb1f6c5a279132 bind-sdb-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm d99f0c01e4aac751795ffafe8302efdf6f81c02e6226323ea742a37b417605b4 bind-utils-9.8.2-0.68.rc1.el6_10.8.x86_64.rpm Source: b86b1a45c7822e0869706835aea7a39e1565ab1a24b4d81bd6bcdf99453c8706 bind-9.8.2-0.68.rc1.el6_10.8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Mon, 9 Nov 2020 13:16:20 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:4329 CentOS 6 tzdata BugFix Update Message-ID: <20201109131619.GA29350(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:4329 Upstream details at : https://access.redhat.com/errata/RHBA-2020:4329 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8c4c97c23f0e3349526813a24de47204cbca3e2b2069b77a1dd1ec1349f4b745 tzdata-2020d-1.el6.noarch.rpm 1ea149ffe57a5b85978f87dd493620e1e7a4d2406868a9afa666a58c8f38d4d0 tzdata-java-2020d-1.el6.noarch.rpm x86_64: 8c4c97c23f0e3349526813a24de47204cbca3e2b2069b77a1dd1ec1349f4b745 tzdata-2020d-1.el6.noarch.rpm 1ea149ffe57a5b85978f87dd493620e1e7a4d2406868a9afa666a58c8f38d4d0 tzdata-java-2020d-1.el6.noarch.rpm Source: 7ab212704df6ecdc5bb0117cfa2fc90468cf1a675eb963f904d44a1efb264325 tzdata-2020d-1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Mon, 9 Nov 2020 13:17:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4946 Important CentOS 6 libX11 Security Update Message-ID: <20201109131707.GA29541(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4946 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4946 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2ac64371cfe0b0675ac6e0d137996d04dde05bdc4fb74f049e6f18c684d0c54c libX11-1.6.4-4.el6_10.i686.rpm 42982c0e189057e646b9af3fad89c9590a25107015b11f1d294d7cc087be2d07 libX11-common-1.6.4-4.el6_10.noarch.rpm d1efeb7df384c9de08034a296df0f3b229c75d73b20e97ac95d583ccbf459660 libX11-devel-1.6.4-4.el6_10.i686.rpm x86_64: 2ac64371cfe0b0675ac6e0d137996d04dde05bdc4fb74f049e6f18c684d0c54c libX11-1.6.4-4.el6_10.i686.rpm 4f8aab32eae845104e60b88ad0d42025d7b797215af410e56445ec7615fb1142 libX11-1.6.4-4.el6_10.x86_64.rpm 42982c0e189057e646b9af3fad89c9590a25107015b11f1d294d7cc087be2d07 libX11-common-1.6.4-4.el6_10.noarch.rpm d1efeb7df384c9de08034a296df0f3b229c75d73b20e97ac95d583ccbf459660 libX11-devel-1.6.4-4.el6_10.i686.rpm 128019277a9c9de7c62b5c929e63e2e8590c0f4f07264e7efe12f1ce69acbcc9 libX11-devel-1.6.4-4.el6_10.x86_64.rpm Source: 5ec3db37efff7035c80185164dfb021cc61a3350a98e5229bc4b7b035093e8bb libX11-1.6.4-4.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 8 Date: Mon, 9 Nov 2020 13:18:25 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4330 Important CentOS 6 firefox Security Update Message-ID: <20201109131825.GA29706(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4330 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4330 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a8e5176d70f304e213059440333fe1b5e3a057c081d7b6543f2da13d2887eabe firefox-78.4.0-2.el6.centos.i686.rpm x86_64: a8e5176d70f304e213059440333fe1b5e3a057c081d7b6543f2da13d2887eabe firefox-78.4.0-2.el6.centos.i686.rpm 4d097a2864cc6adebfd0005683826399f45a9c13edeba2b70e5469340401c4ec firefox-78.4.0-2.el6.centos.x86_64.rpm Source: 5672b6694ef983b8fa988f02c618bf300a74fe64533a228f2d7252b736673a4d firefox-78.4.0-2.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 9 Date: Mon, 9 Nov 2020 13:18:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:4947 Important CentOS 6 thunderbird Security Update Message-ID: <20201109131846.GA29818(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:4947 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:4947 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8ec8ac5181b19be92bcc283c2950300f1a2f32afe97ad1da47a757d8febea355 thunderbird-78.4.0-1.el6.centos.i686.rpm x86_64: f477dfe604679c302feae6ee4ebb578e4329ffec6b8d1d63ba701700b4474c2f thunderbird-78.4.0-1.el6.centos.x86_64.rpm Source: 2550e8fa8ec0b4787bd8dcfaa28d9a36c90e7f60f417cf0260a9d12dbbf3f09f thunderbird-78.4.0-1.el6.centos.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 188, Issue 1 ***********************************************

1 0

Android on CentOS 7
by mark 09 Nov '20

09 Nov '20

Should I install android studio, or spin up a vm and use the android .iso? mark

2 1

dbus packages' versions not making sense
by Jason Pyeron 08 Nov '20

08 Nov '20

I have installed 1.12.8-10.el8_2, but when trying to install dbus-devel it is not available for that version, only 1.12.8-9.el8, which is also not available. Suggestions? # yum list | grep dbus dbus.x86_64 1:1.12.8-10.el8_2 @BaseOS dbus-common.noarch 1:1.12.8-10.el8_2 @BaseOS dbus-daemon.x86_64 1:1.12.8-10.el8_2 @BaseOS dbus-glib.x86_64 0.110-2.el8 @anaconda dbus-libs.x86_64 1:1.12.8-10.el8_2 @BaseOS dbus-tools.x86_64 1:1.12.8-10.el8_2 @BaseOS python3-dbus.x86_64 1.2.4-15.el8 @anaconda python3-slip-dbus.noarch 0.6.4-11.el8 @anaconda abrt-dbus.x86_64 2.10.9-11.el8 AppStream dbus-devel.i686 1:1.12.8-9.el8 AppStream dbus-devel.x86_64 1:1.12.8-9.el8 AppStream dbus-glib.i686 0.110-2.el8 BaseOS dbus-glib-devel.i686 0.110-2.el8 AppStream dbus-glib-devel.x86_64 0.110-2.el8 AppStream dbus-libs.i686 1:1.12.8-10.el8_2 BaseOS dbus-x11.x86_64 1:1.12.8-9.el8 AppStream dleyna-connector-dbus.x86_64 0.3.0-2.el8 AppStream libblockdev-lvm-dbus.i686 2.19-12.el8 AppStream libblockdev-lvm-dbus.x86_64 2.19-12.el8 AppStream libdbusmenu.i686 16.04.0-12.el8 AppStream libdbusmenu.x86_64 16.04.0-12.el8 AppStream libdbusmenu-gtk3.i686 16.04.0-12.el8 AppStream libdbusmenu-gtk3.x86_64 16.04.0-12.el8 AppStream libvirt-dbus.x86_64 1.2.0-3.module_el8.2.0+320+13f867d7 AppStream lvm2-dbusd.noarch 8:2.03.08-3.el8 BaseOS policycoreutils-dbus.noarch 2.9-9.el8 BaseOS python3-dbus-client-gen.noarch 0.4-1.el8 AppStream python3-dbus-python-client-gen.noarch 0.7-3.el8 AppStream python3-dbus-signature-pyparsing.noarch 0.03-2.el8 AppStream python3-into-dbus-python.noarch 0.06-2.el8 AppStream python3-pydbus.noarch 0.6.0-5.el8 AppStream qt5-qdbusviewer.x86_64 5.12.5-1.el8.0.1 AppStream sssd-dbus.x86_64 2.2.3-20.el8 BaseOS usbguard-dbus.x86_64 0.7.4-4.el8 AppStream # yum install dbus-devel Last metadata expiration check: 0:06:11 ago on Sun 08 Nov 2020 05:23:17 PM EST. Error: Problem: cannot install the best candidate for the job - nothing provides dbus-daemon = 1:1.12.8-9.el8 needed by dbus-devel-1:1.12.8-9.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # yum install dbus-devel-1.12.8-10.el8_2 Last metadata expiration check: 0:06:22 ago on Sun 08 Nov 2020 05:23:17 PM EST. No match for argument: dbus-devel-1.12.8-10.el8_2 Error: Unable to find a match: dbus-devel-1.12.8-10.el8_2

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss