Discuss October 2019

discuss@lists.centos.org

125 participants
120 discussions

USB ISO for CentOS 8
by Jerry Geis 04 Oct '19

04 Oct '19

I did the dd of the ISO to a 16G USB device. the second partition is FAT so I can edit it - I want to make a custom menu entry. I edited the grub.cfg - but that did not work - my menu option does not show. Then I think I need to change BOOT.cfg and generate the grub.cfg - but I dont know in this case how to generate for the USB device. What command do I use for that ? Thanks, Jerry

3 4

kpatch (live kernel patching) in CentOS 7.7?
by Phelps, Matthew 04 Oct '19

04 Oct '19

Forgive me if this has been answered before and I've missed it. This https://access.redhat.com/solutions/2206511 says live kernel patches will be available via yum updates as of RHEL 7.7. Is this carried over to CentOS 7.7.1908? -- *Matt Phelps* *Information Technology Specialist, Systems Administrator* (Computation Facility, Smithsonian Astrophysical Observatory) Center for Astrophysics | Harvard & Smithsonian 60 Garden Street | MS 39 | Cambridge, MA 02138 email: mphelps(a)cfa.harvard.edu cfa.harvard.edu | Facebook <http://cfa.harvard.edu/facebook> | Twitter <http://cfa.harvard.edu/twitter> | YouTube <http://cfa.harvard.edu/youtube> | Newsletter <http://cfa.harvard.edu/newsletter>

6 11

CentOS8 and crypto-policies
by Todor Petkov 04 Oct '19

04 Oct '19

Hi, I started playing with CentOS8 and I am trying to set default crypto policies for openssh server/client. In CentOS7 I followed the guide from https://infosec.mozilla.org/guidelines/openssh.html and set KexAlgorithms /Ciphers/MACs in sshd_config. In CentOS8 I can edit /usr/share/crypto-policies/$POLICY/opensshserver.txt for the sshd arguments, but editing openssh.txt or even changing default crypto policy to FIPS seems to not affect the client options (ssh -Q mac) Is the client supposed to be affected by these policies or they are only for the server? Regards,

2 1

Re: [CentOS] CentOS 8 network-scripts
by Mike Litoris 04 Oct '19

04 Oct '19

On 10/4/19 12:27 PM, Jim Perrin wrote:> Why? I'd like to understand more about the use case where this is a requirement.I'd say for the sake of simplicity...Why complicate things with NM when you only need to set an IP ?The ifconfig files were great.Why is the choice, to use or not to use NM, not left the en end user ?That is the question...

2 1

Compiling latest postfix fails on C8
by Adrian van Bloois 04 Oct '19

04 Oct '19

Hi, I tried to compile the latest version of postfix, runs fine on C6 and C7, on C8 it fails. Complaining about missing ypclnt.h, this should com from glibc-headers. Any suggestions? Adrian -- Adri P. van Bloois "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

3 3

CentOS-8 QEMU guest won't bring virtio_net interface up.
by LAHAYE Olivier 04 Oct '19

04 Oct '19

Hi, I’m trying to PXE boot from qemu a CentOS-8 initrd, but despite I set rd.neednet=1, the virtio_net module is not loaded and the interface is not brought up. If I modprobe it by hand, it brings an eth0 interface. My initrd was created using dracut that includes network, qemu and qemu-net modules Qemu is started with EFI bios and vritio ethernet emulation Questions are: * Is it a known bug/ issue? * What Am I missing? * Lspci does see the Red Hat, Inc. Virtio network device, but nothing triggers the module load (virtio_net) * After doing modprobe virtio_net, the interface is named eth0 (it seems that it doesn’t follow the modern network device naming scheme) Before reporting a bug, I want to make sure that I’m not missing something. Regards, Olivier. -- Olivier LAHAYE

1 0

Keyboard backlight fails with recent kernels
by Rob Kampen 04 Oct '19

04 Oct '19

I do not use my laptop often, normally my better half has possession and use of it. It is a late 2011 ASUS ROG G73S which performs very well. The keyboard backlight was an issue initially under CentOS6, but the kind folks at elrepo found the missing bits in a more recent kernel and created a package to add them to the older CentOS6 kernel. An upgrade to CentOS7 went without a hitch and the keyboard lighting has worked fine. Recently I sat infront of the machine and couldn't see the keys - no backlight. A number of reboots later I have found that the latest kernel that I have on the machine, that works okay is 3.10.0-862.14.4.el7.x86_64 3.10.0-957.21.2.el7 and 3.10.0-957.27.2.el7 both fail to load/activate the driver for the keyboard. Would someone with the requisite knowledge please advise what I need to do. Is this a case for using the CentOSplus kernel or do I need to find and load a driver or two? or do I need to request the elrepo folk to make a suitable package. Thanks Rob

2 1

