Discuss

discuss@lists.centos.org

5 participants
34752 discussions

CentOS-announce Digest, Vol 167, Issue 5
by centos-announce-request＠centos.org 25 Jan '19

25 Jan '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:0109 Important CentOS 7 perl Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 24 Jan 2019 15:18:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0109 Important CentOS 7 perl Security Update Message-ID: <20190124151807.GA623(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0109 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0109 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 25fdf4603ff050c99e0733e5c87e956ae4d53958f5cc012c4aef9c96f0db06d7 perl-5.16.3-294.el7_6.x86_64.rpm a5c033d9f07ae7f3e1be74af0efbacba9a28182e49ebb1051e42f401d10df6bd perl-core-5.16.3-294.el7_6.x86_64.rpm d19952d11c7e8a1665de0c25c334a32fbffd15bc86daa5d1d830df8eab234f2e perl-CPAN-1.9800-294.el7_6.noarch.rpm c00e846544d902eea1cd6186e0b0ae97dc8c6e755c324e87f3efb7630aaf4c88 perl-devel-5.16.3-294.el7_6.i686.rpm afd580856968dd1ce74fc7ae4974dd1e0421892524e6fe415cd6300e1959f84e perl-devel-5.16.3-294.el7_6.x86_64.rpm 455397f649b77085744bc3a2e5e256d62d78c21147760b904f0189c21e6c90aa perl-ExtUtils-CBuilder-0.28.2.6-294.el7_6.noarch.rpm 71338d899e335e1fec8e5da0aa24df3400be530758d8380b35d356f07d43cf87 perl-ExtUtils-Embed-1.30-294.el7_6.noarch.rpm aeb5cb697a0edc60d2b4f014cad259620cb435aa0c1b2efead35bc3b60999ee7 perl-ExtUtils-Install-1.58-294.el7_6.noarch.rpm ee21a31de70c64daa1742260fc590203ef3bcb014c881813ada7a3acfb4178b9 perl-IO-Zlib-1.10-294.el7_6.noarch.rpm 2cde9e14351428a33484a57f9e4488ebe3bac607f549187208d0bf169ef85560 perl-libs-5.16.3-294.el7_6.i686.rpm 30bb4e65251eb02ae23fab59cd7833896ca241db385c6f5eea06c489ff00b416 perl-libs-5.16.3-294.el7_6.x86_64.rpm bac35a1f122bcc21c847ee41dc8f660c4a6d52794546eaa557fd036767ef8e8c perl-Locale-Maketext-Simple-0.21-294.el7_6.noarch.rpm a7428d0496b667350f611bbef32237b077e0974e1cff79e4398c0d882e19854a perl-macros-5.16.3-294.el7_6.x86_64.rpm b8f77bf6065bb12cb3fa1f33d0b98b40dabbb231900f41d8b6dbd5bfac7b4acd perl-Module-CoreList-2.76.02-294.el7_6.noarch.rpm 1bfaff78e1bf7696675b2748044beb6ffcd46cbb2a740381c725a617444d9ccb perl-Module-Loaded-0.08-294.el7_6.noarch.rpm 5ab7b507ade62e28bf44e8650b426b8604223314d334fdb7f0d545287086b356 perl-Object-Accessor-0.42-294.el7_6.noarch.rpm 494ab3285e32fd03fe75644fb429ea1250ae442b9cffafbed5a984faf11cffdd perl-Package-Constants-0.02-294.el7_6.noarch.rpm 54e0dadc78699063a7649857f51837a4a2f9299bb410460ad00e9e6c6490c928 perl-Pod-Escapes-1.04-294.el7_6.noarch.rpm 60d7c951435aaf2773a870bc884dbb0509021607f499c2ab06b82e9f3faf76f3 perl-tests-5.16.3-294.el7_6.x86_64.rpm 14342dea55b80183a11e039ca5bd54189467e2b09309717799725bb916dc6d16 perl-Time-Piece-1.20.1-294.el7_6.x86_64.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 167, Issue 5 ***********************************************

1 0

C7, pulseaudio, multi-user setup
by wwp 24 Jan '19

24 Jan '19

Hello there, I'm on a CentOS7 laptop, in a Mate session w/ my default user, and in that desktop, I run apps from other users using sudo, su. It appears that apps started using sudo or in terminals+su, can't play sound: [pulseaudio] main.c: User-configured server at {f7ac68929370425d82f882c116a21597}unix:/run/user/1000/pulse/native, refusing to start/autospawn. User 1000 is my default user. I've searched and read a lot about this topic, and found many suggestions but none works so far. What's the correct way to allow all users to play sound in my default user's desktop session? Adding them all to the audio group doesn't seem to be enough (at least). Regards, -- wwp

1 0

dhcp-client should send hostname to dhcp/ dns server
by Ralf Prengel 24 Jan '19

24 Jan '19

Hallo, what is the right way in centos7 to configure the dhcp-client so that the system name is send to the dhcp/dns server (windows-domain). I found DHCP_HOSTNAME="Hostname" as entry in the device-config of the network-interface. Thanks for hints Ralf

