How to Verify a Linux is 32-Bit or 64-Bit?

By -

To verify if a system is 32 bit versus 64 bit you can use the uname command. Below are examples of using the uname command from the CLI on a 32 bit system followed by using the uname command on a 64 bit system.
32 Bit CentOS Linux Server
1[root@server ~]# uname -a
2Linux server1.example.com 2.6.18-92.1.13.el5 #1 SMP Wed Sep 24 19:33:52 EDT 2008 i686 i686 i386 GNU/Linux
64 Bit CentOS Linux Server
1[root@server ~]# uname -a
2Linux server.example.com 2.6.18-53.1.21.el5 #1 SMP Tue May 20 09:35:07 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
As you can see above the 64 bit server will show x86_64 numerous times after the install date and time. The 32 bit system will show i686 and i386 after the install date and time. So it is very easy to verify if a system is 32 bit versus 64 bit using the “uname -a” command from a shell.

Comments

  1. UnknownSeptember 5, 2020 at 2:42 AM

    good information. if i compiled hello_world.c program in x86_64 machine, can i execute in i686? is there any limitations to execute successful ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Scan FC LUN's in RHEL/CentOS

By -
1.First find out how many disks are visible in “fdisk -l” . # fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l 2.Find out how many host bus adapter configured in the Linux box.you can use “systool -fc_host -v” to verify available FC in the system. # ls /sys/class/fc_host host0 host1 In this case,you need to scan host0 & host1 HBA. 3.If the system virtual memory is too low ,then do not proceed further.If you have enough free virtual memory,then you can proceed with below command to scan new LUNS. # echo "1" > /sys/class/fc_host/host0/issue_lip # echo "1" > /sys/class/fc_host/host1/issue_lip Note:   You need to monitor the “issue_lip” in /var/log/messages to determine when the scan will complete.This operation is an asynchronous operation. 4.Verify if the new LUN is visible or not by counting the available disks. # fdisk -l 2>/dev/null | egrep '^Disk' | egrep -v 'dm-' | wc -l If any new
Read more

CEPH bluestore using ceph-ansible

By -
Just to test the ceph bluestore i have created 2 virtual machine in virtualbox with hostname: admin & osd1. Attached the 2 10G hdd for the OSD's in both the nodes. Below are the commands that i used to deploy it using the ceph-ansible: git clone https://github.com/ceph/ceph-ansible cd ceph-ansible cp group_vars/osds.yml.sample group_vars/osds.yml cp group_vars/all.yml.sample group_vars/all.yml cp group_vars/mons.yml.sample group_vars/mons.yml cp site.yml.sample site.yml vi group_vars/osds.yml     devices:    - /dev/sdb     - /dev/sdc bluestore : true vi group_vars/all.yml ceph_stable: true ceph_mirror: http://download.ceph.com/ ceph_stable_key: https://download.ceph.com/keys/release.asc ceph_stable_release: kraken ceph_stable_repo: "{{ ceph_mirror }}/rpm-{{ ceph_stable_release }}" monitor_interface: enp0s3 monitor_address: 192.xx.xx.xx osd_objectstore: bluestore ceph_conf_overrides:    global:    en
Read more

Start wildfly service with standalone-full.xml

By kris -
Wildfly provides a service.bat in %WILDFLY_HOME%\bin\service. Calling the batch file with the install parameter installs Wildfly as a service on Windows. Once it is installed on windows, you can change the settings so that wildfly starts all the modules and services instead of default minimal setup. For this, change standalone.bat file and add this line : set "SERVER_OPTS=--server-config=standalone-full.xml" This will enable startup of all modules & services of wildfly from now on.
Read more