Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Script to Check 7.x Hardware Compatibility?
by Tim Evans 12 Jul '19

12 Jul '19

I have a vague recollection--from several years back--there was once a script out there that could be run on a CentOS 6.x system to test its hardware compatibility for CentOS 7. (Not talking about a script to actually do any upgrade; just check a system's hardware.) Does anyone remember this? Remember the details? Thanks. -- Tim Evans |5 Chestnut Court 443-394-3864 |Owings Mills, MD 21117

1 1

Scope of classes in CFE 3.10.2 on CentOS 7
by Meikel 12 Jul '19

12 Jul '19

Hi folks, I have a question concerning scope of classes in CFEngine 3. I run CFE 3.10.2 on CentOS 7.4. # cf-agent -V CFEngine Core 3.10.2 # cat /etc/redhat-release CentOS Linux release 7.4.1708 (Core) I'm logged in as root and located in current working dir /root. I have the following file # ll ./samples/scope_of_class.cf -rwx------. 1 root root 720 10. Jul 16:33 ./samples/scope_of_class.cf with content ----BEGIN---------------------------------- bundle agent scope_of_class() { vars: any:: "web_servers" slist => { "ws-1.example.com", "ws-2.example.com", "webserver.example.com", }; methods: any:: "scope_of_class_b1" usebundle => scope_of_class_b1( $(scope_of_class.web_servers) ); } bundle agent scope_of_class_b1( server ) { classes: any:: "is_dir" expression => isdir( "/tmp/scope_of_class/$(server)" ), scope => "bundle"; reports: is_dir:: "is_dir is SET"; !is_dir:: "is_dir is UNset"; any:: "server = $(server)"; } ----END------------------------------------ From my understanding the scope "bundle" is default for a class definition inside a bundle of type agent, but I added the scope to be sure. The definition of class is_dir should depend on directories existing inside /tmp/scope_of_class. I have two subdirectories # ls -1 /tmp/scope_of_class/ webserver.example.com ws-1.example.com but when I run CFE I do NOT get expected behaviour for the definition of class is_dir: # cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence scope_of_class info: Using command line specified bundlesequence R: is_dir is SET R: server = ws-1.example.com R: is_dir is UNset R: server = ws-2.example.com R: server = webserver.example.com When the bundle scope_of_class_b1 is processed for parameter webserver.example.com I expect is_dir to bet set, but from the report it seems not to be set. If I change the slist definition to hold "webserver.example.com" as the first entry, then the class is_dir is set correctly: # grep slist ./samples/scope_of_class.cf -A 4 "web_servers" slist => { "webserver.example.com", "ws-1.example.com", "ws-2.example.com", }; # cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence scope_of_class info: Using command line specified bundlesequence R: is_dir is SET R: server = webserver.example.com R: server = ws-1.example.com R: is_dir is UNset R: server = ws-2.example.com It also works "correct" (or as expected by me) if "ws-2.example.com" is first entry in the slist definition: # grep slist ./samples/scope_of_class.cf -A 4 "web_servers" slist => { "ws-2.example.com", "ws-1.example.com", "webserver.example.com", }; # cf-agent -IK --file ./samples/scope_of_class.cf --bundlesequence scope_of_class info: Using command line specified bundlesequence R: is_dir is UNset R: server = ws-2.example.com R: is_dir is SET R: server = ws-1.example.com R: server = webserver.example.com I do not understand why the ordering inside slist influences how the class is_dir will be defined later by CFE for each processing of scope_of_class_b1. Some background information: my aim is to create webserver vhost configuration files where I have two variants, one with SSL configuration and one without SSL configuration. Which one to configure depends if the directory with the SSL certificate exists for a given vhost or not. I'll replace the report promise type by a file promise type, which should bring the correct vhost configuration file in place, assumed that I understand how the scope of the class definition works. Thanks in advance for any help or explanation of that behaviour. Regards, Meikel

2 2

CentOS-announce Digest, Vol 173, Issue 5
by centos-announce-request＠centos.org 12 Jul '19

12 Jul '19

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-2019:1726 Important CentOS 6 dbus Security Update (Johnny Hughes) 2. CEBA-2019:1703 CentOS 6 tzdata BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jul 2019 16:07:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1726 Important CentOS 6 dbus Security Update Message-ID: <20190711160734.GA7291(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1726 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:1726 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f5bb925a65b0e4ba5c51e2b6a76665c28a71af9a831fd613769643ea3a5b6516 dbus-1.2.24-11.el6_10.i686.rpm c1e57654a9433bd678b8588a1a3e7e3de2abf5e72ab9c8f71a9daae06e9b1325 dbus-devel-1.2.24-11.el6_10.i686.rpm 0d146585a84c8039e0f37c6ad78328e540f0c5e75387f37f1a301ac262c45676 dbus-doc-1.2.24-11.el6_10.noarch.rpm 8f5826a8022d455cb8a1060330ad81d886dbd557886f8b9e3622d9c81001d0cd dbus-libs-1.2.24-11.el6_10.i686.rpm db4b9cb924f0de827486a082d7ba9b496449f0d20d480f1c914971b0fcd1baea dbus-x11-1.2.24-11.el6_10.i686.rpm x86_64: fff1165e33cf46563b4a925cbe2054ad02a03d5de142a703506e3a8bfeb99990 dbus-1.2.24-11.el6_10.x86_64.rpm c1e57654a9433bd678b8588a1a3e7e3de2abf5e72ab9c8f71a9daae06e9b1325 dbus-devel-1.2.24-11.el6_10.i686.rpm 78f1edd146aa9dafd76177fb0102a33db764214c28f256ac5bf5bfdfae27f835 dbus-devel-1.2.24-11.el6_10.x86_64.rpm 0d146585a84c8039e0f37c6ad78328e540f0c5e75387f37f1a301ac262c45676 dbus-doc-1.2.24-11.el6_10.noarch.rpm 8f5826a8022d455cb8a1060330ad81d886dbd557886f8b9e3622d9c81001d0cd dbus-libs-1.2.24-11.el6_10.i686.rpm 4f0130d1a2c7296551dddf395922b65dfd1631cf83dcd74af2c7bffa119d5b09 dbus-libs-1.2.24-11.el6_10.x86_64.rpm 0ffc60993472da1ab68717e6620b8bc00f0e892a408feee8fae95b53e958e356 dbus-x11-1.2.24-11.el6_10.x86_64.rpm Source: 1ec88b6e0e05954f6bbc246da9d996da87f6dd31e99aa5a91a6ed1e94b7e588b dbus-1.2.24-11.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 11 Jul 2019 16:08:03 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:1703 CentOS 6 tzdata BugFix Update Message-ID: <20190711160803.GA7426(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:1703 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1703 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c8f766f235243b051e17761546419b35aa35bbaf35e23fd3a8c990d4330dd840 tzdata-2019b-2.el6.noarch.rpm cd93928f1899fe2cad42354bb9158c127a8e05bae0d4a2c400decb2b89ad39fc tzdata-java-2019b-2.el6.noarch.rpm x86_64: c8f766f235243b051e17761546419b35aa35bbaf35e23fd3a8c990d4330dd840 tzdata-2019b-2.el6.noarch.rpm cd93928f1899fe2cad42354bb9158c127a8e05bae0d4a2c400decb2b89ad39fc tzdata-java-2019b-2.el6.noarch.rpm Source: fa03dd305680c491bfa80c91b1d7804a36f3bc49a1546d8f3e8e0549a080df28 tzdata-2019b-2.el6.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 173, Issue 5 ***********************************************

1 0

screen shot centos 7
by Jerry Geis 10 Jul '19

10 Jul '19

HI All, I have some remote computers - at times I issue commands to take screen shots. I use xwd -silent -root or import -silent -window root to do so. It seems at times the screen capture is the actual current content. It might be a previous displayed item etc... Anyone ran across this or thoughts ? Jerry

2 2

CentOS-announce Digest, Vol 173, Issue 4
by centos-announce-request＠centos.org 10 Jul '19

10 Jul '19

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. CentOS, Red Hat, and IBM (Rich Bowen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 9 Jul 2019 10:47:33 -0400 From: Rich Bowen <rbowen(a)redhat.com> To: CentOS mailing list <centos(a)centos.org>, "The CentOS developers mailing list." <centos-devel(a)centos.org>, centos-announce(a)centos.org Subject: [CentOS-announce] CentOS, Red Hat, and IBM Message-ID: <a42e4032-26f5-85f5-506b-27c60f9dbdbf(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed CentOS community, Today marks a new day in the 26-year history of Red Hat. IBM has finalized its acquisition of Red Hat (https://www.redhat.com/en/about/press-releases/ibm-closes-landmark-acquisit…) which will operate as a distinct unit within IBM moving forward. What does this mean for Red Hat?s contributions to the CentOS project? In short, nothing. Red Hat always has and will continue to be a champion for open source and projects like CentOS. IBM is committed to Red Hat?s independence and role in open source software communities so that we can continue this work without interruption or changes. Our mission, governance, and objectives remain the same. We will continue to execute the existing project roadmap. Red Hat associates will continue to contribute to the upstream in the same ways they have been. And, as always, we will continue to help upstream projects be successful and contribute to welcoming new members and maintaining the project. We will do this together, with the community, as we always have. If you have questions or would like to learn more about today?s news, I encourage you to review the list of materials below. Red Hat CTO Chris Wright will host an online Q&A session in the coming days where you can ask questions you may have about what the acquisition means for Red Hat and our involvement in open source communities. Details will be announced on the Red Hat blog - https://www.redhat.com/en/blog Press release - https://www.redhat.com/en/about/press-releases/ibm-closes-landmark-acquisit… Chris Wright blog - Red Hat and IBM: Accelerating the adoption of open source - https://www.redhat.com/en/blog/red-hat-and-ibm-accelerating-adoption-open-s… FAQ on Red Hat Community Blog - https://community.redhat.com/blog/2019/07/faq-for-communities/ -- Rich Bowen - rbowen(a)redhat.com - CentOS Community Manager @CentOSProject // @rbowen ------------------------------ 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 173, Issue 4 ***********************************************

1 0

CentOS 7 hibernation laptop
by H 10 Jul '19

10 Jul '19

I have a recent Dell Inspiron laptop on which I installed CentOS 7. I have, however, failed somewhere since I do not have a hibernate option when shutting down, only a suspend option. I believe I created the necessary hibernation partition large enough for the RAM the machine has, 16 Gb if I remember correctly. How do I identify where the problem lies?

2 2

32-bit CentOS
by Dave Close 10 Jul '19

10 Jul '19

It appears that CentOS 7 was the last one with a 32-bit version. I'm trying to install it on an older laptop and having some trouble. I have CentOS-7-i386-Everything-1810.iso and have verified it. Using either dd or mediawriter to put a copy on a 16 GB thumb drive seems to work. But then the laptop reports, "no boot image found". Note that the first 32 KB of the iso is all zeros, meaning that there is no MBR or partition table included. According to the 0_README.txt on the CentOS mirrors, the Everything ISO, "contains the complete set of packages for CentOS Linux 7. It can be used for installing or populating a local mirror. This image needs a 16GB USB flash drive as it is too large for DVD isos... You can burn these images to a DVD or 'dd' them to a USB flash drive. After the boot media has been prepared, boot the computer off the boot media." Does anyone know what I don't understand about this procedure? -- Dave Close, Compata, Irvine CA +1 714 434 7359 dave(a)compata.com dhclose(a)alumni.caltech.edu "Fairness is a concept that was invented so kids and idiots could participate in debates." --Dogbert

6 5

Problem to exec 'cc1obj'
by Andreas Meyer 09 Jul '19

09 Jul '19

Hello! Try to comile sope on CentOS 7 and get: # make This is gnustep-make 2.7.0. Type 'gmake print-gnustep-make-help' for help. Running in gnustep-make version 2 strict mode. Making all in sope-xml ... Making all in SaxObjC ... Making all for library libSaxObjC... Compiling file SaxAttributeList.m ... gcc: error trying to exec 'cc1obj': execvp: Datei oder Verzeichnis nicht gefunden gmake[5]: *** [obj/libSaxObjC.obj/SaxAttributeList.m.o] Fehler 1 gmake[4]: *** [internal-library-all_] Fehler 2 gmake[3]: *** [libSaxObjC.all.library.variables] Fehler 2 gmake[2]: *** [internal-all] Fehler 2 gmake[1]: *** [internal-all] Fehler 2 make: *** [internal-all] Fehler 2 Could need some help on this one. Kind regards Andreas

2 2

epoch rpm el8 obsolete?
by Leon Fauster 09 Jul '19

09 Jul '19

I am building a new workstation based on EL8 now. As someone else here mentioned, the raw EL8 distribution is unusable as a workstation. Therefore I am building lot of additional packages. Today I came across a problem with a custom package with an Epoch version, that kills the yum/dnf update process (it tries to find a "best" package etc.). My actually question; is the RPM Epoch stanza obsolete now (for EL8)? I remember that they also started to delete Groups categories ... -- LF

2 2

adding uefi to kickstart CentOS 7
by Jerry Geis 09 Jul '19

09 Jul '19

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda --fstype xfs --size=1 --asprimary --grow the line with /boot/efi is the only new item other then "removing" --location=mbr from the bootloader line. The install is not working. It stops on the Installation part with selections 1-8. I see no errors on screen - but the selection for "Install source" has a "!" and "error setting up install source" is there. when I goto another console and run fdisk -l /dev/sda nothing shows so my partitions are not getting setup. What did I miss to setup efi ? Thanks, Jerry

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss