Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Display boot menu with GRUB_TIMEOUT=0?
by Nicolas Kovacs 12 May '16

12 May '16

Hi, On my minimal installation of CentOS 7, here's what I have in /etc/default/grub: GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos_amandine/root \ rd.lvm.lv=centos_amandine/swap \ video=1024x768 \ quiet" GRUB_DISABLE_RECOVERY="true" According to the official documentation, pressing any alphanumerical key just after the BIOS screen will make the GRUB menu appear. I tried that, but to no avail. Any idea what's the magic combination to make the GRUB boot menu appear when GRUB_TIMEOUT is set to 0? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

4 5

RPM perl requirements woes
by Anand Buddhdev 12 May '16

12 May '16

Dear CentOS hive mind, I'm trying to package up a perl module into an RPM for easy deployment. I want it to be as self-contained as possible (to avoid version issues with perl modules in base or EPEL). So in my spec file, I'm doing: curl -L http://cpanmin.us | perl - App::cpanminus -L %{buildroot}/opt/zonemaster Zonemaster This way, cpanminus is installed first, and then it goes on to install the module and all its dependencies. In the %files section, if I do: /opt/zonemaster the RPM is also neatly packaged up. However, trying to install this on another system causes errors: # yum install zonemaster-engine-1.0.13-1.el7.gii.x86_64.rpm ... ... elided ... ... Error: Package: zonemaster-engine-1.0.13-1.el7.gii.x86_64 (/zonemaster-engine-1.0.13-1.el7.gii.x86_64) Requires: perl(JSON::backportPP) Error: Package: zonemaster-engine-1.0.13-1.el7.gii.x86_64 (/zonemaster-engine-1.0.13-1.el7.gii.x86_64) Requires: perl(namespace::clean::_Util) Error: Package: zonemaster-engine-1.0.13-1.el7.gii.x86_64 (/zonemaster-engine-1.0.13-1.el7.gii.x86_64) Requires: perl(Moose::Conflicts) Now, JSON::backportPP and Moose::Conflicts are part of JSON and Moose, respectively. However, those specific modules hide themselves from /usr/lib/rpm/perl.prov, by doing this: package # hide from PAUSE Moose::Conflicts; and package # This is JSON::backportPP JSON::PP; This is annoying. Does anyone have any idea on how to fix this? Can I get away with manually adding: Provides: JSON::backportPP Moose::Conflicts to the spec file? It looks like an ugly hack to me. Regards, Anand

3 3

Very Delayed Boot on CentOS 7 (With default XFS)
by Traiano Welcome 12 May '16

12 May '16

Hi List I'm testing a VM installation of CentOS 7,(kernel 3-10.0-327) with the default XFS filesystem on the root. During boot up, the VM pauses for about 80 seconds at the following message: "Started filesystem check on /dev/mapper/centos-root" ... And then the boot continues. Looking at the fstab, I see the 6th field is set to 0 , so I expect filesystem checking to be disabled, but no ... Has anyone encountered this issue before ? Is there a way I can reduce the time to boot up at this point? Thanks in advance, Traiano

1 0

softwarecollections/Devtoolset-3 :: usage from different directory
by Adrian Sevcenco 12 May '16

12 May '16

Hi! Did anyone tried to use devtoolset from different directory than the default one? from what i can see it would be enough just to change the hardcoded directory in enable file but i would like to hear if someone else tried this ... Thank you! Adrian

1 0

CentOS-announce Digest, Vol 135, Issue 6
by centos-announce-request＠centos.org 12 May '16

