Discuss July 2019

discuss@lists.centos.org

78 participants
68 discussions

Roughly how many more months before CentOS 8.0 release?
by Turritopsis Dohrnii Teo En Ming 17 Jul '19

17 Jul '19

Good afternoon from Singapore, May I know roughly how many more months before CentOS 8.0 will be released? https://wiki.centos.org/About/Building_8 Thank you very much. -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

6 6

qemu-sparc, not to be confused with qemu-system-sparc
by John Chludzinski 17 Jul '19

17 Jul '19

I installed CentOS 7.6 then installed all things QEMU on my machine. I have a SPARC image I need to bringing up in a VM. I've been using *qemu-system-sparc *on a box on which I have Fedora-30 installed. $ qemu-system-sparc -m 256 -hda solaris_v2-qemu_v2.2.0.disk -nographic -bios ./openbios-sparc32 Can I use *qemu-sparc* to bring up my Solaris image: *solaris_v2-qemu_v2.2.0.disk* ? If so, how? It's not apparent and there's almost no info on it. BTW, *qemu-sparc* come with (on CentOS 7.6) when you: $ sudo yum install qemu* *PS> I've tried to install qemu-system-sparc on my CentOS box but ended up in a never-ending whack-a-mole game of dependencies.*

1 0

cron.allow.local
by mark 16 Jul '19

16 Jul '19

It worked on C 6, but on a C 7 box, I've restarted crond, and cron.allow doesn't have what's in cron.allw.local. What am I missing, folks? mark

2 1

Question on screen capture from command line
by Jerry Geis 16 Jul '19

16 Jul '19

I am trying to get the screen capture to work from command line (remotely). I am getting the wrong screen shot. This is what xrandr is giving me... xrandr --query Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 120.00*+ 100.00 119.88 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98 3840x2160 30.00 25.00 24.00 29.97 23.98 1920x1080i 60.00 50.00 59.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 60.00 50.00 59.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x576i 50.00 720x480 60.00 59.94 640x480 60.00 59.94 720x400 70.08 VIRTUAL1 disconnected (normal left inverted right x axis y axis) I'm thinking its giving me one of the other screens. Not the HDMI2 screen. What do I do ? It is definitely not the current screen shot. I have tried both xwd and import - same wrong result. Or - as a thought - how to I get RID of the other screens - and just have 1. The computer has an intel chipset. 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35) Thanks for any suggestions. Jerry

1 0

RHSA-2019:1150 rh-ruby24-ruby not fixed?
by Sebastian Schubert 16 Jul '19

16 Jul '19

Hi there, it seems like the rh-ruby24-ruby sclo has not been rebuilt yet :-? https://access.redhat.com/errata/RHSA-2019:1150 Kind Regards, basti

1 1

Install virtual win server
by Nikos Gatsis - Qbit 15 Jul '19

15 Jul '19

Hello list. Have someone installed windows server 2019 desktop on centos 7 kvm? Any tips? I have done it but I'm not sure if everything is OK. First of all, I cant ping the virt IP, although I connect through remote! Second, I cant activate windows and I'm pretty sure I have the right code... Thank you in advance, Nikos.

2 1

Alternative to laptop
by H 14 Jul '19

14 Jul '19

I am considering buying a small, and therefore easily portable, computer as an alternative to the laptop I already have. Obviously it would not have battery, a screen, nor a keyboard etc. but more or less be an easily portable computing unit to move between offices where a keyboard and monitor(s) could then be connected. I want to run CentOS 7, later CentOS 8. The smaller, the better, however, there are certain key features I would like to have: - HDMI for 2 monitors - USB for keyboard - 2 extra USB for eg external harddisk etc. - both wifi and at least Gb Ethernet cable connector Probably at least 16 Gb of memory, capability to drive two high-resolution monitors and whatever else might be nice such as SSD of at least 256 Gb. Size wise it would be nice if it were no larger than a "book", whatever size that might be. Does anyone use something like the above, or know of a computer meeting the above criteria?

7 10

Server fails to boot
by Rob Kampen 14 Jul '19

14 Jul '19