CentOS 8 as guest
by Jerry Geis 03 Oct '19

03 Oct '19

Hi all , I am running C7, and C8 as guest at this time. I noticed that when right click on desktop, and select display on C8 - that the largest resolution I get is 1080p, I am running a 4K monitor - is there a way to get higher resolution in the Guest. I am running with qemu 2.0.0 Thanks, Jerry

2 1

CentOS-announce Digest, Vol 176, Issue 2
by centos-announce-request＠centos.org 03 Oct '19

03 Oct '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:2829 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Oct 2019 16:02:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:2829 Important CentOS 7 kernel Security Update Message-ID: <20191002160222.GA24277(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:2829 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:2829 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ebb655a764a63bc72b795336a56b45febbc45118fdf1a3e07ed101cd8708bec1 bpftool-3.10.0-1062.1.2.el7.x86_64.rpm 5f6e02e3f6dc1959408725744f640de18eefaf5404dee6672d08a2d13fd03b6e kernel-3.10.0-1062.1.2.el7.x86_64.rpm 66f1ce8a28ac9fcec1f9a2c1d0191dadb736ee1a84284f10be946a53f7832207 kernel-abi-whitelists-3.10.0-1062.1.2.el7.noarch.rpm 06bbc747caf051a609bcf9174bbc2ef2bfdb1064a312e245bfbede0ebe6860f6 kernel-debug-3.10.0-1062.1.2.el7.x86_64.rpm 45dfb6f5b426ab702a7ccd7cbba672d713bb595295a01a64c376eee1cf924594 kernel-debug-devel-3.10.0-1062.1.2.el7.x86_64.rpm f4e3062885d4d9ddadfea063a8d598b60c0a01f22a13d7c40552ac7afb279aec kernel-devel-3.10.0-1062.1.2.el7.x86_64.rpm 71d8445dc4ffd28ca3229fee825b6dcb972aa50a60e7e3406a8d7b7d9b539f82 kernel-doc-3.10.0-1062.1.2.el7.noarch.rpm e81ddec34f199a568d20e8eb780f0f6da2e0c0a2b0aa5ffc84b3b397af16dc9b kernel-headers-3.10.0-1062.1.2.el7.x86_64.rpm 3f82f4a28e4ddd6eb7eb9eeee8a95931167b429414868aa2f6f447cabd41b28f kernel-tools-3.10.0-1062.1.2.el7.x86_64.rpm a88308a3a6afd8215b4f1960142f27272710151f4a51f22ed8a50f2ebd7a415f kernel-tools-libs-3.10.0-1062.1.2.el7.x86_64.rpm 03c61e99d728bcfffe5b100bdc0e20ba29375beaed1991b67bbc3158cc606dd0 kernel-tools-libs-devel-3.10.0-1062.1.2.el7.x86_64.rpm f0270b133ec6b0c166931d478fd500dad187024837c800fd456c988bb30c1c3d perf-3.10.0-1062.1.2.el7.x86_64.rpm 136a207af3a20d11f5640b8e19318ccbffa4e76461ed0c9301137d2dc555e37e python-perf-3.10.0-1062.1.2.el7.x86_64.rpm Source: 4d1b452162be95ed0f3a5e207175f27389da6472aa6160021e0052d9fa1a823e kernel-3.10.0-1062.1.2.el7.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 176, Issue 2 ***********************************************

1 0

Upgrade from 7.6.1810 to 7.7.1908 -> Interfaces order not static
by Jobst Schmalenbach 03 Oct '19

03 Oct '19

Hi For years (long time) I had " net.ifnames=0 biosdevname=0 " and it worked as it should (6.X, 7.X) I never had any problems, until yesterday. I started upgrading my machines and I stopped after the first one showed issues and I will not update all the other ones until this is sorted. I have problems keeping the interfaces in order as I wanted them to be assigned to eth0, eth1 .. eth4 Every reboot the order of eth1, eth2 and eth3 change BUT eth0 stays. Now when I read this https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… then I am doing the correct thing by adding the MAC as in so: DEVICE=eth0 IPADDR=... ... GATEWAY=... ONBOOT=yes BOOTPROTO=none USERCTL=no NOZEROCONF=true TYPE=Ethernet NM_CONTROLLED=no HWADDR=01:23:45:67:78:9a This works for eth0 but all the other ones the kernel complains /etc/sysconfig/network-scripts/ifup-eth: Device eth[1,2,3] has different MAC address than expected, ignoring NOTE: this worked until yesterday, I could reboot, update whatever it always came up in the same way and I also did not need to swap the network cables EVERY time ... Even without HWADDR/MAX adddress I have to swap the cables every time (eth[1,2,3]). Did something change in the kernel/networking/udev I am not aware of? What am I doing wrong all over sudden? Jobst -- Jobst Schmalenbach Programmer - an organism that turns coffee into software !

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2019