search for: sudoyang

The xfs kernel modules at dev.centos.org are very handy. There are a couple of xfs modules in the 4.3 x86_64 directory, but I don't think it's for the x86_64 4.3 kernel (2.6.9-34). The latest ones in that directory is for the -22 kernel (I believe this came with CentOS 4.2).

For over five years now, we use Perl during the post install of kickstart to perform customization. It appears the Perl setup is broken in CentOS 4.3 x86_64. It still works fine on CentOS 4.1 32-bit. The library Perl needs is missing: # perl -V error while loading shared libraries: libperl.so: cannot open shared object file: No such file or director Is this a bug or is RedHat deprecating

I'm getting a couple of systems that are arriving with the new 3ware 9550sx controller. Does anyone know when this will be natively supported by CentOS? Has anyone built an RPM of the driver/module for this new controller?

Is there a way to determine what package changed from CentOS 4.1 to 4.2 (or between any two versions)? I need to create a yum repository to upgrade some machines that cannot talk to the Internet. Thanks for any help. ID:FONGVANG

What exactly is different between the 32 and 64-bit version of CentOS 4.2? The kernel (drivers, file system, etc.) is probably compiled to support 64-bit and probably glibc. What're some important differences between the 32 and 64-bit version? I'm just trying to get a deeper understanding. Thanks in advance for any help. FongVang

In our environment, we have a mixture of 32 and 64 bit systems. Would the 64-bit CentOS flavor work 32 bit systems? What kind of impact would this have on performance if the 64-bit OS on 32-bit hardware?

In CentOS 4.1/2, what package contains this library: libstdc++-libc6.2-2.so.3? I installed a couple of the compat- packages, but this library is still missing.

What's the easiest way to disable a kernel module during kickstart? Is there a syslinux command that could be passed in to prevent a module from loading? TIA!

For some reason, CentOS 4.1 waits approximately 3-5 min at the "Determining host name and domain" during kickstart. RedHat 7.1, RedHat 9.0, RedHat Enterprise 3.0, and even CentOS 4.0 do not have this problem using the same kickstart server (my kickstart server is configured to kick all of them). Does anyone know why CentOS 4.1 is particularly slow at this stage of kickstart? Thanks

I downloaded the src rpm for CentOS 5 and tried to recompile it. It failed with the following message: + sh ./scripts/modsign/modsign.sh /var/tmp/kernel-2.6.18-8.el5-root /lib/modules/2.6.18-8.el5PAE/kernel/drivers/char/watchdog/pcwd_pci.ko CentOS gpg: WARNING: unsafe permissions on homedir `..' + mv -f

I read that XFS has problems with 4K Stack size for Linux on 32-bit systems. How did we address this in the centosplus kernel? Since what release of CentOS was this problem resolved? Is there a quick way to know what size the Linux stack is configured to be in a system's that's running? Thanks for your help. -------------- next part -------------- An HTML attachment was scrubbed...

I have a couple of 64-Bit Xeon's with CentOS 4.2 x86_64 installed on them. They don't all have the same motherboards. I've having a difficult time getting CentOS 4.2 x86_64 to boot on some of them in SMP mode (UP works fine). After the installation of CD, it boots up but kernel panics with the following error: Badness in i8042_panic_blink at drivers/input/serio/i8042.c:992 This is

3ware now provides driver disk for CentOS. A couple of months ago, I had to add support for the 3ware 9550sx. The driver disk provided for CentOS 4.1 work perfectly. I now need to add support for the 3ware 9550sx for CentOS 4.3 x64. Although the driver disk is available, it doesn't seem to work. Anaconda just can't find the 3w-9xxx module. This is the same seutp as CentOS 4.1 (which

I'm trying to kicktart a CentOS 4.3 x86_64. However, anaconda is unabled to do dhcp, complaining about"no DHCP reply received". While tailing the log on the dhcp server, I clearly see a request come in and address is offered. This same machine kicks fine with CentOS 4.1 (32-bit). Since anaconda could potentially use a different NIC (this system contains 2 NICSs), I've tried

Is there a way to disable the auto reboot when the kernel panics during bootup? I tried passing "panic=0" using grub but it still reboots automatically. I need to at least pause it long enough to read the screen to determine the cause of the panic. Thanks for any help.

The dev.centos.org site has the XFS kernel module RPMS for the CentOS 4.1 and 4.2 kernels. Will there be one for the kernel that shipped with CentOS 4.3? This is one of the 4.2 XFS kernel module RPM, e.g.: kernel-module-xfs-2.6.9-22.0.1.ELsmp-0.1-1.i686.rpm

I just installed CentOS 4.2 x64 bit version. After installaton, the system boots but kernel panics with this message: Badness in i8042_panic_blink at drivers/input/serio/i8042.c:992 The kernel seems to load completely. It gets passed the point where it prompts to press "I" for interactive mode. Something after that probably caused a module to load that crashed the kernel. Any idea

Is it possible compile an a new x86_64 kernel on an i686 CentOS system? When I tried to do so with this command rpmbuild -ba --target x86_64 kernel-2.6.spec I got the following error: make[1]: *** [nonint_oldconfig] Error 51 make: *** [nonint_oldconfig] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.40130 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.40130

I just realized that the PS2 on our CentOS systems do not work (normally we use USB). Shouldn't they work by default?

One of our systems run Apache 2.0.52 (httpd-2.0.52-12.2.ent.centos4 rpm). The kernel we're running is 2.6.9-11.ELsmp. After a few weeks of uptime, Apache refuses to start with the following error in error.log: [crit] (28)No space left on device: mod_jk: could not create jk_log_lock With Apache not running, there're a lot of semaphores left behind by Apache, e.g.: ------ Semaphore