12 May '16

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-2016:1024 CentOS 5 kernel BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 May 2016 14:38:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1024 CentOS 5 kernel BugFix Update Message-ID: <20160511143850.GA10934(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1024 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1024.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e21333e5147902b2e6ac2b21ab7102ea36a883a25376cfab7f13a173974cd08c kernel-2.6.18-410.el5.i686.rpm 234ed889efed1ccac7319ca9ea536917eb8bebb70a9b862c683a993afa997778 kernel-debug-2.6.18-410.el5.i686.rpm 7137d4acd8e588d35f8476fefe106e95f53b4c43867f3c27d904f4685e74c1c1 kernel-debug-devel-2.6.18-410.el5.i686.rpm c4ad98d530a86f26279ea80ccb77c3032f81cf566a54cf6a6d1e19f0fb3c9723 kernel-devel-2.6.18-410.el5.i686.rpm 304092640b7c4f9311c6cc27453c28c32516dc29e9024edaea35bb5546f2e7ae kernel-doc-2.6.18-410.el5.noarch.rpm 58dcfdffd8b8dddb6ad204a6a3bd79ebf8ecea53cf12f22e6b2da6880332afeb kernel-headers-2.6.18-410.el5.i386.rpm ca1d5a7fe86af1d2b8ff1532112c307e4bd06d8d7c0494fff54109e352c1e2a9 kernel-PAE-2.6.18-410.el5.i686.rpm 0a5c2bc78da5244e1066b40d326e887d5209d9e8f4c2436f9a84228907871125 kernel-PAE-devel-2.6.18-410.el5.i686.rpm 199ec6dfa92f5ca778c07f8207c8a8e3115196d903f5418dfda55c306bbcd941 kernel-xen-2.6.18-410.el5.i686.rpm eef410ce2a225688beb24b95610fdb5daf63aab030712825d6030447c1f9bc31 kernel-xen-devel-2.6.18-410.el5.i686.rpm x86_64: 8a73befd4fdd7242d0ebd0d6dd6509289e2372f6f3571366fa7f93f29355bf98 kernel-2.6.18-410.el5.x86_64.rpm b766ff2c1e3ebe9e59de3c8c965e4e9322371f0405d52bf301e2255e442972d7 kernel-debug-2.6.18-410.el5.x86_64.rpm b0fa14014fe9ff9dd0951450c3ee325c1b6af2cb39ffdb357752ca22d08ebcf6 kernel-debug-devel-2.6.18-410.el5.x86_64.rpm 81a8451290fe0e7dfaf57f00128965f73ea8dec1005cd4cc7c09b011a7d313ec kernel-devel-2.6.18-410.el5.x86_64.rpm 304092640b7c4f9311c6cc27453c28c32516dc29e9024edaea35bb5546f2e7ae kernel-doc-2.6.18-410.el5.noarch.rpm 2c6b31ab671e234557f538f300a0f41055277cd68774a298e1647d4c022d35ec kernel-headers-2.6.18-410.el5.x86_64.rpm 8a34a520288918670ded8b109d0a1b3b0e7ecb9c2f8da2576c5212dd18448af2 kernel-xen-2.6.18-410.el5.x86_64.rpm f5687120f37a3b8619029c0454a1334e7e6e88c2107912edb343f2b0b2f8d1a9 kernel-xen-devel-2.6.18-410.el5.x86_64.rpm Source: ac407137307e919622acb07705f4b42189bd75fc66c1ca29b558102a07842a4a kernel-2.6.18-410.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 135, Issue 6 ***********************************************

1 0

Openssl vulnerability
by aswathi.ok＠accenture.com 12 May '16

12 May '16

Hi Team, I have a centos 7 running server with openssl version openssl-1.0.1e-51.el7_2.4.x86_64, I have received a set of vulnerability from security team, can anyone tell me as per below CVE do I need to update my openssl version to 1.0.1t? Or the current version which we have is safe. CVE-2016-0701, CVE-2015-3197 CVE-2015-4000 CVE-2015-0204 CVE-2015-0286, CVE-2015-0287, CVE-2015-0289, CVE-2015-0293, CVE-2015-0209, CVE-2015-0288 CVE-2015-0292, CVE-2014-8176 Thanks Aswathi ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com

3 2

Re: [CentOS] Kernel 2.6.32-573.22.1.el6.x86_64, higher than usual load
by Laura Herrmann 12 May '16

12 May '16

I did a batch update on a number of Xen vservers, with kernel 2.6.32-573.26.1 being installed. In addition to load averages being high and these #s not being reflected by the individual CPU numbers within top, I now have a spattering of occasional daemon crashes that the vservers have historically never had. Such as, here is the start of a nameserver blowing up in my logs: May 12 04:03:41 XXX kernel: named invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 : # May 12 04:03:41 XXX kernel: named cpuset=/ mems_allowed=0 : # May 12 04:03:41 XXX kernel: Pid: 2208, comm: named Not tainted 2.6.32-573.26.1.el6.x86_64 #1 : # May 12 04:03:41 XXX kernel: Call Trace: : # This nameserver has never had a problem with its memory. And, there is another daemon on a different vserver that has done it twice, with the same sort of OOM thing. And.. what kind of sense does this make. top - 17:48:53 up 2 days, 9:10, 2 users, load average: 0.47, 0.29, 0.24 Tasks: 95 total, 1 running, 93 sleeping, 0 stopped, 1 zombie Cpu0 : 0.3%us, 0.7%sy, 0.0%ni, 96.7%id, 2.3%wa, 0.0%hi, 0.0%si, 0.0%st Cpu1 : 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st There's some problem here, at least because of the crashing out of nowhere on formerly-fine daemons. I'll be reverting all my kernels back to 2.6.32-573.18.1.

1 0

Reduce existing CentOS 7 installation to "Minimal install" - services?
by Nicolas Kovacs 12 May '16

12 May '16

Hi, When I install a CentOS server/desktop/workstation, I usually start from scratch with a barebone minimal installation, then add packages as needed. Some machines (like dedicated servers in a datacenter) come preconfigured by the hosting company, so I thought it wouldn't be a bad idea to start stripping that stuff first. Here's a little script I wrote, which essentially strips down any CentOS-7 installation to a minimal core system: https://github.com/kikinovak/centos/blob/master/7.x/scripts/00-elaguer-paqu… The script parses the 'minimal' package list and then just removes everything that's not on the list. Now I tried running that on an existing CentOS-7 "Web Server" installation. I ran it, rebooted... and I got dropped to a console that suggested to run journalctl. Uh oh. I'm currently catching up with systemd and its specificities, working through a bunch of online tutorials. But here's what I figured out so far. Before stripping down my system, I have to reduce services to a minimum. (On a Slackware system, which is what I'm using most of the time, that's where I would disable pretty much all services besides rc.syslog and rc.sshd.) Now what would be the simple systemd equivalent of doing that? E. g. on any CentOS installation (be it graphical, "Web Server", "File Server", whatever), strip down services to the status that they're at just after installing a "Minimal Install"? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

8 17

Official Docker images and security updates
by Giovanni Tirloni 11 May '16

11 May '16

Hello, It seems the official Docker images are missing some important security updates [1][2]. Does anyone have any insight in how these packages get built and when? Their Dockerfile seems to come from here: https://github.com/docker-library/official-images/blob/master/library/centos (commit for "latest" says "update CentOS-7 - 20160331 - monthly build"). In the official Docker documentation [2] they suggest not running `apt-get upgrade` which I understood as don't run `yum -y upgrade` for CentOS. Any advice on whether it's best practice to always update packages or not? Thank you, Giovanni 1 - http://pastie.org/pastes/10833370/text 2 - https://blog.docker.com/2016/05/docker-security-scanning/ 3 - https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practice…

1 0

openssl Security Update for CentOS 6.7 ETA
by Patrick Rael 11 May '16

11 May '16

Hi, Is there an ETA on the openssl security update (CVE-2016-0799) for CentOS 6.7? I saw the openssl update for CentOS 7 on 5/9, eagerly awaiting the same for 6.7. Thanks! -->Pat

7 9

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