First some history. This is an Intel MB and processor some 6 years old, initially running CentOS 6. It has 4 x 1TB sata drives set up in two mdraid 1 mirrors. It has performed really well in a rural setting with frequent power cuts which the UPS has dealt with and auto shuts down the server after a few minutes and then auto restarts when power is restored. The clients needed a Windoze server for a proprietary accounting package they use, thus I have recently installed two SSD drives (500GB each) also in a raid 1 mirror and installed CentOS 7 as the host and also VirtualBox running Windoze 10. The hard drives continue to hold their data files. This appeared to work just fine until a few days ago. After a power cut the server would not reboot. It takes a while to get in front of the machine, add a monitor, keyboard and mouse only to find: Warning: /dev/disk/by-id/md-uuid-xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx does not exist repeated three times - one for each of the /, /boot, and swap raid member sets along with a Warning: /dev/disk/by-uuid/xxxxxxxx:xxxxxxxx:xxxxxxxx:xxxxxxxx does not exist for the /dev/md125 which is the actual raid 1 / device. The system is in a root shell of some sort as it has not made the transition from initramfs to the mdraid root drive. there are some other lines of info and a txt file with hundreds of lines of boot info, ending with the above info (as I recall). I tried a reboot - same result, rebooted and tried an earlier kernel - same result, tried a reboot to the recovery kernel and all went well. System comes up, all raids sets are up and in sync - no errors. So, no apparent H/W issues, no mdraid issues apparently, but none of the regular kernels will now boot. a blkid shows all the expected mdraid devices with the uuids from the error message all in place as expected. I did a yum reinstall of the most recent kernel as I thought that may repair any /boot file system problems - particularly initramfs, but no difference, will not boot, same exact error messages. Thus I now have it running on the recovery kernel, with all the required server functions being performed, albeit on an out of date kernel. Google has one solved problem similar to mine but the solution was change the BIOS from AHCI to IDE - that does not seem correct as I have not changed BIOS, although I have not checked it at this time. Another solution talks about a race condition and the md raid not being ready when required during the boot process and thus to add delay in the kernel boot line in grub2. Although no one indicated this actually worked. Another proposed solution is to mount the failed devices from a recovery boot and rebuild initramfs. Before I do this I would like to ask those that know a little more about the boot process, what is going wrong? I can believe the most recent initramfs being a problem, but all three other kernels too?? Yet the recovery kernel works just fine. As the system is remote, I would like some understanding of what's up before I do any changes - if a reboot occurs and fails, it will mean another trip. Oh, one other thing, it seems the UPS is not working correctly, thus it may not have shut down cleanly. Working to replace batteries in the UPS. TIA for your insight.

2 2

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

13 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. CEBA-2019:1703 CentOS 7 tzdata BugFix Update (Johnny Hughes) 2. CESA-2019:1765 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2019:1763 Critical CentOS 7 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jul 2019 16:51:31 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:1703 CentOS 7 tzdata BugFix Update Message-ID: <20190711165131.GA8753(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 ) x86_64: aaa172e85c6f0ccf3d8276cb0a2ddf4f545b4ee04bf9aa1248db0fa2b2b6b948 tzdata-2019b-1.el7.noarch.rpm f4ce6bd9f84fcf8d48d5cefaf961a04d08505b20392091adda357ccd735afcf0 tzdata-java-2019b-1.el7.noarch.rpm Source: 87057e3cdf326f2d0769e4cf7234f0bcc6fe2f1f54730a8b5a8262f718196c4d tzdata-2019b-1.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 12 Jul 2019 16:20:59 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1765 Critical CentOS 6 firefox Security Update Message-ID: <20190712162059.GA20137(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1765 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2019:1765 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6fe785cbfc9bb4b3aa688a10132d2e1f75f8bd72f4f49a81eb35de6c51eef4da firefox-60.8.0-1.el6.centos.i686.rpm x86_64: 6fe785cbfc9bb4b3aa688a10132d2e1f75f8bd72f4f49a81eb35de6c51eef4da firefox-60.8.0-1.el6.centos.i686.rpm 4b0dedf940377adbd396ae796bb3e511ef61fc353994baf13ad332c9f31d8d7c firefox-60.8.0-1.el6.centos.x86_64.rpm Source: 946dfcfaca2fffab49cb9fafb9cb1dd875724aacefde67b0d0473b3262ffdc51 firefox-60.8.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 12 Jul 2019 16:21:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1763 Critical CentOS 7 firefox Security Update Message-ID: <20190712162153.GA20252(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1763 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2019:1763 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e02b1e7e7fe86baf4e2cf3facc6762d27c39d291261718142474d5ae11df110b firefox-60.8.0-1.el7.centos.i686.rpm f382fa26a94508231ca32e32d35f76fd2284171392190e908a1261de262db2bd firefox-60.8.0-1.el7.centos.x86_64.rpm Source: 6ab820842a4e625e422a5e3decc25dc06afe68faab0c8f8e304085ed145ec54e firefox-60.8.0-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 173, Issue 6 ***********************************************

1 0

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2019