Discuss

discuss@lists.centos.org

3 participants
34748 discussions

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

10 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. CESA-2015:2594 Moderate CentOS 6 libpng Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 9 Dec 2015 14:47:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2594 Moderate CentOS 6 libpng Security Update Message-ID: <20151209144729.GA33887(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2594 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2594.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e4b2fabf9c232b1a84e677df640aceab8b089e72781bec4fcca347d984e581d1 libpng-1.2.49-2.el6_7.i686.rpm c3b0f3d20047a8cef357a96171787aaffcf74ae93bb0b0faff1bca3001315586 libpng-devel-1.2.49-2.el6_7.i686.rpm c37977232c45d61ad118af010e21d611c4e98403b87ffd76bc645474c8754a2e libpng-static-1.2.49-2.el6_7.i686.rpm x86_64: e4b2fabf9c232b1a84e677df640aceab8b089e72781bec4fcca347d984e581d1 libpng-1.2.49-2.el6_7.i686.rpm 0f18ee677b60fe81a24f200cc8db1c9bde26a404cc812e77a73b2bcfd4dd40de libpng-1.2.49-2.el6_7.x86_64.rpm c3b0f3d20047a8cef357a96171787aaffcf74ae93bb0b0faff1bca3001315586 libpng-devel-1.2.49-2.el6_7.i686.rpm 6e30263282f29b65af97733f7704647e615ff857902ebf87927ba276a5230e3a libpng-devel-1.2.49-2.el6_7.x86_64.rpm 8d2cc2d3ed0e4c3d794c847f79d98b63caae912e869ff2f6ada349b1c3c2772e libpng-static-1.2.49-2.el6_7.x86_64.rpm Source: e756441baabe4038f09eb9dbe4207e83d347f21cbe805eb4956c2cd961a891db libpng-1.2.49-2.el6_7.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 3 ***********************************************

1 0

CentOS 6, bareos, kerberos?
by m.roth＠5-cent.us 09 Dec '15

09 Dec '15

After upgradeding to bareos 15.2, which also has a web ui, thereby making it usable (since the command line tool, bconsole, does not have a paging mechanism, and its sytax for choosing files to restore is, let us say, arcane), I've got another question: is *anyone* using bareos with kerberos? I see that they have in alpha(?) tls support, which isn't a great idea, given the recent vulnerabilities.... If you've figured out how to use kerberos, rather than hard-coding a password in the console configuration, I'd love to hear it. mark

2 2

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]
by James B. Byrne 09 Dec '15

09 Dec '15

On Mon, December 7, 2015 13:41, Matthew Miller wrote: > On Fri, Dec 04, 2015 at 09:03:50AM -0500, James B. Byrne wrote: >> On Thu, Dec 03, 2015 at 02:50:38PM -0500, m.roth(a)5-cent.us wrote: >> > For laptops, great. For anything else, not so much. For example, >> > it's supposed to be an *ENTERPRISE* o/s... why does it >> > automatically, without ever asking, install anything wifi? I'm > [...] >> The short answer: Because RHEL is based on Fedora development. > > > This is roughly true, although "downstream" RHEL makes its own > decisions about many things. If you (Mark, or anyone else) would like > to make this different in the future, getting involved with Fedora > Server is a good way to do so. > I subscribe to the Fedora Server list digest. Which form also is how I get this list's messages. Thus the delay in my responses. However, to describe the Server List as an active forum for discussion would be somewhat overstating things. I have not received anything from it as yet in December and the total volume of traffic on that list in November was very light. I am not sure in what way you envisage additional involvement is to take place. I have been bitten by things done in Fedora that only have any use on a laptop and that should never have been allowed into a server distribution. But I cannot see how I would have been aware of them until they manifested themselves on equipment under my care. By which time it is rather too late to influence the decision to include them. Automatically powering down NICs comes to my mind; due the rather nasty consequences that resulted. The difficulty is that with Free and Open Source Software you are only going to see features that are of some immediate use to the writers; or whose value has already been entrenched such that it is difficult if not impossible to dispense with. Clearly, power saving features are of some interest to people that run their systems on batteries. However, there are batteries, and then there are batteries. We occasionally run run on batteries too. It is just that ours are measured in kilovolt-amp hours. Having a server distro configured by default to turn off a NIC because it has not had traffic for fifteen minutes is not going to save us enough power from now to the end of eternity to warrant the disruption that little 'feature' cost us when it was first encountered. The move to Systemd, and all the controversy that decision has generated, also provides 'features' whose benefits appear to me be be aimed principally at users who shut their systems off every day. These benefits are of far less value to people who measure uptime in months or years, while the discomfort, and expense, of this change must be borne regardless. Systemd will eventually be accepted or rejected on its own merits. I am not interested in debating them here since I have nothing upon which to base an opinion one way or the other. But it can hardly be denied that forcing highly qualified people to expend time, a very limited resource in my experience, to learn yet another way to start a computer system, without providing any readily discernible benefit to them, is not likely to engender much in the way of sympathy. We went to RedHat and ended up on CentOS because of its server orientation. Which to us implied something more than simple compatibility of the software components. If RedHats's intent is to end up as a laptop distro then we will probably part ways at some point. We have a laptop distro that works well for us. It is called OSX. And the hardware is pretty good too. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

