Re: [CentOS] CentOS 5.3: duplicate glib2-2.12.3-2.fc6 packages

2009-05-17 Thread William R. Lorenz
Hi Clint, On Mon, 18 May 2009, Clint Dilks wrote: > William R. Lorenz wrote: >> I have a freshly installed CentOS 5.3, x86_64 system -- just the Base >> package selection (via custom packages selection), and nothing else. >> Immediately after install (no updates), here's what's in the RPM db: >>

Re: [CentOS] CentOS 5.3: duplicate glib2-2.12.3-2.fc6 packages

2009-05-17 Thread Clint Dilks
William R. Lorenz wrote: > Hi All, > > I have a freshly installed CentOS 5.3, x86_64 system -- just the Base > package selection (via custom packages selection), and nothing else. > Immediately after install (no updates), here's what's in the RPM db: > >[r...@dev ~]# rpm -qa | grep -i glib2 >

[CentOS] CentOS 5.3: duplicate glib2-2.12.3-2.fc6 packages

2009-05-17 Thread William R. Lorenz
Hi All, I have a freshly installed CentOS 5.3, x86_64 system -- just the Base package selection (via custom packages selection), and nothing else. Immediately after install (no updates), here's what's in the RPM db: [r...@dev ~]# rpm -qa | grep -i glib2 glib2-2.12.3-2.fc6 glib2-2.12.3-

Re: [CentOS] When will we be moving to lighttpd 1.5?

2009-05-17 Thread Robert
Jim Perrin wrote: > On Sun, May 17, 2009 at 2:15 PM, James Matthews wrote: > >> I know I can compile it however I prefer to use the package manager and >> having an updated version. >> >> -- >> http://www.goldwatches.com >> > > Run 'rpm -qi lighttpd' to see where you got the lighttpd packa

Re: [CentOS] Kickstart hang trying to install CentOS 5.3

2009-05-17 Thread Clint Dilks
Alfred von Campe wrote: > On May 14, 2009, at 23:36, nate wrote: > > >> hmm, is your package selection particularly complex? In my case >> I list hundreds of packages in my %packages section I don't have >> groups and stuff. I assume your using a stock CentOS install >> and you didn't put any of

Re: [CentOS] When will we be moving to lighttpd 1.5?

2009-05-17 Thread Jim Perrin
On Sun, May 17, 2009 at 2:15 PM, James Matthews wrote: > I know I can compile it however I prefer to use the package manager and > having an updated version. > > -- > http://www.goldwatches.com Run 'rpm -qi lighttpd' to see where you got the lighttpd package from. Once you know where it came from

Re: [CentOS] When will we be moving to lighttpd 1.5?

2009-05-17 Thread Ralph Angenendt
James Matthews wrote: > I know I can compile it however I prefer to use the package manager and > having an updated version. "We" do not ship lighttpd. So probably never. Ralph pgpN7iHSiQhx6.pgp Description: PGP signature ___ CentOS mailing list CentOS

[CentOS] When will we be moving to lighttpd 1.5?

2009-05-17 Thread James Matthews
I know I can compile it however I prefer to use the package manager and having an updated version. -- http://www.goldwatches.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

[CentOS] X Windows has quit working

2009-05-17 Thread Thomas Dukes
Hello, Not sure when it stopped working as I don't use it often. Maybe since the upgrade from 5.2 to 5.3. Can't say for sure as it's been a while since tried to start X. The errors I receive when startin X are: (EE) I810(0): unknown reason for exception (EE) I810(0): cannot continue (EE) I810(

[CentOS] GlusterFS 2.0 Release

2009-05-17 Thread Harshavardhana
Greetings everyone, On behalf of the Gluster team I'm happy to announce that we've released GlusterFS v2.0. A milestone in terms of feature and stability has been reached, hope it helps your storage needs. :) Announcement === About GlusterFS: GlusterFS is a clustered file system that run

Re: [CentOS] no snd-hda-codec.ko in CentOS 5.3 is that ok ?

2009-05-17 Thread Colonna Francois
Le samedi 16 mai 2009 à 20:35 +0200, Equinox86 a écrit : > did you try see the permission on: > ls -l /dev/dsp crw--- 1 colonna root 14, 3 mai 17 14:24 /dev/dsp > ls -l /dev/audio crw--- 1 colonna root 14, 4 mai 17 14:24 /dev/audio > and ls -l /dev/snd/ crw--- 1 colonna root 116,

Re: [CentOS] Dealing with brute force attacks

2009-05-17 Thread James Matthews
What you can try doing is putting some services on a non standered port (like SSH on port 4583) This will stop most (not all) attacks coming in at port 22. James On Fri, May 15, 2009 at 8:21 PM, James B. Byrne wrote: > On: Thu, 14 May 2009 13:00:09 -0700, Scott Silva > wrote: > > > > http://pac