similar to: System hangs silently

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.

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

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

What release of Fedora is CentOS 4 (RHEL 4) based on?

I've read in many places that file systems on Linux do not suffer the same fragmentation problems of Windows systems. No one has provided a clear explanation as to why fragmentation is not an issue for file systems such as ext2/3, reiserfs, xfs, etc. Just curious.

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

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'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?

This ntp.conf file works fine under RedHat 9: authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 fudge 127.127.1.0 stratum 10 trustedkey 1 enable bclient broadcastclient However, it doesn't work on CentOS 4.1. ntpd complains with this error message: Unable to listen for broadcasts, no

Has anyone tried to install a CentOS 5.x kernel on a CentOS 4.x system? Is this doable? I"m aware of the dependencies but I'm curious if anyone has done this successfully. Basically, we have a few hundred 4.x systems that cannot be upgraded to 5.x, yet, but we do need the kernel update to fix the XFS problem as described here: http://bugs.centos.org/view.php?id=3125 -------------- next

I'm trying to kickstart a Centos 4.1 system with the minimum set of packages. I have no use for ypbind so I'm trying to prevent from being installed, but kickstart/anaconda always insist on its installation (complaining that the package is missing). This is the %packages section of my ks file so far: %packages #-@ dialup kernel grub e2fsprogs lvm2 -slocate -bluez-utils -bluez-bluefw

in dom0, how does one get and set the link information for a NIC? In a non-xen kernel, we could get this info by simply running: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes:

Has anyone gotten Apache 2.0.54 to build on CentOS 4.1? Apache 2.0.52(distrbiuted with CentOS 4.1) compiles file. This is the error: /scratch/apache2.src/httpd-2.0.54/srclib/apr/libtool --silent --mode=link gcc -g -O2 -pthread -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DAP_HAVE_DESIGNATED_INITIALIZER

Has anyone been able to get a Xen Windows domU to install or work properly on CentOS 5? I'm trying to do that now. It's able to boot and start he installation (from ISO), but after partitioning the disk and copying a few files to the hard drive, it cannot boot into the graphical installer. This is the config file I'm using: import os, re arch = os.uname()[4] if

Has anyone gotten XFS support for a CentOS 4.x or 5.0 domU? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070503/4afbfc84/attachment-0001.html>

I just installed a CentOs 5 domU system on a CentOS 5 dom0 system following the instructions detailed here: http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU. The installation went through successfully. After installation, however, pygrub can't find a kernel. This is the xen cfg file I'm using: bootloader="/usr/bin/pygrub" name = "testsrv" memory =

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

A hardware vendor shipped us a product installed with RedHat 8.0 with all file systems created as ext3. This system has about 800 GB of space which we use for buffering email files (in RFC format). Several weeks into the project and with millions of emails stored, we started seeing "out of inode" (something like that) error messages in the /var/log/messages. Are inodes fixed on ext3

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