Discuss

discuss@lists.centos.org

34758 discussions

Centos for Interested Children
by Always Learning 03 Apr '14

03 Apr '14

Today, an enthusiastic 10 year old boy asked me about Linux. I thought of telling me to go to centos.org but then realised there is nothing on centos.org for complete beginners to Linux or for children. If anyone has the time, energy and interest, perhaps a basic technical introduction to the Centos version of Linux would be a good long-term objective. Let's catch the children's interest, imagination and enthusiasm before they become immersed and entrapped in a Micro$oft-only world. Centos is for everyone including granddads and children. Centos is the future of first-class reliable Open Source Software. -- Paul. England, EU. Our systems are exclusively Centos. No Micro$oft Windoze here.

6 6

Chromium 31.0.1650.63-2.el6 for CentOS 6
by Johnny Hughes 03 Apr '14

03 Apr '14

All, As has already been brought up, we have not yet been able to build the new version of Chromium-32 for CentOS, and the current version (31.0.1650.63-1.el6) needs updating. We have also recently been informed that we may not redistribute the PepperFlash Library from the Google site (libpepflashplayer.so) as we did in 31.0.1650.63-1.el6. Therefore, I have had to rebuild the currently released version to remove the libpepflashplayer.so library. What this means for all Chromium users is that after upgrade, you will no longer have built in flash. I apologize for the inconvenience, but we have no real choice in the matter. While the CentOS team can not redistribute that library, end users can still get it ... here is how: 1. Become root and create a temporary working directory to download the package .. I recommend /tmp/working/ mkdir /tmp/working/ cd /tmp/working/ 2. Get the latest google chrome rpm from google for your arch (either x86_64 or i386): wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm (or if needing the 32bit version, substitute i386 for x86_64 in the above path) 3. Extract the RPM using this command: rpm2cpio google-chrome-stable_current_x86_64.rpm | cpio -idv (again, substitute i386 for x86_64 if required) 4. Create the PepperFlash directory where the library will live: mkdir /opt/chromium-browser/PepperFlash/ 5. Copy the chome PepperFlash library and json file to the new directory: cp opt/google/chrome/PepperFlash/* /opt/chromium-browser/PepperFlash/ 6. Restart chromium and test that flash works. Thanks, Johnny Hughes

9 17

kwallet?
by m.roth＠5-cent.us 03 Apr '14

03 Apr '14

So, the other admin I work with comes by, and we're both using kde, and he asks me to to go the start menu, and fire up kwalletmanager. I do... and nothing happens. ps tells me it's running, but there is no window. What's supposed to happen? This is 6.5 mark "don't use it, anyway, but...."

1 0

ruby193 SCL and mod_passenger
by Filip Bartmann 03 Apr '14

03 Apr '14

I'm interested in ruby and I try the ruby193 SCL and I want to run Ruby on Rails with Apache, so I'm searching mod_passenger for this ruby SCL version, but I found, that this package is not in this SCL. Are any other possibilities to run Ruby on Rails with Apache or why is mod_passenger not in this SCL? Thanks, Filip Bartmann

3 2

Re: [CentOS] ruby193 SCL and mod_passenger
by James B. Byrne 03 Apr '14

03 Apr '14

On Thu, April 3, 2014 03:38, Filip Bartmann wrote: > Â > I'm interested in ruby and I try the ruby193 SCL and I want to run Ruby on > Rails with Apache, so I'm searching mod_passenger for this ruby SCL version, > but I found, that this package is not in this SCL. Are any other possibilities > to run Ruby on Rails with Apache or why is mod_passenger not in this SCL? > Â > Thanks, > Filip Bartmann > > When last I looked (~6-9 months ago) mod_passenger had to be built via the Rubygem install process. It also had issues with respect to SELinux that as far as I know remain unresolved. I know that Dan Walsh was working hard with the Phusion team to deal with this but it seemed to me at that time that both sides were considerably distant from an agreement with Phusion at one point basically telling RedHat to fork their project and call it something else. Whether or not this is the reason that the Software Collection does not have an rpm for mod_passenger I cannot say. However, given that support for 1.9.3 ends next January and that Ruby is already at 2.1.1 I suggest that perhaps you are better off building your own Ruby from source and packaging it as a custom rpm. I provided a working spec file and somewhat detailed instructions for building Ruby-1.9.3 at http://byrnejb.wordpress.com/2013/01/30/building-ruby-1-9-3-for-centos-6-3/. You can trivially modify this for 2.1.0 (skip 2.1.1 which has a problem with objects inheriting from Hash - a big problem if you are employing Rails) to build your own package and then use Rubygems to install mod-passenger. You can also package mod_passenger as an rpm should you desire. I do not bother with repackaging gems, although perhaps I should so as to avoid loading development packages on production servers. Alternatively, you can use a Ruby version manager instead of using the system Ruby. On the use of rbenv or rvm I have mixed feelings. Both ruby version managers offer a valuable work-around for environments where system admin is not under the direction of the development team. For production deployments I found that there were other issues which made selection of rvm or rbenv problematic, notably in the deploy process itself and in the brittleness that resulted. I concluded after several incidents involving rvm deploys (not the fault of rvm by the way) that a package managed system really needs to remain a package managed system for ease and efficiency in maintenance. Of course, if you are deploying to a shared hosting arrangement where the production environment is not under your control then rvm or something much like it is unavoidable. But in that case you are only responsible for maintaining your own small part of the system and so your maintenance requirements are far more circumscribed. -- *** E-Mail is NOT a SECURE channel *** 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

1 0

Re: [CentOS] Removing a file that starts with dashes
by James B. Byrne 03 Apr '14

03 Apr '14

On Wed, April 2, 2014 20:56, John R. Dennison wrote: > On Wed, Apr 02, 2014 at 03:59:26PM -0700, benfell(a)parts-unknown.org wrote: >> On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote: >> > >> > WTF - there is a reason the "-f" flag exists - RTFM >> > > > Please ignore and do not respond to this person; he's not a member of > the list and is using nefarious methods to post to it. > Background: https://lists.fedoraproject.org/pipermail/advisory-board/2013-May/011982.ht… -- *** E-Mail is NOT a SECURE channel *** 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

1 0

CentOS-announce Digest, Vol 110, Issue 2
by centos-announce-request＠centos.org 03 Apr '14

03 Apr '14

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. CESA-2014:0348 Important CentOS 5 xalan-j2 Update (Johnny Hughes) 2. CESA-2014:0348 Important CentOS 6 xalan-j2 Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Apr 2014 12:17:13 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0348 Important CentOS 5 xalan-j2 Update To: centos-announce(a)centos.org Message-ID: <20140402121713.GA31311(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0a93cd521aa9197ef5e08abbc130eddae7b0d7d7bdc8de2e3e417e0ceb72789b xalan-j2-2.7.0-6jpp.2.i386.rpm 99f6ad2ccf7ca1ff180360510279a1a274c3af0bbe8f46f51d453f1b5636bfff xalan-j2-demo-2.7.0-6jpp.2.i386.rpm e1abce5dcc6bb72fca6c482e48fd7aa8ddfaacec946ce538ead8044057621003 xalan-j2-javadoc-2.7.0-6jpp.2.i386.rpm d6d235e7331ed50701061db86eb5636435f791d951fd2ca0f5da40ab19fc114b xalan-j2-manual-2.7.0-6jpp.2.i386.rpm 25b19b09a04c414ca19de5ae8776779dff35b2d7f07ea14845c58d1ebf74d12a xalan-j2-xsltc-2.7.0-6jpp.2.i386.rpm x86_64: 20b4cb7dffa6c9e487f000ed856ea236519123c31d37b272cfc5b4a549c03ca0 xalan-j2-2.7.0-6jpp.2.x86_64.rpm 060bb167461297e137975dfa5ce53025320650068ad83ccb7feed626fde9020b xalan-j2-demo-2.7.0-6jpp.2.x86_64.rpm a2e6b04ad6432bfcc87d771ae0c1c07ac8e762babbbb65ab39a81ad2f6a60f57 xalan-j2-javadoc-2.7.0-6jpp.2.x86_64.rpm debebcbc1a2e58d4ce02ffed019716455c5aeb70df0acb60dcd3e4b258394c80 xalan-j2-manual-2.7.0-6jpp.2.x86_64.rpm 7e3c0e52f39a41745c5ef5c9b18f18f2f250badb9b3931db862a43270980f38b xalan-j2-xsltc-2.7.0-6jpp.2.x86_64.rpm Source: 3c7587838c8f200c574eef290aef47c9b95e1d86e4a2eb2030d5ddd056cf0338 xalan-j2-2.7.0-6jpp.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 2 Apr 2014 12:22:27 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0348 Important CentOS 6 xalan-j2 Update To: centos-announce(a)centos.org Message-ID: <20140402122227.GA34356(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4791c5a062d2fafdbc3281552de6770ffcfb2e678913af78a76e8160e7398343 xalan-j2-2.7.0-9.9.el6_5.noarch.rpm 315a5642f01614a5ea9ad520bab9969169c35a5d07622f99003d97aa00c455ee xalan-j2-demo-2.7.0-9.9.el6_5.noarch.rpm 876b3aa82be8b979368b06121e038e01bbb768e91dbf65e4cbd84475b17fb94f xalan-j2-javadoc-2.7.0-9.9.el6_5.noarch.rpm 5c87ed68e12853a34ebb9cfbe4910e1ac5b42092a467fab7980e97a77753a94f xalan-j2-manual-2.7.0-9.9.el6_5.noarch.rpm 439b1a8b03fec9837f0149a3540e79482795ba3359762372fd59c3eb859bc2b8 xalan-j2-xsltc-2.7.0-9.9.el6_5.noarch.rpm x86_64: 4791c5a062d2fafdbc3281552de6770ffcfb2e678913af78a76e8160e7398343 xalan-j2-2.7.0-9.9.el6_5.noarch.rpm 315a5642f01614a5ea9ad520bab9969169c35a5d07622f99003d97aa00c455ee xalan-j2-demo-2.7.0-9.9.el6_5.noarch.rpm 876b3aa82be8b979368b06121e038e01bbb768e91dbf65e4cbd84475b17fb94f xalan-j2-javadoc-2.7.0-9.9.el6_5.noarch.rpm 5c87ed68e12853a34ebb9cfbe4910e1ac5b42092a467fab7980e97a77753a94f xalan-j2-manual-2.7.0-9.9.el6_5.noarch.rpm 439b1a8b03fec9837f0149a3540e79482795ba3359762372fd59c3eb859bc2b8 xalan-j2-xsltc-2.7.0-9.9.el6_5.noarch.rpm Source: a0c023cc26c02efc826a66cbe7e87e0c4808d456a3016a81e0dd1b24b83bf202 xalan-j2-2.7.0-9.9.el6_5.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 110, Issue 2 ***********************************************

1 0

write barrier support in CentOS 6
by Tom Robinson 03 Apr '14

03 Apr '14

Hi, I've been looking for an answer to this question and can't find anything concrete that says full support for write barriers has been backported to the stock kernel. I've read that: "There is incomplete write barrier support in kernel versions 2.6.32 and earlier (2.6.31 has some support, while 2.6.33 works for all types of device target) - RHEL 6 uses 2.6.32." Now, I understand that Red Hat (and therefore CentOS) backport many upstream features into the stock kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write barrier support? Any clues, anyone? Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

3 7

Removing a file that starts with dashes
by Frank M. Ramaekers 03 Apr '14

03 Apr '14

How can I remove this file? -rw-r--r-- 1 root root 28707 Mar 31 12:31 --backup=numbered I've tried a few different methods, but most attempts interprets the file name as a switch (which it doesn't understand). TIA, Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | American Income Life Insurance Company | 254-761-6649

9 14

Re: [CentOS] Removing a file that starts with dashes
by benfell＠parts-unknown.org 03 Apr '14

03 Apr '14

On Wed, Apr 02, 2014 at 11:17:02PM +0200, Reindl Harald wrote: > > WTF - there is a reason the "-f" flag exists - RTFM > I don't know what manual you're reading. But -f has a specific function and *this* *isn't* *it*. -- David Benfell <benfell(a)parts-unknown.org> See https://parts-unknown.org/node/2 if you don't understand the attachment.

3 6

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