USB devices - libgphoto2 - PTP - hplip
by Michael H 09 Dec '15

09 Dec '15

Hi All, I'm trying to disable USB storage devices in Centos7.1.1503. I've setup udev rules to block all usb devices and then additional rules to allow specific vendors / products to be used (mainly keyboards and mice). This is all working perfectly. cat /etc/udev/rules.d/01-usblockdown.rules # Block all USB devices ACTION=="add", SUBSYSTEMS=="usb", RUN+="/bin/sh -c 'for host in /sys/bus/usb/devices/usb*; do echo 0 > $host/authorized_default; done'" # Allow devices # Keyboards ACTION=="add", ATTR{idVendor}=="04f3", ATTR{idProduct}=="0103" RUN+="/bin/sh -c 'echo 1 >/sys$DEVPATH/authorized'" ...... Now I'm testing against mobile devices and when I connect an Asus mobile telephone it's mounting the camera using PTP even though the device is not allowed in my udev rules. I removed libgphoto2 which has now stopped the PTP from automounting. My issue is that I require hplip on my systems for certain printer drivers and this package was removed along with libgphoto2. I added an 'exclude=libgphoto2*' to my /etc/yum.repos.d/CentOS-Base.repo and installing hplip now fails on dependencies. Is there a method of disable libgphoto2 PTP without having to remove the package? or can I create further udev rules to stop PTP mounts? thanks in advance, Michael

1 0

CentOS 6 pci audio card not enabled
by clark＠west.net 08 Dec '15

08 Dec '15

CentOS 6 up-to-date 2.6.32-573.8.1.el6.x86_64 Gigabyte GA-Z68P-DS3 on-board audio BIOS disabled. Intel I5 Pny 550Ti video Envy 24HT pci audio module I want to use the fiber in/out of the audio card, but it is not listed in System/Preferences/Sound/Hardware, only the HDMI is available. It was installed in the pci slot when the system CentOS 6.0 was installed. I have searched all over Google, but can't find a solution. Does anyone have a solution for this problem ? Advice will be appreciated. thanks in advance! [mumbles@120db ~]$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 [mumbles@120db ~]$ lspci | grep -i audio 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) 05:00.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01) [mumbles@120db ~]$ lspci -k <snip> <snip> 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) Subsystem: Device 196e:089c Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel <snip> <snip> 05:00.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01) Subsystem: VIA Technologies Inc. Albatron PX865PE 7.1 Kernel modules: snd-ice1724 [mumbles@120db ~]$ lspci -n | grep 05:00.0 05:00.0 0401: 1412:1724 (rev 01) [mumbles@120db ~]$ grep 1724 /lib/modules/$(uname -r)/modules.pcimap snd-ice1724 0x00001412 0x00001724 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 [mumbles@120db ~]$ modinfo snd-ice1724 filename: /lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/sound/pci/ice1712/snd-ice1724.ko license: GPL description: VIA ICEnsemble ICE1724/1720 (Envy24HT/PT) author: Jaroslav Kysela <perex(a)perex.cz> srcversion: 4159E44B9111EFB98548209 alias: pci:v00001412d00001724sv*sd*bc*sc*i* depends: snd,snd-ac97-codec,snd-pcm,snd-i2c,snd-ice17xx-ak4xxx,snd-rawmidi,snd-pt2258,snd-ak4xxx-adda,snd-ak4114 vermagic: 2.6.32-573.8.1.el6.x86_64 SMP mod_unload modversions parm: index:Index value for ICE1724 soundcard. (array of int) parm: id:ID string for ICE1724 soundcard. (array of charp) parm: enable:Enable ICE1724 soundcard. (array of bool) parm: model:Use the given board model. (array of charp)

1 0

openvpn + routing
by Axel Glienke 08 Dec '15

08 Dec '15

Hello, i have a little question. My system: ip route: 0.0.0.0/1 via 10.8.0.5 dev tun0 default via 192.168.2.1 dev br0 proto static metric 425 10.8.0.1 via 10.8.0.5 dev tun0 10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6 88.198.140.127 via 192.168.2.1 dev br0 192.168.2.0/24 dev br0 proto kernel scope link src 192.168.2.101 metric 425 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 traceroute gmx.de traceroute to gmx.de (213.165.65.60), 30 hops max, 60 byte packets 1 Speedport.ip (192.168.2.1) 0.578 ms 0.662 ms 0.859 ms ^C [root@h1 ~]# traceroute spiegel.de traceroute to spiegel.de (62.138.116.3), 30 hops max, 60 byte packets 1 10.8.0.1 (10.8.0.1) 35.009 ms 34.982 ms 34.956 ms Why the routing is different, in first case over br0 in second over the vpn device? How can i disable "push default route" from the server-directive on client-side in OpenVPN? I want, that only traffic, incoming over tun0 routing back over tun0. Is this possible with firewalld-cmd? Thx. Grüße Axel

5 5

yum errors
by Wes James 08 Dec '15

08 Dec '15

I have inherited centos 6.3 and 6.2 vms in an esxi environment. When I do yum provides ntpd on the 6.3 box I get a lot of errors like: Loaded plugins: fastestmirror, presto Loading mirror speeds from cached hostfile * base: mirror.unl.edu * extras: mirrors.cmich.edu * updates: mirror.steadfast.net http://mirror.unl.edu/centos/6.4/os/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" Trying other mirror. http://mirror.ash.fastserv.com/pub/linux/centos/6.4/os/x86_64/repodata/repo…: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" Trying other mirror. http://mirrors.einstein.yu.edu/centos/6.4/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirrors.einstein.yu.edu/centos/6.4/updates/x86_64/repodata/repomd.xml: (28, 'connect() timed out!') Trying other mirror. http://mirrors.versaweb.com/centos/6.4/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirrors.versaweb.com/centos/6.4/updates/x86_64/repodata/repomd.xml: (28, 'connect() timed out!') Trying other mirror. Why am I getting these errors? I installed 6.4 in virtualbox and the .repo files seem the same, except the 6.3 box didn’t have a fastback.repo file. Also why is it looking at 6.4 repos above? When I see: cat /etc/redhat-release CentOS release 6.3 (Final) i.e., this box is 6.3. Shouldn’t it be looking for 6.3 repo info? Thanks, -wes

8 24

Version numbering vis a vis CentOS and RHEL
by Phelps, Matthew 08 Dec '15

08 Dec '15

