Discuss

discuss@lists.centos.org

2 participants
34758 discussions

C 7, selinux, and rpc.gssd
by m.roth＠5-cent.us 17 May '18

17 May '18

Folks, As systems are upgraded, we're getting a ton of complaints (fortunately, we're in permissive mode) that would break everything. All of them involve rpc.gssd, and I see a number of bugs listed when I search. Note that I first saw this on a RHEL system, but now I'm seeing it on CentOS 7. I'm bringing it up here, because, given that there are multiple reported, that there's some bigger picture involving policy and rpc.gssd. I'll note that some of the reported bugs were *closed last year, or before, so it seems to me an old issue resurfaced. Example. SELinux is preventing /usr/sbin/rpc.gssd from using the block_suspend capability. mark

1 0

place of other RH sources
by Leon Fauster 17 May '18

17 May '18

Out of curiosity - does someone known where the sources of other RH products are placed? RHEL sources are going into git.centos.org but what about e.g. RH OpenStack Platform packages or others products? -- LF

2 2

Creating a bootable USB to install CentOS 7
by KM 17 May '18

17 May '18

I need to copy CentOS 7 to a USB to boot from and install on servers. I have searched and there are a lot of different pages. I wanted someone to give me some tips or current places to look for easy ways to do this. I want to create the bootable USB from my Windows 10 PC in case that matters. Any tips/ideas would be great.Thank you in advance. KM

3 3

Problem with Digikam and libgphoto2 after latest update
by Nicolas Kovacs 17 May '18

17 May '18

Hi, I have CentOS 7 with KDE on my workstation. I'm using the CR repo. I had to remove Digikam to be able to do the latest update (1 GB of updates... wow). Here's what happens when I try to reinstall it. # yum install digikam ... --> Finished Dependency Resolution Error: Package: digikam-4.10.0-6.el7.x86_64 (epel) Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Available: libgphoto2-2.5.2-5.el7.x86_64 (base) libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr) ~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit) Error: Package: digikam-4.10.0-6.el7.x86_64 (epel) Requires: libgphoto2_port.so.10()(64bit) Available: libgphoto2-2.5.2-5.el7.x86_64 (base) libgphoto2_port.so.10()(64bit) Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr) ~libgphoto2_port.so.12()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Any suggestions? Just wait until the EPEL maintainers rebuild it against the latest stuff? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

5 8

Persisting Routes In A Routing Table Other Than The Default
by Adam Tauno Williams 16 May '18

16 May '18

I need to add persistent routes to a policy routing table. I can add rules to an IP policy table after installing NetworkManager-config- routing-rules; but I have not found how to add routes to a table other than the specific table. Manually I do a: ip route add default via 192.168.1.6 dev ens192 table pods Rules load automatically via the /etc/sysconfig/network-scripts/rules- {interface} files. Routes added to /etc/sysconfig/network- scripts/routes-{interface} are always added to the default policy. [root@aqueduct rc.d]# ip rule 0: from all lookup local 32763: from 192.168.65.0/24 lookup pods 32764: from 192.168.41.0/24 lookup pods 32765: from 192.168.43.0/24 lookup pods 32766: from all lookup main 32767: from all lookup default -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA

2 3

kernel-lt from ELRepo vs. GRUB: define default boot kernel
by Nicolas Kovacs 16 May '18

16 May '18

Hi, After upgrading my workstation to CentOS 7.5 (1804), I had to upgrade my kernel from vanilla to kernel-lt from ELRepo. My NVidia GeForce 210 would only work with the driver provided by NVidia, which in turn required a more recent kernel than 3.0.10. Anyway. Right now here's all the kernels that I have on my workstation: [root@alphamule:~] # rpm -qa | grep -i kernel kernel-lt-devel-4.4.129-1.el7.elrepo.x86_64 kernel-lt-devel-4.4.131-1.el7.elrepo.x86_64 kernel-lt-headers-4.4.131-1.el7.elrepo.x86_64 kernel-lt-4.4.131-1.el7.elrepo.x86_64 kernel-lt-4.4.129-1.el7.elrepo.x86_64 And here's what I'm currently running: [root@alphamule:~] # uname -r 4.4.129-1.el7.elrepo.x86_64 I have a Logitech Illuminated USB keyboard, and one of the quirks of this piece of hardware is that it's unresponsive on boot time. Meaning when GRUB displays the kernel menu, the arrow keys (or for the matter any keys) won't work. Which means the only choice I have left is either boot the default kernel in the list... or go to another office, grab a standard USB keyboard and plug it in temporarily just to choose the kernel to boot. So right now I have two kernels on my machine, the 4.4.129 and the 4.4.131. How do I configure GRUB so that on the next reboot, it defaults to the 4.4.131 kernel? I knew how to do this with LILO under Slackware, but GRUB is a very different beast. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

4 4

The right way to deal with in-house development
by m.roth＠5-cent.us 16 May '18

16 May '18

Ok, what's the "correct" way to deal with systems developed in-house, that have their own sets up subdirectories. And why, for that matter, does running sealert give me the full path to the executable, like openjdk... but *not* the full path to the file it's trying to operate on, and I'm left going "ok, where was the file it deleted? (we're running in permissive mode - overwhelmingly, developers and subject matter experts no less than nothing about selinux). mark

1 0

CentOS 7.5 (1804) and NetworkManager
by Nicolas Kovacs 16 May '18

16 May '18

Hi, I'm running CentOS on all kinds of setups: servers, workstations, desktops and laptops. Up until now, I'm only using NetworkManager on laptops, since it makes sense to use it there. On servers and desktop clients, I usually remove it and configure the network "traditionally" by simply editing /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, /etc/hosts, /etc/hostname and /etc/sysconfig/network. Running NetworkManager on anything else than a laptop has never made any sense to me, since it's basically an extra layer of abstraction. With the latest update, the removal of NetworkManager on a desktop client isn't possible anymore, since 'yum remove NetworkManager' also tries to remove 'gdm', and disabling it on startup spews back all sorts of errors. If you folks at Red Hat are reading this, I have one question: WHY ? Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

4 5

Re: [CentOS] CentOS 7.5 (1804) and NetworkManager
by Michael Lampe 16 May '18

16 May '18

Gnome's control-center now requires NetworkManager-wifi. But it's only a soft requirement, no shared libs involved. To keep your workstation NM-free, you want to install a dummy package that provides NetworkManager-wifi but actually contains nothing, ideally before updating to 7.5. Here's a script to create such a dummy: https://github.com/larsks/fakeprovide If you do this, control-center shows a sad face and some text (Oops, blah, blah, ...) in the WiFi tab. Just the same you always got in the network tab without NM. That's all. -M.

3 2

CentOS-announce Digest, Vol 159, Issue 3
by centos-announce-request＠centos.org 16 May '18

16 May '18

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-2018:1454 Critical CentOS 6 dhcp Security Update (Johnny Hughes) 2. CESA-2018:1453 Critical CentOS 7 dhcp Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 May 2018 15:51:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1454 Critical CentOS 6 dhcp Security Update Message-ID: <20180515155139.GA65109(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1454 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:1454 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e7b038ec6216dd9c84a4b2736a650df51c24837311786160402603a1d611d1e1 dhclient-4.1.1-53.P1.el6.centos.4.i686.rpm 56a47d7319dddd86deb59119fbde6bd8997f3d95ebc1023a9fd40d266af715bd dhcp-4.1.1-53.P1.el6.centos.4.i686.rpm f5abe8bcbe57a59102bfa875985c65f8ef11725d8d5cbba363a9af43b5c5b53e dhcp-common-4.1.1-53.P1.el6.centos.4.i686.rpm 7aac0528855e392838d05ed6040828f725fa53617e1a075263509a29ad6b4741 dhcp-devel-4.1.1-53.P1.el6.centos.4.i686.rpm x86_64: 274cc0f07e56546c3be18acc23696b63b83cbeb31d047132f1963b40f8e70eaa dhclient-4.1.1-53.P1.el6.centos.4.x86_64.rpm 34b6034b5152b0db167fb649c9d8d32f23ce6317b571d9a06af5176b0ab33a6a dhcp-4.1.1-53.P1.el6.centos.4.x86_64.rpm ab0da4ab9234f2b9c36251c970880804e4ec9cb6baa1e7a32e50b2e8655a4dc5 dhcp-common-4.1.1-53.P1.el6.centos.4.x86_64.rpm 7aac0528855e392838d05ed6040828f725fa53617e1a075263509a29ad6b4741 dhcp-devel-4.1.1-53.P1.el6.centos.4.i686.rpm d2d2344fd4076e12450ef5ca37ea2139a049166b6b2059b0ecc007fa1b892212 dhcp-devel-4.1.1-53.P1.el6.centos.4.x86_64.rpm Source: d30ede6d503154811891158c268f0b80a892c925662f0b8914d90d437392b42c dhcp-4.1.1-53.P1.el6.centos.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 15 May 2018 17:32:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1453 Critical CentOS 7 dhcp Security Update Message-ID: <20180515173234.GA28880(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1453 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:1453 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d8016005508135f34e59a890a4f189d5d63c1ae90647dc5cf292a58efa1ad281 dhclient-4.2.5-68.el7.centos.1.x86_64.rpm 87c6a692dca9eeae9c5bffed9aec1209570ad6d4ef2235dcd8d4e9aba92bea28 dhcp-4.2.5-68.el7.centos.1.x86_64.rpm 362140e6e05c70c91c4dd4f24d244b808173a2bc155712e0f921230bd139806d dhcp-common-4.2.5-68.el7.centos.1.x86_64.rpm e807c98666a5a90388c1013e8bd4001dafdb4ddc769b2de8679683600995ce47 dhcp-devel-4.2.5-68.el7.centos.1.i686.rpm c0b4af7a8bae02b00407f37283356085c7316a533196615c3f1dfffa6bb8a35a dhcp-devel-4.2.5-68.el7.centos.1.x86_64.rpm 1090e35b58f6eefc7d262df1e9d3e1afc5ebb7b86f7664bee8efd4fed5b0c6f7 dhcp-libs-4.2.5-68.el7.centos.1.i686.rpm 79fe00ee01d3087ca9384f639eec607b0d190007c68fab64da5f0e5c6b77d388 dhcp-libs-4.2.5-68.el7.centos.1.x86_64.rpm Source: fe5f91adcebb9edf7333af7a645d682919c6823d8d93f91d289c4f6da4d73df4 dhcp-4.2.5-68.el7.centos.1.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 159, Issue 3 ***********************************************

1 0

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