Discuss

discuss@lists.centos.org

34753 discussions

CentOS 7 selinux policy bug
by m.roth＠5-cent.us 29 May '15

29 May '15

Hi, folks, CentOS 7.1. Selinux policy, and targetted, updated two days ago. May 28 17:02:41 <servername> python: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/bash.#012#012***** <...> May 28 17:02:45 <servername> python: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/uname.#012#012***** <...> May 28 17:02:45 <servername> python: SELinux is preventing /usr/bin/uname from execute_no_trans access on the file /usr/bin/uname.#012#012***** <...> May 28 17:02:47 <servername> python: SELinux is preventing /usr/bin/bash from execute access on the file /usr/bin/mailx.#012#012***** <...> I did do an ll =Z /usr/bin, and everything looks correct (system_u:object_r:bin_t:s0). Given that, looks to me like a policy bug. No? Yes? File a bug report? mark

3 3

Booting back into CentOS-6
by Timothy Murphy 29 May '15

29 May '15

I'm currently running CentOS-7, but I'd like to re-boot into CentOS-6.5 which I have on another partition. Although this OS is in the grub list when I boot, if I try to run it I get a segfault. I guess this is something to do with the change from grub to grub2? In any case, I'm wondering if there is any simple way of booting into both CentOS-6 and CentOS-7? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

2 1

Re: [CentOS] Booting back into CentOS-6
by philburt stortsky 29 May '15

29 May '15

