Re: [CentOS] yumex for CentOS 8.3
On Sun, 2021-05-09 at 08:36 -0400, Jonathan Billings wrote: > On May 8, 2021, at 21:57, Robert G. (Doc) Savage via CentOS < > centos@centos.org> wrote: > > > > On Sat, 2021-05-08 at 13:53 -0600, Frank Cox wrote: > > > > On Sat, 08 May 2021 14:46:58 -0500 > > > > Robert G. (Doc) Savage via CentOS wrote: > > > > > > > > CentOS 8.3, > > > ... > > > > yumex-3.0.15-1.el7.nux.noarch > > > > > > Centos 8.3 is not el7. > > > > Frank, > > > > Well rats. It seems dnfdragora didn't make it into EL or CentOS, I > > guess > > there's no graphical package manager left. > > In addition, it appears you’ve added a Nux yum repo for el7 to your > el8 system, so you need to fix that too. > > -- > Jonathan Billings Jonathan, That nux yum repo was in Frank's system. My system is all C8. --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yumex for CentOS 8.3
On Sat, 2021-05-08 at 13:53 -0600, Frank Cox wrote: > On Sat, 08 May 2021 14:46:58 -0500 > Robert G. (Doc) Savage via CentOS wrote: > > > CentOS 8.3, > ... > > yumex-3.0.15-1.el7.nux.noarch > > Centos 8.3 is not el7. Frank, Well rats. It seems dnfdragora didn't make it into EL or CentOS, I guess there's no graphical package manager left. Thanks. V/R --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] yumex for CentOS 8.3
If yumex is no longer available, please advise. A few minutes ago when 'dnfdragora' failed for CentOS 8.3, I tried: # yumex --root bash: yumex: command not found... Install package 'yumex' to provide command 'yumex'? [N/y] y * Waiting in queue... * Loading list of packages Failed to install packages: Could not depsolve transaction; 1 problem detected: Problem: conflicting requests - nothing provides python-iniparse needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides pycairo needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides dbus-python needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides /usr/bin/python needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides pexpect needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides python-kitchen needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides urlgrabber needed by yumex-3.0.15-1.el7.nux.noarch Is this a long-winded way of telling me to forget it? V/R --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-7-x86_64-dvd-2009.iso is too big for DVD blanks
On Wed, 2021-03-17 at 20:41 +0100, André Verwijs via CentOS wrote: > > I blueray disk (25GB)?? works great :) André, I'm sure it would, but I thought I made it clear that DL or BluRay have never been options in this case. I'm disappointed that the DVD iso was released without any release notes advising it was oversized I finally burned and used a network installation CD and NFS connected to a local mirror of the CentOS 7.9.2011 repository. That option will not be available to me in the future. I have the server in my physical possession for a very short while. After I finish installation and configuration, I will only have remote access. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Samba config question
After setting up /etc/samba/smb.conf and running "testparm" in CentOS 7.9.2011, I have noticed that the list of parameters echoed back for the [global] section do not match those in the smb.conf file. Is this normal? [global] in /etc/samba/smb.conf: unix charset = UTF-8 dos charset = CP932 vfs objs = acl_xattr map acl inherit = yes store dos attributes = yes printing = cups printcap = cups load printers = yes # Network related options workgroup = WORKGROUP server string = Samba Server Version %v netbios name = SERVER01 interfaces = lo eth0 192.168.1.0/24 hosts allow = 127. 192.168.1. # Logging options log file = /var/log/samba/log.%m max log size = 50 # Standalone Server Options security = user passdb backend = tdbsam map to guest = Bad User # Name Resolution wins support = yes dns proxy = yes # Printing options load printers = yes cups options = raw # Filesystem options map archive = no map hidden = no map read only = no map system = no store dos attributes = yes When I subsequently run "testparm", I get a shorter and in some cases different list: [global] in "testparm" output: dos charset = CP932 interfaces = lo eth0 192.168.1.0/24 log file = /var/log/samba/log.%m map to guest = Bad User max log size = 50 printcap name = cups security = USER server string = Samba Server Version %v wins support = Yes idmap config * : backend = tdb cups options = raw hosts allow = 127. 192.168.1 map acl inherit = Yes map archive = No vfs objects = acl_xattr Is this normal behavior for Samba? I am particularly concerned about workgroup = WORKGROUP missing in the "testparm" output. V/R --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS-7-x86_64-dvd-2009.iso is too big for DVD blanks
On Sun, 2021-03-14 at 21:31 -0400, John Plemons wrote: > Sounds like you need to use a dual layer DVD disc, it is double the > capacity. John, Wrong answer. The server's optical drive doesn't support double-layer disks. The CentOS developers made a mistake on their DVD iso, and they need to fix it. --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-7-x86_64-dvd-2009.iso is too big for DVD blanks
I need help from someone experienced with the CentOS bug tracking system. I gotta say it is one of the most complicated and imposing front ends I've ever seen. Could anyone familiar with it please file a bug on my behalf? Particulars: "CentOS 7.9.2009 DVD iso image too large" ISO image: CentOS-7-x86_64-DVD-2009.iso 4.7GB raw CD image Wed Nov 4 05:37:25 2020 Burners: Both K3B and Brasero Media: Both DVD-R and DVD+R single-layer disks iso image: 4,712,300,544 bytes User Anthony F McInerney advises Wikipedia says DVD-R capacity: 4,707,319,808 bytes (max) I have tried burning this same iso image on two different machines: a CentOS 7.9 server and a Fedora 33 laptop. Same failure on both. We need to ask the developers to make a re-spin that's about 5MB smaller. And before someone suggests it, the 2010-vintage server I'm trying to install CentOS on does not support booting from a thumb drive, so that option is not available. Thanks, --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Sun, 2021-01-31 at 08:26 +0100, José María Terry Jiménez wrote: > > Do you know guest access to shares is disabled in windows 10? > > https://docs.microsoft.com/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default The error message this link says I should be seeing is not the one I'm getting, so I don't think this is the problem. "You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network." --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Fri, 2021-01-29 at 06:32 -0600, Chris Weisiger wrote: > > I’m not exactly sure if this may be the same issue I experienced but > Google smb1 and windows10 . Apparently Microsoft removed support for > Ann version 1 from windows 10 after one of the release updates > > https://go.Microsoft.com/fwlink/?linkid=852747 Chris, I added the following line to [global], but it didn't fix the problem. server max protocol = SMB2 --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Fri, 2021-01-29 at 04:40 +, Strahil Nikolov wrote: > I know from experience that you need to decide how you control access > and you got 2 options: > > - Linux directory is set to 777 and all control is in samba > - Linux directory is set as if unix user will access it and you use > the sam uid/gid for both client and server accounts (AD, FreeIPA, > LDAP) > > What is your settings right now ? > > Best Regards, > Strahil Nikolov Strahil, 777 and ownership of /tank/Windows is nobody:nobody. It's actually an empty directory right now. Not using AD/FreeIPA/LDAP. --Robert Savage Fairview Heights, IL > > > On Thu, Jan 28, 2021 at 7:57, Robert G. (Doc) Savage via CentOS > > wrote: > > On Tue, 2021-01-19 at 17:18 +0100, Götz Reinicke wrote: > > > > > > Anything in the samba logs? May be SELinux/Firewall issues? > > > > Götz, > > > > Unfortunately, no. > > > > The nmbd log verifies that the fileserver's samba service is the > > local > > master browser for WORKGROUP on both eth0 and virbr0. > > > > [2021/01/17 19:02:22.190795, 0] > > > > ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2 > > ) > > * > > Samba name server LIONSTORE is now a local master browser for > > workgroup > > WORKGROUP on subnet 192.168.1.20 > > * > > > > [2021/01/17 19:02:22.191085, 0] > > > > ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2 > > ) > > * > > Samba name server LIONSTORE is now a local master browser for > > workgroup > > WORKGROUP on subnet 192.168.122.1 > > * > > > > The samba smbd log simply reports the connection denials: > > > > [2021/01/17 23:07:40.304626, 0] > > ../../lib/util/access.c:371(allow_access) > > Denied connection from 192.168.1.30 (192.168.1.30 > > > > There's nothing in the SELinux logs for that date. > > > > I checked firewall-config on the storage server and verified that > > the > > samba service is allowed (but not samba-client or samba-dc). > > > > Is there a really comprehensive setup checklist available for > > setting > > up samba on CentOS? The partial how-tos I've been able to find are > > obviously not enough. I'm looking for completer smb.conf setup, > > firewall settings, required services, directory permissions, > > accounts, > > and anything else that's required. I'm running up against very > > unhelpful roadblocks that seem to indicate a critical permissions > > problem but nothing specific. > > > > V/R > > --Doc Savage > > Fairview Heights, IL > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Tue, 2021-01-19 at 17:18 +0100, Götz Reinicke wrote: > > Anything in the samba logs? May be SELinux/Firewall issues? Götz, Unfortunately, no. The nmbd log verifies that the fileserver's samba service is the local master browser for WORKGROUP on both eth0 and virbr0. [2021/01/17 19:02:22.190795, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.20 * [2021/01/17 19:02:22.191085, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 * The samba smbd log simply reports the connection denials: [2021/01/17 23:07:40.304626, 0] ../../lib/util/access.c:371(allow_access) Denied connection from 192.168.1.30 (192.168.1.30 There's nothing in the SELinux logs for that date. I checked firewall-config on the storage server and verified that the samba service is allowed (but not samba-client or samba-dc). Is there a really comprehensive setup checklist available for setting up samba on CentOS? The partial how-tos I've been able to find are obviously not enough. I'm looking for completer smb.conf setup, firewall settings, required services, directory permissions, accounts, and anything else that's required. I'm running up against very unhelpful roadblocks that seem to indicate a critical permissions problem but nothing specific. V/R --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] mcelog service error flagged in Cockpit
Whenever I log into Cockpit, it flags mcelog as a service failure-to- start failure. systemctl confirms this. # systemctl status mcelog * mcelog.service - Machine Check Exception Logging Daemon Loaded: loaded (/usr/lib/systemd/system/mcelog.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-01-10 18:06:36 CST; 1 weeks 2 days ago Main PID: 21959 (code=exited, status=1/FAILURE) Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: Started Machine Check Exception Logging Daemon. Jan 10 18:06:36 lionstore.protogeek.org mcelog[21959]: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jan 10 18:06:36 lionstore.protogeek.org mcelog[21959]: CPU is unsupported Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: mcelog.service: Main process exited, code=exited, status=1/> Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: mcelog.service: Failed with result 'exit-code'. A search through BZ indicates mcelog hasn't been supported on AMD processors s since family 21. How do I tell Cockpit to use this alternative module? Perhaps more importantly, why doesn't Cockpit automatically set up this module when it's installed on an AMD system? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Tue, 2021-01-19 at 17:18 +0100, Götz Reinicke wrote: > Hi, > > > Am 18.01.2021 um 20:08 schrieb Robert G. (Doc) Savage via CentOS > > : > > > > I'm > > > following > https://www.linuxbabe.com/redhat/set-up-samba-server-on-centos-8-rhel-8-for-file-sharing > > to set up Samba 4.12.3-12 on my Storinator fileserver running > > CentOS > > 8.3. I am trying to share out /tank/Windows/ as a Samba share: ... > > > > When I try to map network drive from my Windows 10 PC using the > > graphical File Explorer, it asks me for my username and password. > > It > > doesn't accept my password. When I try to map it at the CMD cli, I > > get: > > > > C:\> net use S: \\192.168.1.20\public\ > > System error 67 has occurred. > > > > The network name cannot be found. > > > > Could this be a network browsing problem in Samba? What have I > > missed? > > Anything in the samba logs? May be SELinux/Firewall issues? Götz, Unfortunately, no. The nmbd log verifies that the fileserver's samba service is the local master browser for WORKGROUP on both eth0 and virbr0. [2021/01/17 19:02:22.190795, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.20 * [2021/01/17 19:02:22.191085, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 * The samba smbd log simply reports the connection denials: [2021/01/17 23:07:40.304626, 0] ../../lib/util/access.c:371(allow_access) Denied connection from 192.168.1.30 (192.168.1.30 There's nothing in the SELinux logs for that date. I checked firewall-config on the storage server and verified that the samba service is allowed (but not samba-client or samba-dc). --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Samba setup
I'm following https://www.linuxbabe.com/redhat/set-up-samba-server-on-centos-8-rhel-8-for-file-sharing to set up Samba 4.12.3-12 on my Storinator fileserver running CentOS 8.3. I am trying to share out /tank/Windows/ as a Samba share: # ls -al /tank total 61 drwxr-xr-x. 6 root root 7 Dec 26 10:43 Backups drwxr-xr-x. 6 root root 6 Dec 4 22:47 Repos drwxrwxrwx. 2 doc doc 4 Dec 28 14:01 VMs drwxrwxrwx. 2 root root 2 Jan 17 17:04 Windows My /etc/samba/smb.conf file is set up as follows: # testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] printcap name = cups security = USER idmap config * : backend = tdb cups options = raw hosts allow = 192.168.0 ... [public] comment = public share, no need to enter username and password guest ok = Yes path = /tank/Windows read only = No When I try to map network drive from my Windows 10 PC using the graphical File Explorer, it asks me for my username and password. It doesn't accept my password. When I try to map it at the CMD cli, I get: C:\> net use S: \\192.168.1.20\public\ System error 67 has occurred. The network name cannot be found. Could this be a network browsing problem in Samba? What have I missed? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Have lost access to ZFS pools with latest CentOS 8 kernels
With the release of the vmlinuz-4.18.0-240.x and vmlinuz- 4.18.0.193.19.x kernels, ZoL cannot connect with a ZFS pool. I'm not 100% sure, but I believe the last CentOS 8 kernel to work with ZFS 0.8.5 was 4.18.0.6.x. Obviously CentOS does not support ZFS, so this means the ZoL folks must find and fix the problem. Otherwise, I think Fedora 33 is the only choice we have for hosting ZFS. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 future
On Tue, 2020-12-08 at 11:58 -0500, Satish Patel wrote: > Folks, > > What is going on here > https://blog.centos.org/2020/12/future-is-centos-stream/ > > CentOS 8's future is not looking bright. Recently deployed CentOS8 on > my production workload and now hearing this. What do other folks > think > about this? Speaking only for myself, I am ready to give up on CentOS (and Red Hat) entirely. Fedora meets all my clients' needs with none of the chaos. I shall miss the stability of past CentOS releases, much as I did those of Scientific Linux. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] /dev/mapper/cl-root filesystem corrupted?
On Mon, 2020-12-07 at 15:43 +1100, Anthony K wrote: > On 7/12/20 12:20 pm, Robert G. (Doc) Savage via CentOS wrote: > > A client's (truly ancient) file server running CentOS 7 suddenly > > started misbehaving, and I believe the ext4 filesystem on > > /dev/mapper/cl-root may be corrupted. A reboot fails with a file > > system > > check and drops me into maintenance mode. I tried booting from a > > live > > C7 DVD and as root running e2fsck. It complains that the superblock > > could not be read and suggests running "e2fsck -b 8193 ". > > That > > also fails. > > > > Is there a way to more forcefully "encourage" e2fsck to do its job > > without totally destroying that filesystem? > > > > --Doc Savage > > Fairview Heights, IL > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > I'd say first make sure the hardware is in good order. If you have a > faulty motherboard, CPU, and/or RAM, you might not be able to do > anything and could end up losing precious data if you manage to > forcefully "encourage" it. Anthony, There are no apparent hardware problems, but as I said this machine is ancient. The hardware is a Dell T110 server (https://www.dell.com/downloads/emea/products/t110_spec_sheet.pdf) orig inally purchased circa 2010. It came with Windows Small Business Server, which I replaced with CentOS 7 when it was released in 2014. I also replaced the original Windows-only RAID card in 2014 with a Dell update that supports a 4 x 500GB Linux software RAID5. All other hardware is original, and I hate to think what the hard drive bearings must look like after more than 87,000 power-on hours. I might be able to use a C7 Live DVD with the external eSATA interface to dd the contents of the boot drive to a spare, but that might just copy a damaged LVM that still resists e2fsck. --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] /dev/mapper/cl-root filesystem corrupted?
A client's (truly ancient) file server running CentOS 7 suddenly started misbehaving, and I believe the ext4 filesystem on /dev/mapper/cl-root may be corrupted. A reboot fails with a file system check and drops me into maintenance mode. I tried booting from a live C7 DVD and as root running e2fsck. It complains that the superblock could not be read and suggests running "e2fsck -b 8193 ". That also fails. Is there a way to more forcefully "encourage" e2fsck to do its job without totally destroying that filesystem? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Update from 7 to 8
On Mon, 2020-11-23 at 10:44 -0500, Jerry Geis wrote: > 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 ? > Jerry, There is a formally supported upgrade from RHEL 7 to 8, but unfortunately there is none for CentOS 7 to 8. The reason for this is based on the totally new repository structure Red Hat used for v8. It's different enough that an exact counterpart to the RHEL 7>8 upgrade script hasn't been compiled, tested, and supported. Your only choice is to back up everything and install CentOS 8 from scratch. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] ZFS fails with latest C8 kernel
As if last weekend's UEFI debacle wasn't bad enough, it now seems the latest C8 kernel (4.18.0-193.14.2) is incompatible with the current ZFSOnLinux packages (0.8.4-1). When booted to the latest kernel, ZFS is inaccessible on my C8 storage server. When I back off to the prior kernel (4.18.0-193.6.3), all is well. If a local ZFS system is unavailable to the C8 kernel support folks, I'll be happy to assist them by volunteering my system as a lab rat. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
-Original Message- From: Stephen John Smoogen Reply-To: CentOS mailing list To: CentOS mailing list Subject: Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable Date: Sun, 2 Aug 2020 10:57:49 -0400 On Sun, 2 Aug 2020 at 10:20, david wrote: > > I agree it is a lot of shorthand because of expectations. In the endwe (the list) don't know what you have on your system or what state itis in. In order to get that information to help we would need you totry the following: 1. boot using a working USB/cdrom/netboot path and installer2. choose the rescue mode3. have the rescue mount the disks as local and chroot into thesystem. << if possible have the system also bring up networking >> Thenyum list kernel shim grub2 mokutil John, I have a CentOS 8.2.2004 system running on an EPYC-equipped SuperMicro motherboard. I assume it uses EFI boot. I have it set to auto-update with cron.daily, so it almost certainly has the buggy package(s) installed. I'm loath to try rebooting it just to see. When I run "yum list kernel shim grub2 mokutil" all I get back are the three installed kernel packages. Reverting to the old fashioned "rpm -qa | grep kernel-4 ; rpm -qa | grep shim ; rpm -qa | grep grub2 ; rpm -qa | grep mokutil" I get: kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-193.14.2.el8_2.x86_64 kernel-4.18.0-193.6.3.el8_2.x86_64 grub2-tools-2.02-87.el8_2.x86_64 grub2-pc-2.02-87.el8_2.x86_64 grub2-pc-modules-2.02-87.el8_2.noarch grub2-common-2.02-87.el8_2.noarch grub2-tools-efi-2.02-87.el8_2.x86_64 grub2-tools-minimal-2.02-87.el8_2.x86_64 grub2-tools-extra-2.02-87.el8_2.x86_64 I apparently do not have either shim or mokutil packages installed. I'm not sure what this means. Am I not using EFI boot? I have local copies of the earlier v2.02-81 grub2 packages. Would it be worthwhile to replace my v2.02-87 grub2 packages, then add this line to /etc/dnf/dnf.conf: exclude=grub shim mokutil as previously advised? Or should I just leave well enough alone and wait for tonight's auto-update to fix things? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ailing MATE desktop [SOLVED]
On Thu, 2020-05-14 at 16:12 -0400, Jon LaBadie wrote: > On Thu, May 14, 2020 at 05:24:13AM -0500, Robert G (Doc) Savage via > CentOS wrote: > > > > If you look at the listing attached to my last message, you'll > > > > see > > > > three different groups of packages: > > > > > > > > Removing: > > > > xxx > > > > Removing dependent packages: > > > > xxx > > > > Removing unused dependencies: > > > > xxx > > > > > > > > I don't understand the meaning of the last group of "unused > > > > dependencies". > > > > > As I understand them, dependent packages are dependent on MATE. > If MATE goes away they are useless. > > Dependencies are packages MATE is dependent upon. Other things > may also be dependent on those packages. > > Unused dependencies are things that if MATE were removed have > no other packages dependent on them. So MAYBE they are no longer > needed and can be removed. > > But be careful with these. Nothing may depend upon them, but you > may use them. First in your list is ImageMagick. You may use this > whether MATE is there or not. > > The "--noautoremove option prevents removal of "unused dependencies". > You can then take your list and see which you really don't need and > remove them separately. > > Jon Jon, You have nailed the obscure but critical element for removing a damaged MATE installation. The --noautoremove option made everything else possible: # dnf erase *mate* --noautoremove --skip-broken This removes all of the front line MATE packages and their direct dependencies. All are in the COPR repository. I just ran that command followed by a fresh re-install of MATE 1.22 using the instructions at https://copr.fedorainfracloud.org/coprs/stenstorp/MATE/. When I logged out of GNOME3 and logged back in using the re-installed MATE, all is well again. I think I owe you a beer or two Jon. Thanks very much. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ailing MATE desktop
On Thu, 2020-05-14 at 08:18 +0200, Simon Matter wrote: > > On Wed, 2020-05-06 at 10:26 -0500, Robert G (Doc) Savage via CentOS > > wrote: > > > On Tue, 2020-05-05 at 19:25 -0500, Robert G (Doc) Savage via > > > CentOS > > > wrote: > > > > I'm about ready to run "dnf erase *mate*" and try re-installing > > > > MATE > > > > from scratch from the GNOME3 desktop. Is that possible without > > > > ripping > > > > the heart out of C8 by deleting other critical packages? > > > > > > I've attached a capture of "dnf erase *mate*" that shows the 104 > > > packages that would be removed. It looks safe enough, but if > > > there's > > > a > > > a better way to fix the problem I'd rather try that. > > > > Having gotten no responses, I'm about ready to plunge ahead and try > > removing MATE v1.22 with dnf, then do a fresh reinstall of all > > packages. However, I'm unsure about the safest way to proceed. > > > > If you look at the listing attached to my last message, you'll see > > three different groups of packages: > > > > Removing: > > xxx > > Removing dependent packages: > > xxx > > Removing unused dependencies: > > xxx > > > > I don't understand the meaning of the last group of "unused > > dependencies". > > > > Is there a manual, more surgical way to remove packages that won't > > rip > > the overall CentOS 8.1 installation apart? For example, is there a > > way > > (perhaps a for loop) that deletes only the first two package > > groups? > > All of those are from the COPR repository. Removing them should > > cause > > no problems. But the third group (unused) includes several > > @AppStream, > > @epel, and even one @PowerTools package. > > > > Any dnf gurus please weigh in here. > > I'm not sure why dnf is eager to remove more than what you want. I > think > it's an option you can use to make it remove only what is required, > and > unused packages are not touched. > > However, in such cases, what I did is: > - check the yum/dnf log for which packages were installed by the time > I > installed something with lot of dependencies. Make a list of all > RPMs. > - use plain 'rpm -e --test ' and see what it does. > - if okay remove '--test' and remove the RPMs. > > Regards, > Simon Simon, I took the "dnf erase *mate*" output list and removed everything but the package names. This gave me a 104 package list "trial.txt". With that I built a for loop at the command line: # for i in `cat trial.txt` > do > rpm -e --test $i > done I've attached the list of all packages identified by the original "dnf erase *mate*" exercise. This took a lot of manual editing to strip out all but the package names to get the list file trial.txt. Using that in the for loop I captured the output in trial-output.txt. This will take me some tedious cross checking to make sure only the packages in trial.txt are affected. --Doc Savage Fairview Heights, IL libmatekbd libmatemixer libmateweather libmateweather-data mate-applets mate-backgrounds mate-calc mate-control-centerM mate-control-center-filesystem mate-desktop mate-desktop-libs mate-dictionary mate-disk-usage-analyzer mate-icon-theme mate-media mate-menus mate-menus-libs mate-menus-preferences-category-menu mate-notification-daemon mate-panel mate-panel-libs mate-polkit mate-power-manager mate-screensaver mate-screenshot mate-search-tool mate-session-manager mate-settings-daemon mate-system-log mate-system-monitor mate-terminal mate-themes mate-user-admin mate-user-guide mate-utils-common atril-caja atril-thumbnailer caja-actions caja-image-converter caja-open-terminal caja-sendto caja-wallpaper caja-xattr-tag engrampa eom marco mozo pluma seahorse-caja ImageMagick ImageMagick-libs LibRaw OpenEXR-libs atril atril-libs caja caja-actions-doc caja-core-extensions caja-extensions-common caja-schemas crda djvulibre-libs enchant fftw-libs-double gamin graphviz group-service gtk-murrine-engine ilmbase iw libXScrnSaver libXaw libXpresent libappindicator-gtk3 libcryptui libdbusmenu libdbusmenu-gtk3 libgnome-keyring libindicator-gtk3 libraqm libwmf-lite marco-libs mathjax mathjax-ams-fonts mathjax-caligraphic-fonts mathjax-fraktur-fonts mathjax-main-fonts mathjax-math-fonts mathjax-sansserif-fonts mathjax-script-fonts mathjax-size1-fonts mathjax-size2-fonts mathjax-size3-fonts mathjax-size4-fonts mathjax-stixweb-fonts mathjax-typewriter-fonts mathjax-vector-fonts mathjax-winchrome-fonts mathjax-winie6-fonts pluma-data texlive-lib web-assets-filesystem wireless-tools xorg-x11-fonts-ISO8859-1-100dpi # for i in `cat trial.txt` &
Re: [CentOS] Ailing MATE desktop
On Wed, 2020-05-06 at 10:26 -0500, Robert G (Doc) Savage via CentOS wrote: > On Tue, 2020-05-05 at 19:25 -0500, Robert G (Doc) Savage via CentOS > wrote: > > I'm about ready to run "dnf erase *mate*" and try re-installing > > MATE > > from scratch from the GNOME3 desktop. Is that possible without > > ripping > > the heart out of C8 by deleting other critical packages? > > I've attached a capture of "dnf erase *mate*" that shows the 104 > packages that would be removed. It looks safe enough, but if there's > a > a better way to fix the problem I'd rather try that. Having gotten no responses, I'm about ready to plunge ahead and try removing MATE v1.22 with dnf, then do a fresh reinstall of all packages. However, I'm unsure about the safest way to proceed. If you look at the listing attached to my last message, you'll see three different groups of packages: Removing: xxx Removing dependent packages: xxx Removing unused dependencies: xxx I don't understand the meaning of the last group of "unused dependencies". Is there a manual, more surgical way to remove packages that won't rip the overall CentOS 8.1 installation apart? For example, is there a way (perhaps a for loop) that deletes only the first two package groups? All of those are from the COPR repository. Removing them should cause no problems. But the third group (unused) includes several @AppStream, @epel, and even one @PowerTools package. Any dnf gurus please weigh in here. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Ailing MATE desktop
On Tue, 2020-05-05 at 19:25 -0500, Robert G (Doc) Savage via CentOS wrote: > > I'm about ready to run "dnf erase *mate*" and try re-installing MATE > from scratch from the GNOME3 desktop. Is that possible without > ripping > the heart out of C8 by deleting other critical packages? I've attached a capture of "dnf erase *mate*" that shows the 104 packages that would be removed. It looks safe enough, but if there's a a better way to fix the problem I'd rather try that. --Doc Savage Fairview Heights, IL # dnf erase *mate* Modular dependency problems: Problem 1: conflicting requests - nothing provides module(perl:5.26) needed by module perl-DBD-MySQL:4.046:8010020191114030811:073fa5fe-0.x86_64 Problem 2: conflicting requests - nothing provides module(perl:5.26) needed by module perl-DBD-SQLite:1.58:8010020191114033549:073fa5fe-0.x86_64 Problem 3: conflicting requests - nothing provides module(perl:5.26) needed by module perl-DBI:1.641:8010020191113222731:16b3ab4d-0.x86_64 Dependencies resolved. = Package ArchitectureVersion Repository Size = Removing: libmatekbdx86_64 1.24.0-1.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 659 k libmatemixer x86_64 1.24.0-1.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 868 k libmateweatherx86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 192 k libmateweather-data noarch 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 114 M mate-applets x86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 38 M mate-backgrounds noarch 1.24.0-1.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 20 M mate-calc x86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 6.2 M mate-control-center x86_64 1.22.2-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 14 M mate-control-center-filesystemx86_64 1.22.2-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE0 mate-desktop x86_64 1.24.0-3.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 186 k mate-desktop-libs x86_64 1.24.0-3.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 3.0 M mate-dictionary x86_64 1.22.2-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 23 M mate-disk-usage-analyzer x86_64 1.22.2-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 23 M mate-icon-theme noarch 1.24.0-1.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 28 M mate-mediax86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 1.5 M mate-menusx86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 430 k mate-menus-libs x86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 134 k mate-menus-preferences-category-menu x86_64 1.24.0-2.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 3.2 k mate-notification-daemon x86_64 1.22.1-1.el8 @copr:copr.fedorainfracloud.org:stenstorp:MATE 527 k mate-panel
Re: [CentOS] Ailing MATE desktop
On Tue, 2020-05-05 at 10:32 -0600, Frank Cox wrote: > On Tue, 5 May 2020 05:30:26 -0400 > Eddie O'Connor wrote: > > > Are there .conf files for the desktop?what about > > logs?something's > > got to be amiss somewhereand Linux always complains when it > > is.in > > logs. Just wondering out loud... > > What happens if he sets up a new user? Does the desktop work then? Frank, For some reason I didn't get Eddie O'Connor's message. If there are .conf files they're hiding pretty well. And as I said, systemctl -ex, journalctl, and dmesg don't show any errors. If you search for "troubleshooting MATE desktop" I think you'll be disappointed in how little help there is. I guess that's to be expected of a desktop that "just works". Yours is an excellent suggestion. If the new user works, the problem would be a fault in my account's configuration. If not, then it's the MATE system. So I created a new user "test", reset the machine, and logged into the MATE desktop as the new user. Unfortunately I see the exact same misbehavior. I'm about ready to run "dnf erase *mate*" and try re-installing MATE from scratch from the GNOME3 desktop. Is that possible without ripping the heart out of C8 by deleting other critical packages? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Ailing MATE desktop
I need some C8 troubleshooting help with MATE. I'm building a ZFS storage server with a SuperMicro H11SSL motherboard, EPYC 7232 CPU, and 32 GB ECC SDRAM. I installed CentOS 8.1.1911 from the iso as soon as it was released. I'm using the on-board ASPEED VGA video. I installed MATE v1.22 from https://copr.fedorainfracloud.org/coprs/stenstorp/MATE/. The following packages are installed: libmateweather-data-1.24.0-2.el8.noarch libmatemixer-1.24.0-1.el8.x86_64 mate-desktop-libs-1.24.0-3.el8.x86_64 mate-terminal-1.24.0-2.el8.x86_64 mate-themes-3.22.21-1.el8.noarch mate-panel-libs-1.22.2-1.el8.x86_64 mate-desktop-1.24.0-3.el8.x86_64 mate-settings-daemon-1.22.1-2.el8.x86_64 mate-polkit-1.24.0-2.el8.x86_64 mate-notification-daemon-1.22.1-1.el8.x86_64 mate-media-1.24.0-2.el8.x86_64 mate-power-manager-1.22.2-1.el8.x86_64 mate-system-log-1.22.2-2.el8.x86_64 libmateweather-1.24.0-2.el8.x86_64 libmatekbd-1.24.0-1.el8.x86_64 mate-utils-common-1.22.2-2.el8.noarch mate-disk-usage-analyzer-1.22.2-2.el8.x86_64 mate-user-guide-1.24.0-1.el8.noarch mate-menus-preferences-category-menu-1.24.0-2.el8.x86_64 mate-dictionary-1.22.2-2.el8.x86_64 mate-menus-1.24.0-2.el8.x86_64 mate-session-manager-1.24.0-1.el8.x86_64 mate-backgrounds-1.24.0-1.el8.noarch mate-search-tool-1.22.2-2.el8.x86_64 mate-panel-1.22.2-1.el8.x86_64 mate-system-monitor-1.24.0-1.el8.x86_64 mate-applets-1.24.0-2.el8.x86_64 mate-control-center-1.22.2-2.el8.x86_64 mate-icon-theme-1.24.0-1.el8.noarch mate-control-center-filesystem-1.22.2-2.el8.x86_64 mate-menus-libs-1.24.0-2.el8.x86_64 mate-user-admin-1.5.1-3.el8.x86_64 mate-calc-1.24.0-2.el8.x86_64 mate-screenshot-1.22.2-2.el8.x86_64 mate-screensaver-1.24.0-2.el8.x86_64 About two weeks ago following a reset, after a normal login an incomplete MATE desktop appeared. The background is black. There is no visible mouse, although there is some ghostly pixel movement in the top toolbar when what should be the mouse cursor floats over each of those toolbar icons. I can hit Enter and start whatever app the ghost cursor is over, and the mouse works only within that app's window. I'm a long-time user of MATE ever since GNOME3 was released, but until now I've never had any problems with it. I have no idea where to start troubleshooting. I've looked in journalctl, systemctl, and dmesg, but found nothing obvious. There's nothing in the MATE wiki to help. I'm open to any suggestions where to start looking. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] C8 network install
I'm building a new storage server. I was unable to use the CentOS-8- x86_64-1905-dvd1.iso image written to a 256GB thumb drive. It kept failing the integrity check. I had to use the much smaller CentOS-8- x86_64-1905-boot.iso image and do a network install from a mirror site. That's a first for me. Even though I selected "Server with GUI", the resulting installation boots to a text prompt. I've installed the GNOME and GNOME Applications groups, and I can get to them by typing 'startx'. How do I change this behavior and make it boot directly to a graphical desktop? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Renaming virtio devices names on CentOS 8 VM guest
On Fri, 2020-02-21 at 13:03 +0100, Gianluca Cecchi wrote: > On Fri, Feb 21, 2020 at 10:57 AM Chris Card > wrote: > > > I have built a CentOS 8 base image from a kickstart, for use in > > OpenStack. > > This image boots fine but the problem I have is that I can't stop > > udev > > from renaming the network device from eth0 to ens. > > I have /etc/sysconfig/network-scripts/ifcfg-eth0 with the correct > > HWADDR > > defined in it, and have set net.ifnames=0 and biosdevname=0 in the > > grub > > configuration, but nothing I have tried has stopped the renaming. > > I found this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1660179 > > which describes the same situation, but the comments in the bug > > didn't help. > > I'd like to keep the eth* device names because we have various heat > > templates and other scripts which assume that the network devices > > are > > called eth0, eth1 etc. > > Any ideas? Is this even possible with a CentOS 8 VM guest? > > > > Chris > > > > > It is strongly discouraged, for Openstack and when you have more than > one > adapter. See here if you have access: > https://access.redhat.com/solutions/2435891 > > Anyway perhaps you could manage order of names customizing > /usr/lib/systemd/network/99-default.link > At least as described here: > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking > but I never tried it > HIH, > Gianluca Gianluca, What you are trying to do is documented at https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-disabling_consistent_network_device_naming You need to edit the GRUB_CMDLOINE_LINUX line in /etc/default/grub as shown below; ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel_7/swap rd.luks.uuid=luks- cc387312-6da6-469a-8e49-b40cd58ad67a crashkernel=auto vconsole.keymap=us vconsole.font=latarcyrheb-sun16 rd.lvm.lv=rhel_7/root rhgb quiet net.ifnames=0 biosdevname=0" GRUB_DISABLE_RECOVERY="true" Then for an EUFI system run this: ~]# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg Reboot and you should have your old eth0, eth1, etc. naming convention back again. WATCH YOUR TYPING. BE CAREFUL NOT TO OMIT OR ADD EXTRANEOUS SPACES !!! Hope this helps. --Doc SavageFairview Heights, IL 62208-3432 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Need help modding src.rpms to generate complete SAMBA AD DC binary RPMs for CentOS 8
When RHEL8 and CentOS8 were released, I was looking forward to setting up SAMBA as a AD DC server for CentOS8. But when I lifed the hood on the samba.spec file I found the option to build the samba-dc binary rpm has been disabled for rhel family builds. Apparently Red Hat does not want to support a unified SAMBA AD DC environment. I believe we have all of the componentns needed to set up a fully up-to-date samba-dc binary. But it's been decades since I last rolled up my sleeves with my hardbound copy of "Maximum RPM" and built custom binary rpms. Has anyone already done this as a COPR or similar project? Failing that, I'm willing to work with anyone with more up-to-date rpmbuild tools to create and document the process. --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 Mate?
On Thu, 2019-10-17 at 10:59 -0400, Fred Smith wrote: > On Thu, Oct 17, 2019 at 09:08:28AM -0500, Johnny Hughes wrote: > > On 9/24/19 2:41 PM, Frank Cox wrote: > > > Without wanting to sound too pushy, I'm wondering if there is any > > > update on the status of Mate now that Centos 8 has been released? > > > > > > I would love to jump on C8 and start playing with it, but the > > > lack of Mate is kind of a showstopper for me at the moment. > > > > > > > Is gnome3 really that bad :D > > > > I decided to just bite the bullet and shift to real gnome3 (and not > > the > > classic) about 4 years ago. It waas different and took some time > > to > > learn .. BUT .. I can do everything I need to do now. > > > > I like both mate and cinnamon .. so I am not knocking either one. I > > just > > think people might be well server switching to a 'supported' > > desktop in > > the longer run. > > > > Again .. don't get me wrong .. it's open source, so do what makes > > you > > happy :D > > > > Johnny, I'm sure it can be learned, apparently lots of people have > done > so and are now happy(for some values of happy) with it. > > That is just something I don't feel like doing. I'm not against > change, > but the changes in Gnome 3 seemed to me to be needlessly adding pain > and difficulty to what had been a perfectly usable desktop. Every > time > I install a new CentOS I grit my teeth at having to remember/figure > out > enough of it to get me thru to the point where I can use a friendly > UI. > > Yes, I should stop being a luddite and learn it. but, y'know, I just > can't bring myself to deal with the pain. As a geezer, I guess I'm > kinda set in my ways. :) > > Just to get the Mate installed on C8 (as was posted here recently > where/how to do it) was more pain that I enjoyed going through. Now, > I'm sure there are simple solutions to these issues, but I just don't > want to have to stop what I'm doing to google for them... anyway, > I had firefox open and wanted a terminal window. couldn't figure out > how to set it up so I could see both at the same time. Once I > maximized > FF I couldn't figure out how to get it to not eat the entire screen > --no > clicky buttons on the top-right of the window, so I ended up using > the > left-most item at the top of the window (forget what it is named...) > to > choose which window I wanted in front. tedious but livable. > > but now I don't have to do that 'cause Mate works great! > > And thanks to you, Johnny, and your companions/associates for all the > many YEARS of work you've all put in on CentOS. Even though I gripe > and > complain about Gnome3, I really do appreciate all you've done! > > Fred What Fred said, Johnny. I was very happy with GNOME v2 until its developers decided to take magic mushrooms or whatever and shuffled off to Oz. If you want to use GNOME v3, great. But this thread is probably not the best place to trumpet how much you like GNOME v3. A fairly substantial group of us is trying to restore a capability (MATE) that Red Hat deliberately took away from us. I hope when you find yourself on the wrong side of a Red Hat decision you are lucky enough to have a talented and resourceful group to help you recover. --Doc Savage ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 Mate?
On Wed, 2019-09-25 at 15:25 +0200, Ljubomir Ljubojevic wrote: > > As of now, I have a working MATE DM on CentOS 8. It's a hack though, > I > used Fedora repositories. But that means compiling MATE in EPEL > should > be straightforward, just recompile Fedora 28 packages. > > > I used Fedora 28 repo file and Fedora 28 GPG keys (links are > bellow), > unpacked then to proper directory and in Fedora repo files I changed > "$releasever" to "28". > I also installed yum-plugin-priorities and in all CentOS repo's added > "priority=1" and in all Fedora repos added "priority=2". > > Then I ran following commands (something like this, I experimented > some): > > > yum install python2-six > yum install mate* -x mate*devel* -x mate-menu > yum groupinstall "MATE" --skip-broken > yum groupinstall "MATE Desktop" --skip-broken > echo "exec /usr/bin/mate-session" >> ~/.xinitrc > reboot > and then selected MATE in login screen. > > > Links to rpm's: > https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/fedora/linux/releases/28/Everything/x86_64/os/Packages/f/fedora-repos-28-1.noarch.rpm > and > https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/fedora/linux/releases/28/Everything/x86_64/os/Packages/f/fedora-gpg-keys-28-1.noarch.rpm > > List of installed packages from Fedora 28: > https://pastebin.com/VXL03Uqj > Ljubomi, Hooray! I re-installed CentOS 8 to a fresh VM and went through your instructions again. This time everything rebuilt and installed correctly. Thank you! --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 Mate?
On Wed, 2019-09-25 at 15:25 +0200, Ljubomir Ljubojevic wrote: > On 9/24/19 10:55 PM, Stephen John Smoogen wrote: > > On Tue, 24 Sep 2019 at 15:41, Frank Cox > > wrote: > > > Without wanting to sound too pushy, I'm wondering if there is any > > > update on the status of Mate now that Centos 8 has been released? > > > > > > I would love to jump on C8 and start playing with it, but the > > > lack of Mate is kind of a showstopper for me at the moment. > > > > > > > Nothing has changed since the September 16 answer I gave: > > > > This is more of a question for the EPEL lists versus here. The > > current > > status is that desktops are harder to package up in EL8 and only a > > less feature version is available at the moment. At the moment the > > only one I know of is KDE is half implemented in EPEL Playground > > and > > will be reimplemented as a module when EPEL gains the ability to do > > modules. At that point interested people can also do the work to > > make > > Mate/Cinnamon/etc available. > > As of now, I have a working MATE DM on CentOS 8. It's a hack though, > I > used Fedora repositories. But that means compiling MATE in EPEL > should > be straightforward, just recompile Fedora 28 packages. > > > I used Fedora 28 repo file and Fedora 28 GPG keys (links are > bellow), > unpacked then to proper directory and in Fedora repo files I changed > "$releasever" to "28". > I also installed yum-plugin-priorities and in all CentOS repo's added > "priority=1" and in all Fedora repos added "priority=2". > Ljubomir, So far so good. Had some problems breaking "whatprovides" for 'system- release' when I manually relinked it to 'fedora-release'. I had to manually install fedora-update.spec pointing only to 'updates'. [root@server02 Downloads]# yum list avail mate* Last metadata expiration chec: 0:15:35 ago on Sat 05 Oct 2019 09:17:39 PM CDT. Available Packages mate-applets.x86_64 1.20.3-2.fc28 updates mate-calc.x86_64 1.20.3-1.fc28 updates mate-control-center.i686 1.20.4-1.fc28 updates mate-control-center.x86_641.20.4-1.fc28 updates ... mate-utils-common.noarch 1.20.2-1.fc28 updates mate-utils-devel.i686 1.20.2-1.fc28 updates mate-utils-devel.x86_64 1.20.2-1.fc28 updates > Then I ran following commands (something like this, I experimented > some): > > > yum install python2-six > yum install mate* -x mate*devel* -x mate-menu I ran into trouble at this second step: Error: Problem 1: conflicting requests - nothing provides libgucharmap_2_90.so.7()(64bit) needed by mate- applet-1.20.3-2.fc28.x86_64 Problem 2: conflicting requests - nothing provides libgnome-keyring.so.0()(64bit) needed by mate- power-manager-1.20.3-1.fc28.x86_64 Problem 3: conflicting requests - nothing provides gtk2-engines needed by mate-themes-3.22-19- 2.fc28.noarch - nothing provides gtk-murrine-engine needed by mate-themes-3.22.19- 2.fc28.noarch Problem 4: conflicting requests - nothing provides pythin3-setproctitle needed by mate-optimus- 19.10.3-4.el8.noarch - nothing provides glew needed by mate-optimus-19.10.3-4.el8.noarch Problem 5: cannot intall the best candidate for the job - nothing provides hddtemp needed by mate-sensors-applet-1.20.3- 1.fc28.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Does this look familiar? --Doc > yum groupinstall "MATE" --skip-broken > yum groupinstall "MATE Desktop" --skip-broken > echo "exec /usr/bin/mate-session" >> ~/.xinitrc > reboot > and then selected MATE in login screen. > > > Links to rpm's: > https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/fedora/linux/releases/28/Everything/x86_64/os/Packages/f/fedora-repos-28-1.noarch.rpm > and > https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/fedora/linux/releases/28/Everything/x86_64/os/Packages/f/fedora-gpg-keys-28-1.noarch.rpm > > List of installed packages from Fedora 28: > https://pastebin.com/VXL03Uqj > > > > > > > > -- > > Stephen J Smoogen. > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Differences between CentOS 7.x and CentOS 8.x OS
On Sat, 2019-10-05 at 10:47 +0200, Ljubomir Ljubojevic wrote: > On 10/5/19 3:14 AM, David G. Miller wrote: > > On 10/4/19 6:59 PM, Fred Smith wrote: > > > On Fri, Oct 04, 2019 at 04:52:28PM -0600, David G. Miller wrote: > > > > On 10/3/19 1:37 PM, Ljubomir Ljubojevic wrote: > > > > > On 10/3/19 5:49 PM, Kaushal Shriyan wrote: > > > > > > Hi, > > > > > > > > > > > > I will appreciate it if someone can help me understand the > > > > > > differences > > > > > > between CentOS 7.x and CentOS 8.x OS. I look forward to > > > > > > hearing > > > > > > from you > > > > > > and thanks in advance. > > > > > > > > > > > In short, CentOS 7.x is based on Fedora 19 while CentOS 8 is > > > > > based on > > > > > Fedora 28. Most of what is in those Fedora's is also in > > > > > coresponding > > > > > CentOS version. Fedora's might be much easier to compare. > > > > > > > > > > This sort of cuts across two discussion threads but I found > > > > this one > > > > first. Silly question: has anyone tried using the Mate or Xfce > > > > Fedora 28 spins as package sources with CentOS 8? > > > I think someone did post recently that he took Mate from F28 > > > and with some judicious tweaking of the spec file got it built > > > and working on C8. Sorry, I have no details. > > > > > > > > Hopefully, the perpetrator will 'fess up and provide the details. > > > > Cheers, > > Dave > > > > "It is I, Leclerc" > > Here is what I did to have working MATE from Fedora 28 repositories > (did > not recompile anything): > > https://lists.centos.org/pipermail/centos/2019-September/173533.html > This is great information, Ljubomir. Thank you very much. I'll try to validate your process this weekend using F28 as you did. That should yield an older MATE v1.16. With that in hand, I'll try to re-run the procedure using the counterpart MATE v1.22 packages from Rawhide. Nothing ventured, nothing gained, right? --Doc Savage Fairview Heights IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 Mate?
On Thu, 2019-09-26 at 08:02 +0200, Ljubomir Ljubojevic wrote: > > I managed to install F28 MATE packages to CentOS 8, so all is needed > is > to recompile those in EPEL. I too am a solid fan of MATE. F28 had v1.16. F30 has the latest v1.22. Is there any reason I should not try the latest? Perhaps some dependencies not available in C8? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
