Discuss

discuss@lists.centos.org

34753 discussions

Video card
by centos＠911networks.com 24 May '07

24 May '07

Hi, I need to get a new video card, pci-x16 for CentOS5. In your opinion, which is better: ATI or NVIDIA? -- Thanks http://www.911networks.com When the network has to work

3 2

IPv6 router on CentOS
by Brijesh Shukla 24 May '07

24 May '07

CentOS-list Could any body teach me any "how to" or document to build an IPv6 (dual stack) router on CentOS. Thanks in advance Brijesh Shukla

1 0

Re: [CentOS] CentOS 4 won't boot on test machine [SOLVED]
by Mark Hull-Richter 23 May '07

23 May '07

On 5/23/07, Mark Hull-Richter <mhullrich(a)gmail.com> wrote: > > Typo - my bad. The device map contains this: > > (fd0) /dev/fd0 > (hd0) /dev/sdd > (hd1) /dev/sde > > What happened to sda-sdc (i.e., why aren't they in the device map at all)? > On a hunch, I tried hd0 and that works. I am completely baffled as to why there was another disk drive in the map, particularly sdd, since that's the bad one. I just guessed that, since the CMOS boot order only specifies one disk drive, maybe that was the "one." Strange.... -- Mark Hull-Richter DATAllegro (www.datallegro.com) 85 Enterprise, Second Floor, Aliso Viejo, CA 92656 949-680-3082 - Office 949-680-3001 - fax

1 0

CentOS 4 won't boot on test machine
by Mark Hull-Richter 23 May '07

23 May '07

I must have really shot myself in the foot on this one. I reinstalled CentOS 4.4 (have to, for now) on my test machine, exactly the way it was before (same options anyway), but when it comes up, I get: Booting 'CentOS-4 x86_64 (2.6.9-42.ELsmp)' root(hd1,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/ rhgb quiet Error 15: File not found Press any key to continue... If I press any key, I get a garbled screen that is nearly impossible to read. So, I rebooted from the DVD in rescue mode, ran fdisk to verify that the partitions are set up correctly, ran e2fsck on all three formatted partitions (sde1 - /boot, sde3 - /, sde6 - /home), ran e2label to make sure the labels are set correctly and everything checks out. All the file images are present in /boot where they should be, and the device map shows hd1 is /dev/sde3. Is my disk rotten or something? Everything is in the right place (so far) but it won't boot. The test machine is of a type I don't recognize, it's running a 2.88GHz Xeon processor with 8Gb of memory, a 4-disk RAID SATA controller (currently configured as 4 separate drives, one of which is "spared" because it did go bad) and a WD hard drive as /dev/sde. It has a 17" FP monitor with an ATI <something> XL video card, though I doubt that last part is terribly relevant. Suggestions welcome. -- Mark Hull-Richter DATAllegro (www.datallegro.com) 85 Enterprise, Second Floor, Aliso Viejo, CA 92656 949-680-3082 - Office 949-680-3001 - fax

2 2

RE: It works now -- RE: trying to run sshd daemon inkickstartenvironment
by Guolin Cheng 23 May '07

23 May '07

Steden and all, Sure, I'll find some time to document my steps in near future. Have fun. --Guolin -----Original Message----- From: kickstart-list-bounces(a)redhat.com [mailto:kickstart-list-bounces@redhat.com] On Behalf Of Steden Klaus Sent: Wednesday, May 23, 2007 2:41 PM To: Discussion list about Kickstart Cc: centos(a)centos.org Subject: RE: It works now -- RE: trying to run sshd daemon inkickstartenvironment Hmmm, this sounds like a useful addition. Could you post your steps, etc. to the Fedora Wiki? Cheers, Klaus > -----Original Message----- > From: kickstart-list-bounces(a)redhat.com [mailto:kickstart-list- > bounces(a)redhat.com] On Behalf Of Guolin Cheng > Sent: Wednesday, May 23, 2007 2:39 PM > To: Discussion list about Kickstart > Cc: centos(a)centos.org; kickstart-list(a)redhat.com > Subject: It works now -- RE: trying to run sshd daemon in > kickstartenvironment > > Hi, > > Thanks a lot for so many helpful responses. > > The fix is pretty straight: just mount /dev/pts again at the chrooted > %post environment where my original sshd fires up from. > > One command 'Mount -t devpts -o rw,gid=5,mode=620 devpts /dev/pts' or > just a bare 'mount /dev/pts' command fix the problem since the devpts > entry is in fstab already. > > I also hacked image stage2.img to include sshd daemon binary, libraries > and configuration files, and fire up the ssh daemon at the first line of > %pre script section. Then disable my original fired up sshd daemon at > %post section. > > Now kickstart environment is not 'dump' at all -- I can kick into and > monitor the kickstart clients any time and stop run-away kickstart > processes with 'reboot' command immediately should my home directory > server upgrade turn into a disaster. > > --Guolin > > > > -----Original Message----- > From: kickstart-list-bounces(a)redhat.com > [mailto:kickstart-list-bounces@redhat.com] On Behalf Of Chris Edillon > Sent: Tuesday, May 22, 2007 9:42 AM > To: Discussion list about Kickstart > Cc: centos(a)centos.org > Subject: Re: trying to run sshd daemon in kickstart environment > > On Mon, 2007-05-21 at 10:54 -0700, Guolin Cheng wrote: > > > I tried to make kickstart environment a little bit more charming by > > firing up openssh daemon in the limited environment. I edited/checked > > a bunch of files and almost succeeded but still not. > > > > I can reach the machine to run a command like 'ssh -x > > <kickstartClient> <command>' and it does work for %pre and both chroot > > and non-chroot %post sections, in fact, you can run a command on > > kickstartClient through ssh connections without problems. But it > > still fails because I can not ssh into the kickstartClient to get a > > local command shell. > > > > In short, 'ssh -x <kickstartClient>' fails, 'ssh -x <kickstartClient> > > <command>' works. > > > > Any one has succeeded in this topic? Life will be much happier if we > > can freely turn on/off sshd daemon for Kickstart environment. Thanks. > > you may need to force ssh to allocate a pseudo-tty, > try "ssh -t -x <ksClient>". the -t option is described > in the ssh manpage. > > chris > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list(a)redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list

1 0

It works now -- RE: trying to run sshd daemon in kickstart environment
by Guolin Cheng 23 May '07

23 May '07

Hi, Thanks a lot for so many helpful responses. The fix is pretty straight: just mount /dev/pts again at the chrooted %post environment where my original sshd fires up from. One command 'Mount -t devpts -o rw,gid=5,mode=620 devpts /dev/pts' or just a bare 'mount /dev/pts' command fix the problem since the devpts entry is in fstab already. I also hacked image stage2.img to include sshd daemon binary, libraries and configuration files, and fire up the ssh daemon at the first line of %pre script section. Then disable my original fired up sshd daemon at %post section. Now kickstart environment is not 'dump' at all -- I can kick into and monitor the kickstart clients any time and stop run-away kickstart processes with 'reboot' command immediately should my home directory server upgrade turn into a disaster. --Guolin -----Original Message----- From: kickstart-list-bounces(a)redhat.com [mailto:kickstart-list-bounces@redhat.com] On Behalf Of Chris Edillon Sent: Tuesday, May 22, 2007 9:42 AM To: Discussion list about Kickstart Cc: centos(a)centos.org Subject: Re: trying to run sshd daemon in kickstart environment On Mon, 2007-05-21 at 10:54 -0700, Guolin Cheng wrote: > I tried to make kickstart environment a little bit more charming by > firing up openssh daemon in the limited environment. I edited/checked > a bunch of files and almost succeeded but still not. > > I can reach the machine to run a command like 'ssh -x > <kickstartClient> <command>' and it does work for %pre and both chroot > and non-chroot %post sections, in fact, you can run a command on > kickstartClient through ssh connections without problems. But it > still fails because I can not ssh into the kickstartClient to get a > local command shell. > > In short, 'ssh -x <kickstartClient>' fails, 'ssh -x <kickstartClient> > <command>' works. > > Any one has succeeded in this topic? Life will be much happier if we > can freely turn on/off sshd daemon for Kickstart environment. Thanks. you may need to force ssh to allocate a pseudo-tty, try "ssh -t -x <ksClient>". the -t option is described in the ssh manpage. chris _______________________________________________ Kickstart-list mailing list Kickstart-list(a)redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list

1 0

Recommendations
by Scott McClanahan 23 May '07

23 May '07

We have two virtual machines on ESX 3 running CentOS 4.3 and we'd like to turn them into some sort of highly available nfs file server. Currently, I am familiar with DRBD and RHCS but I was curious what others might recommend in such a situation. I'm not sure how easily we could use RHCS in such a situation because we don't really have the advantage of shared storage in this setup. We are strictly limited to the two boxes. Having said that, it would be nice to have some of the exports running on one node (tied to a VIP) and others on the other node (tied to another VIP) if possible and manage those services individually if needed. So basically both nodes would be exporting select locations at any given time on this highly available file system. That is not 100% necessary but it would be nice if the capability is there. I would assume some sort of fencing mechanism would need to been in place as well. This might not be the best place to ask an ESX question but would 'raw device mapping' work in such a scenario? I don't know much about it. I can give more details if needed but hopefully this is enough for some suggestions. Thanks!

2 2

Simple Install of x86_64 CentOS 5 is failing
by James Olin Oden 23 May '07

23 May '07

It gets all the way through the install, and then when it reboots, grub can't find the kernel. Grub can't find the kernel because the kernel was not instaled for some reason? I looked at the box through rescue mode and in /boot there is no kernel. Any ideas what might have happened? Cheers...james

2 2

Yum vs. pirut
by Niki Kovacs 23 May '07

23 May '07

Hi, Once I'm working with Yum, can i safely remove pirut? cheers, Niki Kovacs -- Dyslexics have more fnu.

3 5

Re: [CentOS-announce] CentOS 4.5 is released for i386, x86_64, and ia64
by Larry Vaden 23 May '07

23 May '07

On 5/17/07, Johnny Hughes <johnny(a)centos.org> wrote: > The CentOS development team is pleased to announce the release of CentOS > 4.5 for i386, x86_64 and ia64. What steps are required to make sure yum running in autopilot mode doesn't destroy a locally compiled and configured postfix? rgds/ldv

4 4

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