similar to: prevent kernel module from loading during kickstart

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

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

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

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

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?

Could someone tell me how the kernel used for kickstart (called the BOOT kernel in RH 9 days) is created? How does one generate this kernel using rpmbuild of the src rpm? I'm just trying to undertstand the differences. Thanks for any help.

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

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

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).

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?

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

I'm trying to add XFS and ReiserFS to CentOS, integrating with Kickstart. I think I'm fairly close. I've added xfs.ko and reiserfs.ko to modules.cgz in initrd. Several of my partitions now specify --fstype=xfs. I can see tty5 mkfs.xfs is creating the XFS file systems. The system currently installs completely via kickstart, but it does not mount the XFS file systems while in the

I have a total of 20 CentOS 4.1 systems running on fairly new hardware. About 6 of them are experiencing strange hangs without any indication -- nothing in /var/log/messages nor on the console -- sometime within 10-30 minutes after a reboot. The systems still responds to ping but you can't ssh to it. At the console, you could type "root" at the user prompt but it hangs immediately

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