This, IMHO, is one of the more annoying bugs with the newer GRUB (which i assume is the bootloader you are using). Specifically the newer grub can't, won't boot from a drive other than the one grub is on. suggest you revert to grub 0.97 or, if any boot loader is or can be put on the drive with the 6.5 distro you can make that drive the boot drive in the bios, which is how i do it. i.e. i just put grub on any drive i might want to boot from and install etc. with the drive i want to be able to boot to set as the boot drive in the bios. of course, depending on how you are mounting drives this may break links etc. since the bios will have different names for the drives due to the different order of the boot media list in the bios. hope that helps, it is highly annoying. "We kill when we close our eyes to poverty, affliction or infamy. We kill when, because it is easier, we countenance or pretend to approve of atrophied social, political, educational and religious institutions instead of resolutely combating them." - Hesse > Message: 13 > Date: Fri, 29 May 2015 02:23:44 +0100 > From: Timothy Murphy <gayleard(a)eircom.net> > To: centos(a)centos.org > Subject: [CentOS] Booting back into CentOS-6 > Message-ID: <mk8f30$lf1$1(a)ger.gmane.org> > Content-Type: text/plain; charset="ISO-8859-1" > > I'm currently running CentOS-7, > but I'd like to re-boot into CentOS-6.5 > which I have on another partition. > Although this OS is in the grub list when I boot, > if I try to run it I get a segfault. > I guess this is something to do with the change from grub to grub2? > > In any case, I'm wondering if there is any simple way > of booting into both CentOS-6 and CentOS-7? > > -- > Timothy Murphy > gayleard /at/ eircom.net > School of Mathematics, Trinity College, Dublin > > > > > ------------------------------ > > Message: 14 > Date: Fri, 29 May 2015 02:52:53 +0100 > From: Timothy Murphy <gayleard(a)eircom.net> > To: centos(a)centos.org > Subject: [CentOS] Using Mariadb databases from old server > Message-ID: <mk8gpm$ea1$1(a)ger.gmane.org> > Content-Type: text/plain; charset="ISO-8859-1" > > I'm running CentOS-7, but I left some MySQL databases > on my old CentOS-6.5 partition which I'd like to retrieve. > I assume they are contained in the file /var/lib/mysql/ibdata1 ? > > Could I just copy this file to /var/lib/mysql in CentOS-7? > Or is there some way Mariadb or phpMyAdmin can import mysql databases > from a server that is no longer running? > > -- > Timothy Murphy > gayleard /at/ eircom.net > School of Mathematics, Trinity College, Dublin > > > > > ------------------------------ > > Message: 15 > Date: Thu, 28 May 2015 19:55:41 -0700 > From: Gordon Messmer <gordon.messmer(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] New controller card issues > Message-ID: <5567D52D.5060108(a)gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 05/28/2015 03:02 PM, Valeri Galtsev wrote: > > > > If I get you correctly you are saying that 3ware RAID cards are prone to > > hardware failures - as opposed to software RAID which is not (as it does > > not include hardware, so never has a hardware failures), right? No this is > > a joke of course. But it's the one one asked for ;-) > > Software RAID uses whatever controller the disks are connected to. > Often, that's the AHCI controller on the motherboard. And those > controllers are almost always more reliable than 3ware. Seriously. No > joke. > > > Again, I don't know your statistics: i.e. how many did you use, > > Hundreds of systems, both with 3ware and with software RAID. > > > how many > > of them died (failed as hardware). > > Not many, but some. A handful of data corruption cases (maybe 5? I > don't have logs). One BBU failure that resulted in a system that > wouldn't boot until it was removed (and a couple of hours down time > while 3ware techs worked that ticket). A couple of times when we really > wanted to move an array of disks and couldn't. > > Vs zero reliability issues with software RAID. > > > How well surge-free the power is. > > We always used trusted UPS hardware. > > > How > > well the guys who installed your cards into your boxes followed static > > discharge precautions > > Our systems were built by a professional VAR. Employees always wore > ground straps. There were other anti-static measures in place as well. > I had been to the facility. > > And I'll throw you a curveball: > > I've argued that software RAID is more reliable than 3ware cards, > specifically. In the world of ZFS and btrfs, you absolutely should not > use hardware RAID. As you mentioned earlier, hardware RAID volumes > should scan disks regularly. However, scanning only tells you if disks > have bad sectors. It can also detect data (parity) errors, but it can't > repair them. Hardware RAID cards don't have information that can tell > them which sectors are correct. ZFS and btrfs, on the other hand, > checksum their data and metadata. They can tell which sectors are > damaged in the case of corruption such as bit flips, and which sector > should be used to repair the data. > > Now, btrfs and ZFS are completely different from software RAID. I'm not > comparing the two. But hardware RAID simply has too many deficiencies > to justify its continued use. It should go away. > > > ------------------------------ > > Message: 16 > Date: Thu, 28 May 2015 21:22:45 -0700 > From: Keith Keller <kkeller(a)wombat.san-francisco.ca.us> > To: centos(a)centos.org > Subject: Re: [CentOS] New controller card issues > Message-ID: <l56l3cxekb.ln2(a)goaway.wombat.san-francisco.ca.us> > Content-Type: text/plain; charset=us-ascii > > On 2015-05-28, Valeri Galtsev <galtsev(a)kicp.uchicago.edu> wrote: > > > > I do use both LSI and 3ware. > > Both are now owned by Avago. (Not sure when that happened, last I > looked LSI was its own company.) > > > For me big advantage of 3ware is transparent > > interface. By which I mean web interface. There is command line interface > > for both and 3ware command line interface may be less confusing for me. > > I find the 3ware CLI a little clunky but easy to understand. I find the > LSI CLIs (both MegaCLI and storcli) incredibly confusing, and the GUI > interface is not intuitive (and I think doesn't expose all the > information about the controller; the Nagios LSI plugin found errors > that I could find no trace of in the GUI). > > > Sorry for long comment. I did feel 3ware deserves more respect than one > > might draw from this thread otherwise. > > Agreed; I'll share some of my experiences in another post. > > --keith > > -- > kkeller(a)wombat.san-francisco.ca.us > > > > > ------------------------------ > > Message: 17 > Date: Thu, 28 May 2015 21:36:31 -0700 > From: Keith Keller <kkeller(a)wombat.san-francisco.ca.us> > To: centos(a)centos.org > Subject: Re: [CentOS] New controller card issues > Message-ID: <fv6l3cx8ub.ln2(a)goaway.wombat.san-francisco.ca.us> > Content-Type: text/plain; charset=us-ascii > > On 2015-05-28, Valeri Galtsev <galtsev(a)kicp.uchicago.edu> wrote: > > > > Now, seriously: of more than a couple of dozens of cards I used during > > last about 13 years not a single one died on me. > > I have had a couple dozen hardware RAID controllers over the years. I > have not had the success you've had, but I've had very few hard > failures. I have had one data loss event, where a bad BBU was causing > problems with an old controller (of course I had backups, as should > everyone). I've had two other controllers just die, but replacing it > was easy, and the new controller recognized the arrays immediately. > This includes moving two different disk arrays from two different 9650s > to two different 9750s, so whoever wrote that arrays are not compatible > across different models is at least partly incorrect. > > I do also have an LSI controller, which has been fine, but it's only one > controller so it's not enough data points to draw any conclusions. I also > have an md RAID array (on a very old 3ware controller which doesn't > support RAID6), and it's also been fine. It hasn't suffered through any > major catastrophes, though I do think it's had one or two fatal kernel > panics, and once or twice had a hard reset done. It's still fine even > with a small number of really crappy "green" drives still in the array > (I learned that lesson the hard way--don't use green drives with a hardware > RAID controller!). > > --keith > > -- > kkeller(a)wombat.san-francisco.ca.us > > > > > ------------------------------ > > Message: 18 > Date: Fri, 29 May 2015 08:32:47 +0300 > From: Todor Petkov <zakk(a)online.bg> > To: CentOS mailing list <centos(a)centos.org> > Cc: Timothy Murphy <gayleard(a)eircom.net> > Subject: Re: [CentOS] Using Mariadb databases from old server > Message-ID: <62128b8c308448402a65c2b760d4d88c(a)online.bg> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On 29/05/2015 04:52 AM, Timothy Murphy wrote: > > I'm running CentOS-7, but I left some MySQL databases > > on my old CentOS-6.5 partition which I'd like to retrieve. > > I assume they are contained in the file /var/lib/mysql/ibdata1 ? > > > > Could I just copy this file to /var/lib/mysql in CentOS-7? > > Or is there some way Mariadb or phpMyAdmin can import mysql databases > > from a server that is no longer running? > > The C6 partition is part of the new server, so you are able to mount it > and copy files from it, is this correct? Have you done something with > the MariaDB or it's still clean installation? > > > > ------------------------------ > > Message: 19 > Date: Fri, 29 May 2015 09:45:24 +0200 > From: G?tz Reinicke - IT Koordinator <goetz.reinicke(a)filmakademie.de> > To: CentOS <centos(a)centos.org> > Subject: [CentOS] NSS Tools certutil buggy ? Centos 6 nss-tools-3.18.0 > Message-ID: <55681914.1040504(a)filmakademie.de> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I try to add a certificate to a fresh certificate db, but the trust > attributes are not set as expected. Neither can I change tham. > > The cert/pem is valid and double checked :) > > > Any idea/suggestion? > > > certutil -N -d certdb-test > > certutil -A -n "foobar" -t "u,u,u" -d certdb-test/ -i foobar.pem > > certutil -L -d certdb-test/ > > > Certificate Nickname Trust Attributes > SSL,S/MIME,JAR/XPI > foobar ,, > > > > certutil -M -n "foobar" -t "u,u,u" -d /tmp/certdb-test/ > > > certutil -L -d certdb-test/ > > Certificate Nickname Trust Attributes > SSL,S/MIME,JAR/XPI > foobar ,, > > > > > > Thanks and regards . G?tz > > -- > G?tz Reinicke > IT-Koordinator > > Tel. +49 7141 969 82 420 > E-Mail goetz.reinicke(a)filmakademie.de > > Filmakademie Baden-W?rttemberg GmbH > Akademiehof 10 > 71638 Ludwigsburg > www.filmakademie.de > > Eintragung Amtsgericht Stuttgart HRB 205016 > > Vorsitzender des Aufsichtsrats: J?rgen Walter MdL > Staatssekret?r im Ministerium f?r Wissenschaft, > Forschung und Kunst Baden-W?rttemberg > > Gesch?ftsf?hrer: Prof. Thomas Schadt > > > ------------------------------ > > Message: 20 > Date: Fri, 29 May 2015 12:00:07 +0100 > From: Timothy Murphy <gayleard(a)eircom.net> > To: centos(a)centos.org > Subject: Re: [CentOS] Using Mariadb databases from old server > Message-ID: <mk9gro$pq3$1(a)ger.gmane.org> > Content-Type: text/plain; charset="ISO-8859-1" > > Todor Petkov wrote: > > >> I'm running CentOS-7, but I left some MySQL databases > >> on my old CentOS-6.5 partition which I'd like to retrieve. > >> I assume they are contained in the file /var/lib/mysql/ibdata1 ? > >> > >> Could I just copy this file to /var/lib/mysql in CentOS-7? > >> Or is there some way Mariadb or phpMyAdmin can import mysql databases > >> from a server that is no longer running? > > > > The C6 partition is part of the new server, so you are able to mount it > > and copy files from it, is this correct? Have you done something with > > the MariaDB or it's still clean installation? > > I did add something to Mariadb on the new CentOS-7 system, > but I don't mind deleting it and starting again. > I can mount the partition with the old mysql files on it. > Could I just copy the contents of /mnt/var/lib/mysql > to the new system? > There are files with the same name, eg ibdata1, on both systems. > Could I have an ibdata2 ? > > Any suggestions gratefully received. > > -- > Timothy Murphy > gayleard /at/ eircom.net > School of Mathematics, Trinity College, Dublin > > > > > ------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > > > End of CentOS Digest, Vol 124, Issue 29 > *************************************** >

1 0

NSS Tools certutil buggy ? Centos 6 nss-tools-3.18.0
by Götz Reinicke - IT Koordinator 29 May '15

29 May '15

Hi, I try to add a certificate to a fresh certificate db, but the trust attributes are not set as expected. Neither can I change tham. The cert/pem is valid and double checked :) Any idea/suggestion? certutil -N -d certdb-test certutil -A -n "foobar" -t "u,u,u" -d certdb-test/ -i foobar.pem certutil -L -d certdb-test/ Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI foobar ,, certutil -M -n "foobar" -t "u,u,u" -d /tmp/certdb-test/ certutil -L -d certdb-test/ Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI foobar ,, Thanks and regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

