Discuss

discuss@lists.centos.org

34753 discussions

sound conversion assistance
by fred smith 17 Jan '08

17 Jan '08

OK, I downloaded a batch of ".rm" audio files from the net. I can play them with mplayer or realplayer, but how can I convert them to something else, e.g. mp3, etc.? So far haven't unearthed any tools that can both read them and write out in another format. Thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "For him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy--to the only God our Savior be glory, majesty, power and authority, through Jesus Christ our Lord, before all ages, now and forevermore! Amen." ----------------------------- Jude 1:24,25 (niv) -----------------------------

2 1

Capturing Packets -- Ethereal
by Al Sparks 17 Jan '08

17 Jan '08

This may be off topic, but I think my ethereal question might be simple enough. I am presently compiling ethereal on a CentOS platform to check it out. But the packets I want to monitor are actually on a different CentOS platform, and I'd rather not install Ethereal on it, if for no other reason I don't have X-Windows installed on that platform. My question is, can I monitor/write packets to a file on the more remote machine, and then analyze the packets on another machine using my ethereal SW? Can I sniff the packets on the remote w/o a full install of ethereal? === Al

5 4

screen locking - pam and xscreensaver
by Scott Ehrlich 16 Jan '08

16 Jan '08

For an out-of-box Centos install that utilizes PAM for xscreensaver within both gnome and kde, what factors would lead to xscreensaver not being able to properly unlock the user? I reviewed the logs and nothing helped. I performed ldd on xscreensaver and an ls -l on each dependency proved they were all there. The system uses local /etc/passwd and /etc/shadow files for authentication - no NIS or LDAP or Kerberos. If Xwindows was to be disabled, and only tty was used, what would be the best option for ensuring the logged-in session was locked after a determined amount of inactivity> Also, if the user stepped away from the system and wanted to manually lock it, what is the best tty screen-locking utility? I reviewed vlock, but after prompting me for my password, it then prompted for root's. That was less than helpful. Thanks. Scott

2 2

location of sg.c on distro CDs
by Ray Leventhal 16 Jan '08

16 Jan '08

Hi all, I find I'm in need of sg.c and can't seem to locate the rpm for the generic scsi driver on my CentOS5 CD's. Might someone point me in the right place, please? Thanks in advance, ~Ray

4 7

Re: [CentOS] OT: Dell BIOS and mixed drives
by David G. Miller 16 Jan '08

16 Jan '08

"Jerry S." <bugzjer(a)aol.com> top posted his reply: > In the BIOS you should also be able to specify the boot drive as well. > > jer > > Barry Schiffman wrote: > >> > I have a Dell Precision 360, which has both onboard >> > SATA and ultra ATA controllers, and I put one of each >> > kind of drive into the bays to make an experimental >> > machine with the xen kernel. >> > >> > After enabling both of drives, the BIOS recognizes >> > each drive, but it fails to boot, giving me the >> > message "secondary drive 1 not found". The BIOS gives >> > me a choice of going ahead or going to setup. Choosing >> > 'continue anyway' has no effect. >> > >> > I can circumvent this going to F12 to manually choose >> > to boot from the 'Primary Master' (rather than the >> > SATA primary, or the CD, or Hard Disk Drive C:). I >> > still get the warning about secondary drive 1 not >> > found, but now I can choose to go ahead. At this >> > point, grub takes over and everything is fine, boots >> > fine, both drives show up. >> > >> > In fact, I installed CentOS from the DVD, and during >> > installation there was no hint of a problem with using >> > the two drives. >> > >> > In the BIOS setup, I do not get all the drives to >> > choose from -- just Hard Disk Drive C: and the CD. >> > >> > Can anyone suggest a way around this? Depending on the BIOS options, you may be able to set the SATA to "no auto-detect" and "no drive". The kernel should still probe the SATA channel and give you access to the drive once the system is up. This is highly BIOS dependent but I've seen it work as described when the BIOS supports it. It's kind of strange that the BIOS is complaining about "secondary drive 1 not found". Sounds like a BIOS bug. Is there a BIOS update available? Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

3 2

FreeNX issues
by jake l. eaker 16 Jan '08

16 Jan '08

I have just installed freenx on two seperate centos 5.0 boxes. I had freenx server working before performing a "yum update" (which upgraded centos to 5.1). I then rebooted the box and now the display starts to show on the client, but then terminates the connection for no reason (at least nothing in any server logs). Below is the session info on the client machine. NXPROXY - Version 3.0.0 Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '14861'. Session: Starting session at 'Wed Jan 16 05:02:52 2008'. Info: Connection with remote proxy completed. Warning: Unrecognized session type 'unix-gnome'. Assuming agent session. Info: Using WAN link parameters 768/24/1/0. Info: Using cache parameters 4/4096KB/16384KB/16384KB. Info: Using pack method 'adaptive-9' with session 'unix-gnome'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 1/1. Info: Using cache file '/home/jake/.nx/cache-unix-gnome/S-4275B4AC746DA0CDBBFE7A84DDC3791F'. Info: Forwarding X11 connections to display ':0.0'. Info: Listening to font server connections on port '11000'. Session: Session started at 'Wed Jan 16 05:02:52 2008'. Info: Established X server connection. Info: Using shared memory parameters 1/4096K. Session: Terminating session at 'Wed Jan 16 05:02:53 2008'. Session: Session terminated at 'Wed Jan 16 05:02:53 2008'. PS. I get the same session info coming from separate windows and linux client boxes. Any help would be appreciated. --Jake

2 1

CentOS-announce Digest, Vol 35, Issue 8
by centos-announce-request＠centos.org 16 Jan '08

16 Jan '08

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-2008:0005 Moderate CentOS 3 i386 httpd - security update (Tru Huynh) 2. CESA-2008:0005 Moderate CentOS 3 x86_64 httpd - security update (Tru Huynh) 3. CESA-2008:0006 Moderate CentOS 4 i386 httpd - security update (Johnny Hughes) 4. CESA-2008:0006 Moderate CentOS 4 x86_64 httpd - security update (Johnny Hughes) 5. CESA-2008:0005 Moderate CentOS 3 ia64 httpd - security update (Pasi Pirhonen) 6. CESA-2008:0006 Moderate CentOS 4 ia64 httpd - security update (Pasi Pirhonen) 7. CESA-2008:0004-01: Moderate CentOS 2 i386 apache security update (John Newbigin) 8. CESA-2008:0005 Moderate CentOS 3 s390(x) httpd - security update (Pasi Pirhonen) 9. CESA-2008:0006 Moderate CentOS 4 s390(x) httpd - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Jan 2008 13:48:29 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0005 Moderate CentOS 3 i386 httpd - security update To: centos-announce(a)centos.org Message-ID: <20080115124829.GB2748(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0005 httpd security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0005.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/httpd-2.0.46-70.ent.centos.i386.rpm updates/i386/RPMS/httpd-devel-2.0.46-70.ent.centos.i386.rpm updates/i386/RPMS/mod_ssl-2.0.46-70.ent.centos.i386.rpm source: updates/SRPMS/httpd-2.0.46-70.ent.centos.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update httpd\* Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Fun with nosetuid!
by Scott Ehrlich 15 Jan '08

15 Jan '08

On an unpatched Centos 4.4 system I chmod'd /usr/bin/sudo to ug+s, and set the filesystem in /etc/fstab to defaults,nosetuid. Reboot, and am told sudo needs to be set to setuid root. An ls -l shows rwsrws-- root root sudo I had to use a rescue CD to undo /etc/fstab for the filesystem partition so sudo would work. What am I missing? Thanks. Scott

2 1

AW: [CentOS] tty login vs Gnome screen lock
by Marc Rebischke 15 Jan '08

15 Jan '08

Which Keyboard-Layout do you use ? Maybe that's the trick... Well, i use Germay Keyboard Layout, but when the Screen lock is coming up The "z" and "y" is swapped (qwertz vs. querty). Try logging in Using us-keyboard-Layout. Just my 2 cents... Regards Marc Rebischke ----- Ursprüngliche Nachricht ----- Von: Scott Ehrlich <scott(a)MIT.EDU> Gesendet: Dienstag, 15. Januar 2008 19:53 An: centos(a)centos.org Betreff: [CentOS] tty login vs Gnome screen lock I have a Centos 4.4 system (unpatched) that lets me log in via tty/console, but when the Gnone screen lock kicks in, my password is unable to unlock. I am absolutely certain I an typing the correct password. I had to Alt-F1 to log in that way, issue a sudo reboot, then logged back in, enabled the screen lock, typed my password again, and it would not unlock. What am I missing? Thanks. Scott _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

tty login vs Gnome screen lock
by Scott Ehrlich 15 Jan '08

15 Jan '08

I have a Centos 4.4 system (unpatched) that lets me log in via tty/console, but when the Gnone screen lock kicks in, my password is unable to unlock. I am absolutely certain I an typing the correct password. I had to Alt-F1 to log in that way, issue a sudo reboot, then logged back in, enabled the screen lock, typed my password again, and it would not unlock. What am I missing? Thanks. Scott

1 0

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