Discuss

discuss@lists.centos.org

9 participants
34745 discussions

Start a nNew thread

semi-OT:apcupsd
by m.roth＠5-cent.us 18 Nov '17

18 Nov '17

I can't seem to find apcupsd for C 6. Just went to epel's website, and not visible. Anyone have a clue? mark

9 14

Re: [CentOS] semi-OT:apcupsd
by Miguel Medalha 18 Nov '17

18 Nov '17

>> I can't seem to find apcupsd for C 6. Just went to epel's website, >> and not visible. Anyone have a clue? I am running apcupsd on CentOS 6.9, monitoring through the network a common UPS that is physically connected to another server via USB. Just download the latest source code and compile it yourself. It's as easy as ./configure make make install No problems whatsoever.

1 0

CentOS-announce Digest, Vol 153, Issue 4
by centos-announce-request＠centos.org 18 Nov '17

18 Nov '17

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-2017:3247 Critical CentOS 6 firefox Security Update (Johnny Hughes) 2. CESA-2017:3247 Critical CentOS 7 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 17 Nov 2017 16:50:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:3247 Critical CentOS 6 firefox Security Update Message-ID: <20171117165004.GA21777(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:3247 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:3247 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d7077384cc2593c8bc462d76e5167ba9e8fd9bcc517c8ce01dc110ad259b7d6b firefox-52.5.0-1.el6.centos.i686.rpm x86_64: d7077384cc2593c8bc462d76e5167ba9e8fd9bcc517c8ce01dc110ad259b7d6b firefox-52.5.0-1.el6.centos.i686.rpm 61d760be7c4fc39ea73792b64bf1c795f2e69cb3da13897e2b3b0e60506f7648 firefox-52.5.0-1.el6.centos.x86_64.rpm Source: e1f638e27bac1f4aec6cbbec91a0bfda495c77f6f1089771cb7e45df32f1a616 firefox-52.5.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 17 Nov 2017 16:54:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:3247 Critical CentOS 7 firefox Security Update Message-ID: <20171117165429.GA21965(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:3247 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:3247 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 69d18c12d8754992222e09d20142293882e45d27e6998df7ea6a4134da97e11d firefox-52.5.0-1.el7.centos.i686.rpm 3fea84e873702db7febafaf1677c89d7038127c3280921b6e8498911618eb4a7 firefox-52.5.0-1.el7.centos.x86_64.rpm Source: 25633241b2c7d527db4cb389b1fb9a57e8b82cebc8c3794043eb0ddb074438d8 firefox-52.5.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 153, Issue 4 ***********************************************

1 0

CentOS Linux 6 to CentOS Linux 7 upgrade tool
by Johnny Hughes 17 Nov '17

17 Nov '17

We have asked several times on this list (and other places) for someone from the Community to maintain the Upgrade Tool for c6 to c7 upgrades. It was maintained for a very short period of time, and now that version no longer works. Info about the tool is here: https://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool If we can not get someone to maintain the tool, we are going to have to remove it from downloads as it no longer works. Will someone from the Community please step up and maintain it? Thanks, Johnny Hughes

1 0

USB Serial Ports
by Chris Olson 17 Nov '17

17 Nov '17

We have several CentOS 6 systems that are used in various configurations of test equipment. One of the primary functions of these systems is the connectivity to serial ports of some operational systems that have serial port control requirements. Lack of interface bus slots led us to the use of USB connected serial ports on these CentOS 6 systems. We first used these USB connected serial ports in our RHEL 5 test equipment systems. With RHEL 5, shut down and boot up of the systems would often cause the serial ports to have a different driver name, even though we had not changed the ports where the USB devices were plugged in. This caused software access problems until we discovered what could be done using the udev rules to lock in the driver names. This problem seems to have gone away in our newer systems with CentOS 6, and we would like to make sure that it does not return. We are deploying some of the systems and do not want to have software access issues in the field where fixes are more difficult. We would like to know if there is some underlying factor that has solved this problem for us. Any ideas on what to check would be greatly appreciated.

3 2

How to blacklist a device driver (sysemd)
by Frank Thommen 17 Nov '17

17 Nov '17

Hi, how can a specific device driver in CentOS 7 be blacklisted, so that it doesn't load at boot time? We have Infiniband adapters which are not completely supported by CentOS and we want to silence the error messages for the time being. I tried with the files /etc/modprobe.d/blacklist /etc/modprobe.d/blacklist.conf and with entries mlx5_core mlx5_ib blacklist mlx5_core blacklist mlx5_ib install mlx5_core /dev/null install mlx5_ib /dev/null all found on different websites. None of these entries helps. mlx5_core and mlx5_ib are still loaded and the system is flooded with error messages. Cheers frank

4 5

CentOS-announce Digest, Vol 153, Issue 3
by centos-announce-request＠centos.org 17 Nov '17

17 Nov '17

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. Re: CESA-2017:3200 Important CentOS 6 kernel Security Update (Johnny Hughes) 2. Re: CEBA-2017:3198 CentOS 6 cloud-init BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Nov 2017 09:44:51 -0600 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: Re: [CentOS-announce] CESA-2017:3200 Important CentOS 6 kernel Security Update Message-ID: <0d7e56f9-fbaf-38e9-32fc-862333dbc626(a)centos.org> Content-Type: text/plain; charset="utf-8" On 11/15/2017 03:38 PM, Johnny Hughes wrote: > > CentOS Errata and Security Advisory 2017:3200 Important > > Upstream details at : https://access.redhat.com/errata/RHBA-2017:3200 > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( sha256sum Filename ) > > i386: > 5d284bfa08a5793517ec76a246754d2f4645ac012336d27f1c5807380a4e256e kernel-2.6.32-696.16.1.el6.i686.rpm > f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114 kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm > 95a65d3b9b1aa4a02457dd53ad321c1118e937d452bd4082498141a7ea20ce7a kernel-debug-2.6.32-696.16.1.el6.i686.rpm > 3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9 kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm > 13442b6c43647b8160f8cc15d099f078a6b2550d00b322857c067d82b9cadb6c kernel-devel-2.6.32-696.16.1.el6.i686.rpm > 2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974 kernel-doc-2.6.32-696.16.1.el6.noarch.rpm > e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5 kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm > 4f1380ddb2db054ea518d9186c04e4148644f5f4f9c201fcc1a563b9e4ef487f kernel-headers-2.6.32-696.16.1.el6.i686.rpm > f04384bf339595bedfdcc7bc008a59968f090bade0a6b8148d9eb22eac4964f5 perf-2.6.32-696.16.1.el6.i686.rpm > 58f5d8fef44bd215d01559cdc53fee903b3f9f6544c67c67fcafd4587d8ca4b1 python-perf-2.6.32-696.16.1.el6.i686.rpm > > x86_64: > 9490bf087394c9c7e98444728438ab41ac99a44fbea99e8b22b39f7cebe7b1ca kernel-2.6.32-696.16.1.el6.x86_64.rpm > f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114 kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm > 9b754666727e4b8802f448a84279eff3a02285a227af4fa3199ed761798d7965 kernel-debug-2.6.32-696.16.1.el6.x86_64.rpm > 3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9 kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm > 0da6ec2f05ed53d70b115c475f86b01ddbc11f85fe116127f648316265c565a3 kernel-debug-devel-2.6.32-696.16.1.el6.x86_64.rpm > 2fa496dc3ece90d97886030754340d8dd4f5816c3cad2182de275b1f0007ef75 kernel-devel-2.6.32-696.16.1.el6.x86_64.rpm > 2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974 kernel-doc-2.6.32-696.16.1.el6.noarch.rpm > e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5 kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm > 6f451f1500fbcefac11541065c607cca80afcd74910dd72b54d8a659826835aa kernel-headers-2.6.32-696.16.1.el6.x86_64.rpm > e72ba7452350e398030e8d65bd53830cb003964c1444cc823378db5792b6588b perf-2.6.32-696.16.1.el6.x86_64.rpm > ce90fe8a317164248e18390182d9a4d4e1cf60c2aa13fd07d3df53bc8561ea1b python-perf-2.6.32-696.16.1.el6.x86_64.rpm > > Source: > 2909a2f8bd8cda02978aa674da4a7b0fbbabc65d817131193bdd50a11bf60555 kernel-2.6.32-696.16.1.el6.src.rpm > > > Actual Link: https://access.redhat.com/errata/RHSA-2017:3200

1 0

HP laptops with CentOS 7?
by Sorin Srbu 17 Nov '17

17 Nov '17

Hello all, I'm looking into getting HP laptops for our department running CentOS 7. Last time I checked this was some five or so years ago, and when I look at https://wiki.centos.org/HowTos/Laptops, nothing much seems to have happened since. At that time, I had to give up CentOS on laptops, as both Wi-Fi and graphics wasn't too well supported with CentOS 5 and 6. Is the situation better now with CentOS 7? We're only allowed to buy the HP, Dell and Apple brands here at this university, so what I'm looking at is basically HP. Apple is not of interest because of their pricing. All our desktops and laptops are HP's running Windows 7 and 10, and they work fine. We do have some Dells, but only in the server area. Currently all our CentOS 6 and 7 workstations are custom built OEMs used for molecular modelling, but are now getting rather long in the tooth. I have a laptop at the office as a backup, running Ubuntu 16 LTS, as that was the only thing that found all the hardware properly at the time. However, I'd rather not go down that particular road for various reasons. The thing that interests me first and foremost is whether the latest CentOS 7 iteration will install right out of the box with all hardware properly detected, no manual compiling of drivers or jumping through hoops to _maybe_ getting stuff to work with eg a HP Elitebook 850 G4. Anybody care to chime in with a comment or hint on the laptop situation and-or their experiences? -- BW, Sorin ----------------------------------------------------------- # Sorin Srbu, Sysadmin # Uppsala University # Dept of Medicinal Chemistry # Div of Org Pharm Chem # Box 574 # SE-75123 Uppsala # Sweden # # Phone: +46 (0)18-4714482 # Visit: BMC, Husargatan 3, D5:512b # Web: http://www.orgfarm.uu.se ----------------------------------------------------------- # O< ASCII ribbon campaign - Against html E-mail # http://tinyurl.com/ascii-ribbon-campaign # # This message was not sent from an iProduct! # # Please consider the environment before printing this email. # Join the campaign at http://thinkBeforePrinting.org # # MotD follows: A father is a banker provided by nature.

9 30

CentOS 7 "Set Up Enterprise Login" after update and reboot
by Valeri Galtsev 16 Nov '17

16 Nov '17

Dear Experts, Something went astray with one of my systems. Large number of updates were installed on it all at once at some point. Then after system was rebooted it does strange thing I haven't seen on other systems. The machine is set up to boot into graphic login ("runlevel 5" to say it using outdated language). But before giving login screen upon (re)boot it tries to walk you through set of screens similar to first login to newly created account. However, along that it forces to to "Set Up Enterprise Login", and there is no way to bypass that, or kill this thing to get graphic login screen. As of this moment I suspect that something went astray during big update. I'm not excluding system compromise, however as of this moment this seems unlikely, as this system while online is constantly watched for "system integrity" (i.e. all files that only root should be able to touch are monitored for their checksums, etc.) and I would be alerted earlier were anything wrong. Rolling back big update (using yum history) failed, I am going to restore all on the box to the state before that big update (and I also can just wipe the drive and reinstall the system). So I kind of have ways out. Still, if anyone can shed some light onto what could have happened, or what could have accidentally get changed, it would be really great. I can ssh to the box, and I can switch it to "runlevel 3" and back... Thanks in advance to everybody who will respond for your insights! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

2 1

Re: [CentOS] CentOS 7 "Set Up Enterprise Login" after update and reboot
by Richard 16 Nov '17

16 Nov '17

> Date: Thursday, November 16, 2017 15:31:32 -0600 > From: Valeri Galtsev <galtsev(a)kicp.uchicago.edu> > > Dear Experts, > > Something went astray with one of my systems. Large number of > updates were installed on it all at once at some point. Then after > system was rebooted it does strange thing I haven't seen on other > systems. The machine is set up to boot into graphic login > ("runlevel 5" to say it using outdated language). But before giving > login screen upon (re)boot it tries to walk you through set of > screens similar to first login to newly created account. However, > along that it forces to to "Set Up Enterprise Login", and there is > no way to bypass that, or kill this thing to get graphic login > screen. > > As of this moment I suspect that something went astray during big > update. I'm not excluding system compromise, however as of this > moment this seems unlikely, as this system while online is > constantly watched for "system integrity" (i.e. all files that only > root should be able to touch are monitored for their checksums, > etc.) and I would be alerted earlier were anything wrong. > > Rolling back big update (using yum history) failed, I am going to > restore all on the box to the state before that big update (and I > also can just wipe the drive and reinstall the system). So I kind > of have ways out. > > Still, if anyone can shed some light onto what could have happened, > or what could have accidentally get changed, it would be really > great. > > I can ssh to the box, and I can switch it to "runlevel 3" and > back... > > > Thanks in advance to everybody who will respond for your insights! > > Valeri > I ran into the "first boot" (though not "set up enterprise login") issue after C-7 updates in mid-september. This only happened on one of three C-7/mate desktop machines. With "first boot" I went through the process, including setting up an account, that was added to wheel as a part of the process. I then logged out of that and was able to get into my regular account (via the gui) just fine. I removed that spurious account and cleaned things up, but ended up in "first boot" again the next time the machine was rebooted. So, I've now neutered that account, but left it in place and haven't run into "first boot" again. I haven't been able to figure out what caused this, yet.

1 0

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