similar to: 64-bit CentOS 4.2

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

Hello to everybody, it?s possible run 32 bits program on a 64 bits CentOS core?? --------------------------------- Correo Yahoo! Comprueba qu? es nuevo, aqu? http://correo.yahoo.es -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20051122/d38637c7/attachment-0005.html>

From: Maciej ?enczykowski <maze at cela.pl> > That's a good point - does anyone know what the new Intel > Virtualization thingamajig in the new dual core pentium D's is about? It's all speculation at this point. But there are _several_ factors. But I'm sure the first time Intel saw AMD's x86-64/PAE52 presentation, the same thing popped into my mind that popped

Is this a known bug? Suprisingly google didn't turn up much. I'm running DDR RAM and a AMD XP processor on CentOS 4.

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

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?

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

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

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

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!

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

Hi, I have several machines using xen-hypervisor-3.2-1-i386 from etch-backports and they recently got upgraded to 20 or 24G RAM. I have seen talk of a limit of a 16G RAM with 32bit PAE Xen and indeed this is what I am seeing. I am guessing there is still no way to get the 32bit hypervisor to see more than 16G RAM, and I must go to 64bit. Can I boot a 64bit hypervisor and still keep the same

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.

On Wed, Jun 25, 2014 at 3:30 PM, John Criswell <criswell at illinois.edu> wrote: > On 6/25/14, 5:15 PM, Vadim Chugunov wrote: > > In a recent review via Phabricator, I was receiving bounce notifications for > mail being sent to llvm-commits because of "Too many recipients to the > message", even though I am a subscriber. I wonder how common is that. > > >

Hey folks, If I've got some code that I can compile using clang, that depends on a certain endianness, can I generate bitcode that will have the code operate correctly, even if run on machines of the the opposite endianness? If not, what're we talking about in specific work that'd be needed? Thanks, - Lally

Hello, the need here is to have a single LLVMContext used for multiple compilations. You make a good point about that by the way. If there are outstanding users cleaning the context under their seats might still pose a risk to them, and in that case deleting + newing a new LLVMContextImpl might actually not be very different. Marcello 2014-06-24 17:14 GMT+01:00 David Blaikie <dblaikie at