OK, I'm staring a new thread. On Mon, Dec 7, 2015 at 9:53 AM, Timothy Murphy <gayleard(a)eircom.net> wrote: > Phelps, Matthew wrote: > > >> > Oh, wait: CentOS, love it or leave it. > >> > >> Correct. > >> > >> In fact, I would prefer you leave. > > > > Really? > > > > This is what we're dealing with now? > > > > OK. I will recommend we move away from CentOS. > > This seems to be raising what to me is a trivial issue > to an absurd level of hostility. > Johnny Hughes' comment was uncharacteristically harsh; > and yours is even harsher. > > To me, CentOS is a highly stable OS for my home servers, > and I am eternally grateful to Johnny Hughes and his colleagues > for carrying out what looks to me like an impossibly complex task. > > The numbering of packages is a very small part of this. > On the other hand, a kernel panic would be very worrying to me > if it were in fact likely to happen. > I am glad to hear that I have no need to worry. > To you, and probably a majority of CentOS users, the "version number" of CentOS is indeed a trivial, cosmetic issue. However, there are those of us who use CentOS in a very large enterprise environment. That is, in fact, the intended audience of the whole distro. When there is a "new version" of Red Hat (and I know that means nothing with hundreds of constantly updating packages; however, my bosses don't get that), and hence CentOS, there is a huge amount of work that needs to be done in a typical enterprise. These include, but are not limited to: - setting up a new internal-only mirror of the distribution - setting up a new tftp/PXEboot/kickstart environment for network installs. - Editing several install scripts to match the new environment - Testing all these changes - Checking that all security recommendations/edicts from a higher authority (e.g. the US Government), which are also based on the "version", are followed - Checking that all commercial software supports the release (most of these use "RHEL X.y", what is that in CentOS now?) - Trying to get support from commercial software when the "version numbers" don't match - Coordination of other repositories (e.g. EPEL) is based on the "version", how does that work now? All of these things ran in parallel with the RHEL release cycle, and the work could be done at the same time. That was the overriding philosophy of CentOS, "we are a recompile of RHEL." Now, the impression is (rightly or wrongly, it doesn't matter to me) CentOS is totally becoming a separate Linux distro, and needs to be treated as such. And that has huge implications for system administrators in a large environment. Huge. There are answers to all these questions, but there is a lot of confusion that's been generated by this seemingly cosmetic change in version numbers. I've checked, and there was no,"We're considering creating this basic difference from RHEL, how will this affect you?" on this list, or the website, etc. From our viewpoint, it was sprung on us out of nowhere, and now were being told "deal with it, or leave." It sucks. -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps(a)cfa.harvard.edu, http://www.cfa.harvard.edu

10 15

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

08 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. CESA-2015:2549 Moderate CentOS 6 libxml2 Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 7 Dec 2015 13:26:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2549 Moderate CentOS 6 libxml2 Security Update Message-ID: <20151207132633.GA36846(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2549 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2549.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ef6fc5b110883e8b85e6e0aadb0dece190506569ba1c25247b612ffee5e10e7c libxml2-2.7.6-20.el6_7.1.i686.rpm 02e4ba1fea746762064a0fc7ba37d9fa1626cefd43257360db633fb23007c1d7 libxml2-devel-2.7.6-20.el6_7.1.i686.rpm d45068dcb62936bfd95e45182c807339dc060963d97adeae4d7717943a0107df libxml2-python-2.7.6-20.el6_7.1.i686.rpm 3c14ee97b4f56ede803f59fcdadb4786e3e4ab6792d68e7b509e7a346973b363 libxml2-static-2.7.6-20.el6_7.1.i686.rpm x86_64: ef6fc5b110883e8b85e6e0aadb0dece190506569ba1c25247b612ffee5e10e7c libxml2-2.7.6-20.el6_7.1.i686.rpm 6c42e07b5804dc8c346d5fa29755a515e8338618fc2b228959e4449e0d7b3227 libxml2-2.7.6-20.el6_7.1.x86_64.rpm 02e4ba1fea746762064a0fc7ba37d9fa1626cefd43257360db633fb23007c1d7 libxml2-devel-2.7.6-20.el6_7.1.i686.rpm 46fa4d9f942837bb4dc48907578ed4e12ca6a830b61719c649ff2b7ac5292bbf libxml2-devel-2.7.6-20.el6_7.1.x86_64.rpm 248032ec39a9aa0964763fa824604bc696dc54b59adaaac6b9e7c54f76137518 libxml2-python-2.7.6-20.el6_7.1.x86_64.rpm 67315973b872c5fdfc8656df43af9d21bd9a881e4c20d1bff3f53db1def4022b libxml2-static-2.7.6-20.el6_7.1.x86_64.rpm Source: 647b02b23b0fc8a0cb8d0821279cb4600f130b3776e345e91dee342f8dfbbbb4 libxml2-2.7.6-20.el6_7.1.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 2 ***********************************************

1 0

7.2 kernel panic on boot
by Duncan Brown 07 Dec '15

07 Dec '15

Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? thanks Duncan

23 91

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