1 0

New controller card issues
by m.roth＠5-cent.us 29 May '15

29 May '15

Running CentOS 5 (long story, will be updated some day). A 5 yr old Dell PE R415. Whoever spec'd the order, they got the cheapest, embedded controller. Push came to shove - these things gag on a drive > 2TB. So, we bought some PERC H200's for it, and its two mates. This morning, I brought the system down, and put in the card, and moved the SATA cables. This did not end well. The new card seemed to see the drives, it loaded the initrd... and kernel panic'd every time when it went to switch root. I went into the card's firmware and set the first drive to boot. No change. Upshot was that I actually had to pull the card - once it was in, and set, it insisted that it was 0 in boot order, and would not let me take it out, even though I'd reconnected the SATA connector to the on-board one. So: my manager and I are suspecting that the initrd simply doesn't have the driver for the card. I'm going to rebuild the initrd (once I figure out how to do that without the card in the box). The reason I'm posting is to ask y'all if anyone out there has some *other* thoughts as to what the problem might be, other than the initrd. Thanks in advance. mark

6 14

Openssl C6 distro tag different from upstream
by Leonard den Ottolander 28 May '15

28 May '15

Hi, Just noticed that the distro tag used in openssl is different from upstream. Upstream and the last update (openssl-1.0.1e-30.el6_6.7) use "el6_6" where as the latest update (openssl-1.0.1e-30.el6.8) uses "el_6". Any reason for this discrepancy? Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