1 0

C7, and my RAID
by mark 23 Jan '19

23 Jan '19

Ok, I think my only choice at this point is to delete and recreate the RAID, then restore from backup (oy, 7TB). I see that I can do an mdadm --remove /dev/md0, then, the page I see that on, suggests zeroing the superblocks. What would happen if I *don't* zero the superblocks before doing an mdadm --create? Would I just wind up back where I am? mark

1 0

Where is everyone?
by mark 23 Jan '19

23 Jan '19

There's usually a lot more traffic here. Just today, I've started wondering if a lot of folks who are usually here are on furlough, with the US gov't shutdown.... If so, my condolences, folks. mark

1 0

Re: [CentOS] C7 and mdadm - apparently SOLVED
by mark 23 Jan '19

23 Jan '19

Looking around on the Web, what I just tried was to stop the RAID, then do an --assemble --scan, and *that* found everything, put the raid together, and appears to be rebuilding using the new drive. *phew* I do find it interesting that scan works, but explicitly assembling apparently remembers the drive that died, and wouldn't even look at it. mark

2 3

dmarc auth on incoming email
by Fred Smith 23 Jan '19

23 Jan '19

Just reading up on DMARC, toying with setting it up to auth against incoming emails. (but not configure my domain to use dmarc, or at least not yet) ran into an article about opendmarc, which is available on epel. but when I took a look at the opendmarc website and the git pages it doesn't appear to have been updated in several years. while I see that it is still available from epel, I wonder if anyone knows the project status? Is it still active? are there any other viable alternatives? thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

2 1

C7 radeon driver
by mark 23 Jan '19

23 Jan '19

Hi, folks, We've been recently (the last few months) having issues on workstations with the radeon driver. A typical sample is this, from /var/log/messages: Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: ring 0 stalled for more than 10000msec Jan 23 11:35:32 <workstation> kernel: radeon 0000:03:00.0: GPU lockup (current fence id 0x0000000000000212 last fence id 0x0000000000000213 on ring 0) Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: Saved 23 dwords of commands on ring 0. Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GPU softreset: 0x00000019 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS = 0xE5303CA0 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS_SE0 = 0xF4000007 Jan 23 11:35:33 <workstation> kernel: radeon 0000:03:00.0: GRBM_STATUS_SE1 = 0x00000007 ... The above system has a Cedar GL [FirePro 2270], while the other two have Radeon HD 8570 / R7 240/340, so it doesn't seem to be limited to one video card. Are other people seeing similar errors? Is this enough for a bug report? mark

1 0

C7 and mdadm
by mark 23 Jan '19

23 Jan '19

A user's system had a hard drive failure over the weekend. Linux RAID 6. I identified the drive, brought the system down (8 drives, and I didn't know the s/n of the bad one. why it was there in the box, rather than where I started looking...) Brought it up, RAID not working. I finally found that I had to do an mdadm --stop /dev/md0, then I could do an assemble, then I could add the new drive. But: it's now cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid5 sdg1[8](S) sdh1[7] sdf1[4] sde1[3] sdd1[2] sdc1[1] 23441313792 blocks super 1.2 level 5, 512k chunk, algorithm 2 [7/5] [_UUUU_U] bitmap: 0/30 pages [0KB], 65536KB chunk unused devices: <none> and I can't mount it (it's xfs, btw). *Should* I make it readwrite, or is there something else I should do? mark

3 2

Yum refuses to install kmod-8188eu from elrepo
by Marko Vojinovic 23 Jan '19

23 Jan '19

I am having trouble using the realtek wifi chip in my new tp-link usb wifi dongle. Upon plugging it, the device gets registered by the kernel (in /var/log/messages), but that's about it, no network device is being created (iwconfig does not see it, nothing else works). A few google searches later I found out that this realtek chip is not supported by the kernel and requires a driver, and that the driver is packaged for C7 as kmod-8188eu in elrepo. However, yum install kmod-8188eu refuses to install it (full yum output is here: https://pastebin.com/raw/vvak6FCU ), complaining that the following dependencies cannot be met: --> Processing Dependency: kernel(wireless_send_event) = 0xa02e7e03 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_submit_urb) = 0x74c6ac58 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_reset_device) = 0xddd0084e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_put_dev) = 0xf709107c for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_kill_urb) = 0xa55bf715 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_get_dev) = 0x372a41af for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_free_urb) = 0x739aecf4 for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_control_msg) = 0xd04e3a9e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(usb_alloc_urb) = 0x12a4948e for package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 I've never seen such output from yum before --- I'm guessing it is asking for a kernel with specific "properties", and failing to find one. What is the best way to resolve this? Is there some kernel package somewhere that matches these properties, or is there some other package that provides these features to an existing kernel, or something else? Or should I just ditch the kmod, and compile the 8188eu driver from source? I'd prefer to avoid this if possible, since I am not a fan of recompiling it every time the kernel is updated in C7. And I might need to use the wifi dongle on multiple machines, anyway. I'd appreciate any suggestions! TIA, :-) Marko

4 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss