I have a 32 bit userland and kernel.(rhel5 based)
I have already updated kernel to 64 bit. 32 bit userland application successfully runs on 64 bit kernel.
Now I also want to use 64 bit userland binaries with 32 bit userland together.
What should be my next steps?
You need to setup a new repository that contains 64 bit userland [repository] Options.
Here is one, but it is for Red Hat 7.
Related
I have a 32 bit Windows Operating System. But my system supports 64 bit architecture,i could say that because when i downloaded and ran VMWare Processor Check for 64 bit compatibility tool from the VMware website it shows 'This host is capable of running a 64-bit guest Operating System under this VMWare product'. So with this 64 bit architecture would i be able to install and use Cloudera VM and then hadoop?
Based on the comments, you can go ahead and use 64 bit without any issues and hadoop will be up and running. However, you can always go back and download 32 bit and import in your VMWare and have both 64 bit and 32 bit imported. If in case you get in to any issues with 64 bit, then you can stop using it and run 32 bit.
If cloudera is not supporting 32 bit, then check with hortonworks VM.
Hope this helps!
I'm going through Linux Kernel code and interested in knowing which file will be responsible for setting long mode to support 64 bit or which will be telling the OS going to boot would be 32 bit or 64 bit??
Is it bootloader code responsible to set this mode up??
The boot loader (usually GRUB) is booting some Linux kernel. This kernel may be a 32 bits kernel (then able only to run 32 bits programs) or a 64 bits kernel.
64 bits Linux kernels are able to run thru execve(2) syscalls either 32 bits binary executable program (in a 32 bits process) or 64 bits program
So most kernels are 64 bits and can run both 32 or 64 bits ELF executables.
I guess that, depending how they are booted, Linux kernels start in 32 bits mode (at least when booted by GRUB).
I have a vbscript, which connects to a .mdb file using 32 bit drivers and it works fine on a 32 bit system, but when i try to run the same on a 64 bit system( with 32 bit office),the connection doesnt work.
I cant install 64 bit drivers as the system has 32 bit office.
Is it possible to connect to .mdb file using 32 bit drivers on a 64 bit system?
For your scenario, just make sure that the process executing your script is running on 32 bit.
You could try to call your script from the x86 PowerShell prompt to test it on your x64 system.
Under MacOS, you can change a little option for 32-bit executables called "Open in 32-bit mode". Wouldn't it work directly? And it works, but for some applications you had to select this option in order to run without problems. This was frequent in Safari, where some add-ons required a 32-bit environment.
I can't understand what makes an 32-bit executable not able to run directly in 64-bit, so what exactly changes in 32-bit mode?
This is really only of historical interest. In the transition period from 32 bit to 64 bit many apps were built as universal with 3 or sometimes even 4 architectures combined into one fat binary (aka "Universal Binary"), typically ppc, x86 and x86-64. In a 32 bit x86 environment the 32 bit x86 executable would be used. In a 64 bit x86-64 bit environment the 64 bit executable would be used. However in some cases you might want to use the 32 bit x86 executable even in a 64 bit x86-64 environment, e.g. in the case you mentioned where you have older plug-ins which are 32-bit only and can not be used with a 64 bit executable. Hence the option to launch an app in 32 bit mode.
Obviously a 32 bit app uses 32 bit APIs and has a 32 bit address space, whereas a 64 bit app has a 64 bit address space and uses 64 bit APIs.
We have an application written in C/C++ code running on 32-bits windows with 32-bit Hardware. My question is that if we upgrade our hardware to 64-bit and keep our OS 32-bit, does my application need a port to 64-bit? If it requires, what benefits will be there on a 32 bit OS?
Hardware doesn't count -- the OS does. Ergo:
32 bit hardware with 32 bit OS will run only 32 bit ports
64 bit hardware with 32 bit OS will run only 32 bit ports
64 bit hardware with 64 bit OS will run both 32 bit and 64 bit ports
The advantage of recompiling for 64 bit is access to more than 3GB ram and a speed increase if you operate on 64 bit datatypes or take advantage of compiler intristics (and a few others, but do not count on a immedate gain).
If you keep the OS 32-bit, you must keep the app 32-bit, for many common values of OS. We, of course, cannot use telepathy to tell which OS you are using.