3 3

CentOS-announce Digest, Vol 123, Issue 10
by centos-announce-request＠centos.org 28 May '15

28 May '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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. CEEA-2015:1029 CentOS 6 tg3 Enhancement Update (Johnny Hughes) 2. CEBA-2015:1032 CentOS 5 pam BugFix Update (Johnny Hughes) 3. CentOS-7 beta candidate for AArch64 platforms (Jim Perrin) 4. CEBA-2015:1033 CentOS 6 glibc BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 May 2015 12:37:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2015:1029 CentOS 6 tg3 Enhancement Update Message-ID: <20150527123717.GA61453(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2015:1029 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-1029.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5dff711b2e373e9659765e628fc5ba969313021fc81608078af40dad90442a5f kmod-tg3-3.137-2.el6_6.i686.rpm x86_64: 3dc5c70e00006a0188efa931a453a0a8d6eaba50032abf7f3cfec428842099bd kmod-tg3-3.137-2.el6_6.x86_64.rpm Source: 532e79131f1bef630ec4607b1d05b6c21d8addc979eea37eca318de4786cf416 tg3-3.137-2.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 27 May 2015 14:35:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:1032 CentOS 5 pam BugFix Update Message-ID: <20150527143501.GA26646(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:1032 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1032.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: abdd6996f2976fec625db70ade1ae4693196f67105b688feaad382d3ac17ae60 pam-0.99.6.2-14.el5_11.i386.rpm 784578b99de9d56f32a49325896d046321feafdcc9fd0d7c417ecfbdca3cfafd pam-devel-0.99.6.2-14.el5_11.i386.rpm x86_64: abdd6996f2976fec625db70ade1ae4693196f67105b688feaad382d3ac17ae60 pam-0.99.6.2-14.el5_11.i386.rpm 5e2d0e23ae1e63ac116ae0b96f3d8b523d9f035dcae03b0a5670374842e2579d pam-0.99.6.2-14.el5_11.x86_64.rpm 784578b99de9d56f32a49325896d046321feafdcc9fd0d7c417ecfbdca3cfafd pam-devel-0.99.6.2-14.el5_11.i386.rpm 22d657e3ee8612afc3d75582e1717013582cd03690258f58303fabfb459c28aa pam-devel-0.99.6.2-14.el5_11.x86_64.rpm Source: 1d0d664b4815216f0df166264bf5d5adb15bffcbb8d7cd207e63af168a5c3edb pam-0.99.6.2-14.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 27 May 2015 11:20:19 -0500 From: Jim Perrin <jperrin(a)centos.org> To: centos-announce(a)centos.org, arm-dev(a)centos.org Subject: [CentOS-announce] CentOS-7 beta candidate for AArch64 platforms Message-ID: <5565EEC3.7010905(a)centos.org> Content-Type: text/plain; charset=utf-8 We are pleased to announce the public beta release of CentOS Linux 7 for AArch64 compatible hardware. We've addressed a number of issues discovered from the previous 2 weeks of alpha testing, and feel that the release is stable enough to transition to beta. Improvements from Alpha ======================= Improved package selection: A number of additional packages have been added, including libreoffice, evolution, abrt, and more. Updated kernel: Some non-fatal kernel errors have been address by moving to a 4.1rc based kernel version. This also adds ACPI functionality to the platform. Improved Group selection: The installer now offers a larger group selection from the previous minimal-only install. Installation ============ Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Download ======== The full (unsigned) install tree is available at http://buildlogs.centos.org/centos/7/os/aarch64/ ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch) and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a loose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ------------------------------ Message: 4 Date: Wed, 27 May 2015 15:14:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:1033 CentOS 6 glibc BugFix Update Message-ID: <20150527151406.GA14300(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:1033 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1033.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a193dd5a810304800b3c6c8c6ebe9cf7c812405c2c90c91a8d5e2f55c2808259 glibc-2.12-1.149.el6_6.9.i686.rpm a49df2dc9eb6106ed952593c72b1454e26eca771c68c659b426f458c3efb7a7b glibc-common-2.12-1.149.el6_6.9.i686.rpm f7c136221d3f6fb8d4c25ba4c1e4e49f052529608b350e29e5b2863275f29b33 glibc-devel-2.12-1.149.el6_6.9.i686.rpm afca31eff6e38e5a7b95e8737be5baff927d5b70b20bd93751148befa2745b02 glibc-headers-2.12-1.149.el6_6.9.i686.rpm 8ff405369f9bbc106364df0b169337c677fedcc1a501b8a92c86c9b9fb21fb14 glibc-static-2.12-1.149.el6_6.9.i686.rpm 70ddf8e976e4a4721ccfced10c5d1e07858afcb04b2fb00198c7641135daa295 glibc-utils-2.12-1.149.el6_6.9.i686.rpm 1c395ae1da4e73c7d60dc3ff4b372ea6d881d8102a15bb76f127a4ffea367cf2 nscd-2.12-1.149.el6_6.9.i686.rpm x86_64: a193dd5a810304800b3c6c8c6ebe9cf7c812405c2c90c91a8d5e2f55c2808259 glibc-2.12-1.149.el6_6.9.i686.rpm 712f9c468fa39edcb974433852db80d5cb6ce6cacb6d24f2050c04de62c834e3 glibc-2.12-1.149.el6_6.9.x86_64.rpm 62c09f50b6bb09105f34733e0ddf68f7313925c08b736e364fb4f9ee3ff6e137 glibc-common-2.12-1.149.el6_6.9.x86_64.rpm f7c136221d3f6fb8d4c25ba4c1e4e49f052529608b350e29e5b2863275f29b33 glibc-devel-2.12-1.149.el6_6.9.i686.rpm 3705c8079805449b4a01aa97aa6a7d8f467fedbf2ac88e5e9c3d58ebf15fc23e glibc-devel-2.12-1.149.el6_6.9.x86_64.rpm 9910a446ca5782bf4c8745abe63357ab368b6d36d8723a4ce978fec49064262d glibc-headers-2.12-1.149.el6_6.9.x86_64.rpm 8ff405369f9bbc106364df0b169337c677fedcc1a501b8a92c86c9b9fb21fb14 glibc-static-2.12-1.149.el6_6.9.i686.rpm ef0c6146fc033accef8e61c4821114d264db034643a254e2d2676b89f80f2cbf glibc-static-2.12-1.149.el6_6.9.x86_64.rpm 097fea253a97bdfc5bbf1114986cedfd24cc1bd3548c206b3986ee96175fad26 glibc-utils-2.12-1.149.el6_6.9.x86_64.rpm 74af55bb1cca30aa6e682230be1db3f6478cf8d0eff46b89e14ab93bdd4edd9a nscd-2.12-1.149.el6_6.9.x86_64.rpm Source: 707d103e880ad41fb7996eaa7f74575c942601b85cbbbec47363384619e1e869 glibc-2.12-1.149.el6_6.9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 123, Issue 10 ************************************************

