Discuss

discuss@lists.centos.org

3 participants
34748 discussions

"installation source" specification for netinstall
by ken 21 Dec '15

21 Dec '15

Trying to specify the "installation source" in the configuration of netinstall for centos 7 (7.1). Three places on the web said mirror.centos.org/centos/7/os/x86_64/ But that configuration page probes, then it says, "Error setting up base repository". What's the magic needed? Also, if anyone knows specs for epel and others, they might help too. Thanks.

6 23

CentOS-announce Digest, Vol 130, Issue 9
by centos-announce-request＠centos.org 21 Dec '15

21 Dec '15

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-2015:2668 CentOS 6 watchdog FASTTRACK BugFix Update (Johnny Hughes) 2. CESA-2015:2671 Important CentOS 5 jakarta-commons-collections Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sun, 20 Dec 2015 17:40:13 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:2668 CentOS 6 watchdog FASTTRACK BugFix Update Message-ID: <20151220174013.GA28981(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:2668 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2668.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d7a9fb01a178a2dbb1a93d5e5ca7d8744e26ade820da1e95c8250d4a88d7acd2 watchdog-5.6-5.el6.i686.rpm x86_64: 9a8101cf52bba32ec1e6c653683ec5468aeb81ec972785136023c2a2f19923ec watchdog-5.6-5.el6.x86_64.rpm Source: d5a4e034185b85e189da7bdf77fad1bf1fea5ff8bf41e18da4f214966b075792 watchdog-5.6-5.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 21 Dec 2015 11:17:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2671 Important CentOS 5 jakarta-commons-collections Security Update Message-ID: <20151221111735.GA12735(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2671 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2671.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3e91e8870eb490c06269ba53179728b3afbe6df74144a5033bd5d762591f3b3b jakarta-commons-collections-3.2-2jpp.4.i386.rpm e204902787c9476bbeee8f399eef182ddbe8dac776d6ddd23850498558ed4399 jakarta-commons-collections-javadoc-3.2-2jpp.4.i386.rpm 81ca9f0edcf5d0cde39f5f6f81c7535ddd5f01c444e731e3387b947751f2a696 jakarta-commons-collections-testframework-3.2-2jpp.4.i386.rpm 1401ddec74229e5f7bb0da50a3d5c47b7912a2276296284096394f73c37a85b6 jakarta-commons-collections-testframework-javadoc-3.2-2jpp.4.i386.rpm ab3d96dfe6aebc3c7b4f7ce7f0f307ddc210b1885e72ccf2d14bb9427bcd315a jakarta-commons-collections-tomcat5-3.2-2jpp.4.i386.rpm x86_64: 74add7a4f0f7879d2108f06e5216602dd05963b88c7984b6d247d136578dc449 jakarta-commons-collections-3.2-2jpp.4.x86_64.rpm 48eb0f726e79b462a8505f7960481006a6c252bccbf37a3cccbb416030b48da8 jakarta-commons-collections-javadoc-3.2-2jpp.4.x86_64.rpm 0934cf0cb13caf4cbac653a13895b933648e40a76a4d900c8b08d1a51d2a5231 jakarta-commons-collections-testframework-3.2-2jpp.4.x86_64.rpm 314c67cfaf4bef3c95326d83fa164d64c3ede371d7c712e40598e12eebe42064 jakarta-commons-collections-testframework-javadoc-3.2-2jpp.4.x86_64.rpm 356b54c0aded684d0d0b7f5ecc056c2f62f666011c84c342b95a6863b4499b87 jakarta-commons-collections-tomcat5-3.2-2jpp.4.x86_64.rpm Source: 1470c341f4d068e5c6fe3f8dc619f4a2be4ab7c0b720a54dd15a80a3fe1d5502 jakarta-commons-collections-3.2-2jpp.4.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 130, Issue 9 ***********************************************

1 0

Supermicro CentOS 7 install failure
by dsavage＠peaknet.net 21 Dec '15

21 Dec '15

My workhorse server is a SuperMicro with their H8DM8-2 motherboard. For many years it ran CentOS 5.x and 6.x until the boot drive failed last year. I installed a 1TB SSD as /dev/sda and planned to install CentOS 7 on it, replacing CentOS 6.5 on the failed drive. Unfortunately every CentOS 7 media I tried, either optical disk or USB thumb drive, breaks down just a few seconds after selecting "Install..." The H8DM8-2 motherboard is based on the nVidia MPC55 Pro and NEC uPD720400 chipsets. It has an on-board Adaptec AIC-7902W dual-channel SCSI controller and companion Zero-Channel RAID card. It has twin AMD Opteron HE processors and 32GB of registered ECC DDR2 memory. The RAID array is populated with ten Fujitsu 300GB 15K SCSI3 drives. I took it into a friendly Linux shop where they reviewed / verified all of my work and confirmed the boot-time problem. Two hours into the effort, my friend plugged in a bootable Windows 10 thumb drive and to our amazement, it came up very normally. So did another thumb drive with a Fedora 23 installation image. So there's nothing wrong with my hardware. We believe the problem is due to Red Hat compiling RHEL7 without at least one old device driver that I still need. My friend thinks we should build an installation disk from a modified CentOS 7 live CD kickstart file and a CentOS-Plus kernel. While that may work, I think there may be a simpler boot-time kernel option I could use to successfully install from a stock ISO. Does anyone have any suggestions for boot-time options I could try? --Doc Savage Fairview Heights, IL

2 1

yum/RPM and Trust on First Use
by Alice Wonder 21 Dec '15

21 Dec '15

I'm not on the yum / RPM list and I don't know that I want to join just to discuss this but with respect GPG keys - it is a classic example of trust on first use. The first time yum installs a package, it asks to import the GPG key used to sign the packages. Most people accept without validating the key. This is potentially exploitable because most repositories are http What if there was a DNS TXT record that corresponds with the repository, with the fingerprint of the key? The DNS record could be DNSSEC secured (I believe Fedora already uses DNSSEC - some of their servers anyway) and yum could refuse to ask if the fingerprint of the key it is importing does not match the DNSSEC secured fingerprint. Something like TXT record for _rpmkey.security.centos.org. could be requested for the fingerprint for security(a)centos.org Advantage over gpg keyrings is that it can be implemented by anyone without needing to manage your keys with specific gpg keyrings, which has always been messy. When yum is first asked to import a key, it refuses if it can not DNSSEC validate the fingerprint. After it DNSSEC validates the fingerprint, it can then does what it currently does, where the user can verify they trust the key. To get a fingerprint in the centos.org zone and signed by DNSSEC would not be easy for a malicious packager to do. Furthermore when a signing key has been compromised (happened with Fedora once) changing the DNS record would prevent the key from being imported in the future, and could even prevent packages signed by that key from being installed in the future even if the key is already imported. For offline yum usage, a switch could be used to tell yum not to do the DNS lookup and DNSSEC validation. Thoughts?

6 16

Power Management
by Chris Olson 20 Dec '15

20 Dec '15

Recent power management discussions plugged into one of our current frustrations, namely the interaction of the screen lock and power-save features on Intel/CentOS 6 platforms. We certainly would not have guessed that locking the screen would inhibit going into the power-save mode, but it sure seems to do exactly that on some of our test platforms. If one leaves the desktop idle for the timeout period, the computer sleeps. If one locks the screen and then leaves the machine idle, the computer does not sleep. We were hoping that this "feature" was isolated to just our older Dell desktop machine hardware and firmware, but it appears elsewhere as well. Possibly more interesting is that most of our systems were loaded with CentOS 6.X almost two years ago and have been updated at least weekly ever since. This new power-save scenario has appeared just within the last three weeks,and our investigations have not discovered the cause ora solution.

3 2

Critical problem with power management CentOS 7.2
by Alice Wonder 20 Dec '15

20 Dec '15

Thinkpad T410 running CentOS 7 with the Mate desktop (Gnome 3 is too demanding on video capabilities for this hardware) Under CentOS 7.1 - the laptop would sleep when I closed the lid. It no longer does. I can tell because the laptop remains warm when I close the lid now, mail filters in Thunderbird run when the lid is closed, and it doesn't need to re-establish wifi when opening. This is dangerous because thinkpads cool through the keyboard. The battery usage monitor also no longer works. It shows 99% battery even as the laptop starts giving its warning beep that the battery is exhausted and it is about to shut down. Anyone know what broke with the update to 7.2 and how to fix it? No 3rd party kernel modules are involved. -- -=- Sent my from my laptop, may not be able to respond timely

3 5

fail2ban problem new installation
by Günther J. Niederwimmer 20 Dec '15

20 Dec '15

Hello, I have a big problem with fail2ban and firewalld on my new system. I have a server running (CentOS 7.1) and run a Update to 7.2 on this system all is working ? BUT I install a new system with CentOS 7 1511 on this systems fail2ban don't work anymore. I have this error or more, in the firewalld 2015-12-19 08:39:55 ERROR: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -I INPUT_direct 1 -p tcp -m multiport --dports ssh -m set --match-set fail2ban- sshd src -j REJECT --reject-with icmp-port-unreachable' failed: iptables v1.4.21: Set fail2ban-sshd doesn't exist. Try `iptables -h' or 'iptables --help' for more information. Is on 7.2 some missing or not installed I installed fail2ban from the epel repo. Thanks for a answer, -- mit freundlichen Grüßen / best regards, Günther J. Niederwimmer

3 3

LDAP create home directories
by Tim Dunphy 20 Dec '15

20 Dec '15

Hey guys, I've setup an LDAP server on our network. I'm using OpenLDAP. It was really easy to use the authconfig-tui to generate the nsswitch.conf and ldap.conf files that would allow user authentication. But when users would log in, the system wasn't creating the home directories. I found one command that would correct that: authconfig --enablemkhomedir --update After that logging in with an LDAP user to that machine would create the home directories. But that only worked on the first machine. Running the command on other machines would have no effect. Which is odd. You would think it would be consistent. Even after copying over the entire contents of /etc/pam.d from the working machine to the non-working machine and making sure that the non-working machine had the same /etc/nsswitch.conf /etc/openldap/ldap.conf as the one that worked. It still doesn't create the home directories when LDAP users log in. The non-working machine also has the required librariy file: -rwxr-xr-x. 1 root root 11176 Aug 18 10:56 /usr/lib64/security/pam_mkhomedir.so So how can I fix this? How can I get the system to create home directories for LDAP users automatically? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

3 5

playing DVDs on C7
by Fred Smith 20 Dec '15

20 Dec '15

Hi all! I'm trying to finish setting up my newly upgraded C7 system. It's on the same hardware I ran C6 on for several years. on C6 I had no trouble playing DVDs (after installing tons of packages and libdvdcss). Well, on C7, I've got totem (videos) and all its plugins I can find via yum, VLC (from nux) all the gstreamer and gstreamer1 packages I can find, everything with "dvd" in its name, including libdvdcss from nux. vlc will kinda play movies, i.e., moving garbage appears on the screen, sometimes it'll resemble something from the movie, but most of the time not so much. I can't figure out what's missing here. Totem played a movie for me this afternoon, flawlessly, but now I can't get it to do anything. sometimes it starts up as a plain gray box with no borders, no controls, no nothing, and has to be killed. sometimes it draws the player controls but never starts playing. I've got two DVD drives, one of them replaces a broken one, but the other one has been there for 2-3 years. I've been googling for hours, but haven't turned up anything that I haven't already tried. I'd appreciate suggestions. thanks in advance! here's some yum listings of things I have installed: yum list installed | grep -y dvd dvd+rw-tools.x86_64 7.1-15.el7 @anaconda libdvdcss.x86_64 1.2.13-1.el7.nux @nux-dextop libdvdnav.x86_64 4.2.0-8.el7 @anaconda libdvdread.x86_64 4.2.0-6.el7 @anaconda radvd.x86_64 1.9.2-9.el7 @base yum list installed | grep -y vlc vlc.x86_64 2.2.1-6.el7.nux @nux-dextop vlc-core.x86_64 2.2.1-6.el7.nux @nux-dextop vlc-extras.x86_64 2.2.1-6.el7.nux @nux-dextop yum list installed | grep -y totem totem.x86_64 1:3.14.3-5.el7 @cr totem-nautilus.x86_64 1:3.14.3-5.el7 @cr totem-pl-parser.x86_64 3.10.5-1.el7 @cr yum list installed | grep -y gstreamer PackageKit-gstreamer-plugin.x86_64 1.0.7-5.el7.centos @cr gstreamer.x86_64 0.10.36-7.el7 @anaconda gstreamer-ffmpeg.x86_64 0.10.13-15.el7.nux @nux-dextop gstreamer-plugin-crystalhd.x86_64 3.10.0-11.el7 @epel gstreamer-plugins-bad.x86_64 0.10.23-5.el7.nux @nux-dextop gstreamer-plugins-bad-free.x86_64 0.10.23-20.el7 @anaconda gstreamer-plugins-bad-nonfree.x86_64 0.10.23-2.el7.nux @nux-dextop gstreamer-plugins-base.x86_64 0.10.36-10.el7 @anaconda gstreamer-plugins-good.x86_64 0.10.31-11.el7 @anaconda gstreamer-plugins-ugly.x86_64 0.10.19-17.el7.nux @nux-dextop gstreamer-tools.x86_64 0.10.36-7.el7 @anaconda gstreamer1.x86_64 1.4.5-1.el7 @cr gstreamer1-libav.x86_64 1.0.6-1.el7.nux @nux-dextop gstreamer1-plugins-bad-free.x86_64 1.4.5-3.el7 @cr gstreamer1-plugins-bad-freeworld.x86_64 gstreamer1-plugins-base.x86_64 1.4.5-2.el7 @cr gstreamer1-plugins-good.x86_64 1.4.5-2.el7 @cr gstreamer1-plugins-ugly.x86_64 1.0.6-2.el7.nux @nux-dextop -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

4 8

Serial Communication
by Chris Olson 19 Dec '15

19 Dec '15

Many years ago, we began scrapping the RTOS approach for some of our timing-critical applications. Our first applications were based on Solaris real-time extensions and served well us well for many years. Then came the era of shaky support for Intel Solaris and we moved many applications to Linux. There appeared to be no actual need for special real-time features with a good Linux distribution kernel and a GHz processors. One of our most productive applications involves special test equipment computers that drive high speed serial ports. The original development of these systems had the "added benefit" of helping us to learn udev rules. The serial communication is very flexible and most of it is script driven. A current need to update computing platforms is driving script review. There appears to be a bit of variety in outputs to the serial drivers. The echo of a string with redirection to the serial driver, cat of a file with redirection to the serial driver and dd of=/dev/.... are methods used at various places in the scripts. It is not at all clear what drove the choice of the output method at various points in the application. In addition, changing the method of output has not succeeded in breaking most of the applications. Is there some fundamental difference between these methods of output to the driver that might trip us up as we simplify the scripts and port to new computer platforms? Thanks in advance for any assistance.

2 1

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