1 0

What does "4m[terminated]" mean?
by Nan Xiao 28 May '15

28 May '15

Hi all, After installing CentOS 7 and restart it, it always promptd "4m[terminated]". What does this prompt mean? Does it will affect normal OS functions? Thanks in advance! Best Regards Nan Xiao

1 0

dummy interface shenanigans - CentOS6
by Frank Even 27 May '15

27 May '15

tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. I have a situation where I need to rename a dummy interface on my system. I have a total of 3 dummy interfaces: dummy0 dummy1 adummy0 I've been doing some puppet testing in a vbox VM to get this all sorted out to deploy to a group of boxes. Every time I reboot my VM, it comes up WITHOUT adummy0, but I notice there is now an unconfigured dummy2. I've tried everything from adding aliases to /etc/modprobe.d/dummyopts.conf to renaming the interface via "ip" (ip link set dummy2 name adummy0). This is all fine during use, even during a network restart. But as soon as I restart the VM, it comes back up broken. I for the life of me have been unable to figure out why. I could use some help in narrowing down why this won't persist across reboots. I can write a startup script to deal with it, but it doesn't seem like a good solution. Thanks, Frank

2 3

Command line mp3 player
by Bowie Bailey 27 May '15

27 May '15

I have a CentOS 7 server that I want to use as an audio source for our hold music. It does not have a GUI installed, so I am looking for a program with a command line interface that will let me play a folder full of mp3 files on a continuous loop. MOC seems to do what I want, but I can't find a build for CentOS 7. Is there another program that I can use for this? Thanks. -- Bowie

7 10

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss