Nov 28 2008

How to Verify a CentOS Linux Server is 32 Bit or 64 Bit

Posted by alex in Insights at 2:57 AM

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

[root@server ~]# uname -a
Linux 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

[root@server ~]# uname -a
Linux 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.

Related posts:

  1. Linux: Setup TFTP Server on CentOS The below steps will allow you to set up a...
  2. Linux CLI FTP Over Explicit TLS SSL Use lftp for Linux command line FTP with explicit TLS/SSL....
  3. How To Add Static Routes In CentOS There are numerous ways to add static routes in Linux...
  4. Routing Issues With One Server Connected To Two Networks Recently I was assisting a company set up a new...
  5. Linux CLI Commands For Windows The best way I have found to emulate Linux commands...
Tags: , , , , , , , , ,

This entry was posted on Friday, November 28th, 2008 at 2:57 AM and is filed under Insights. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

« 
 »
12 Responses to “How to Verify a CentOS Linux Server is 32 Bit or 64 Bit”
  1. Marlon says:
    October 21, 2011 at 12:10 PM

    Worked like a charm!

    [Reply]

    alex Reply:
    November 6th, 2011 at 2:46 PM

    Hello Marlon,

    Good to hear. Thanks for taking the time to leave feedback.

    Thanks.
    alex

    [Reply]

    Reply
  2. johan says:
    March 23, 2012 at 10:47 AM

    Short and to the point. Was very helpful.

    [Reply]

    alex Reply:
    April 3rd, 2012 at 1:53 AM

    Hello johan,

    Thanks for posting feedback.

    Thanks.
    alex

    [Reply]

    Reply
  3. HelgiK says:
    July 22, 2012 at 3:36 PM

    Thanks for that, now I know, that I’ve installed a 32 bit version. I tried the 64 bit version of SL but when I wanted to install it, something went wrong, and it won’t install. My processor is 64 bit compatible, AMD Athlon 64 3200+ , but I don’t know, if having only 4 GB RAM is a hinderance.

    I’m doing this without my glasses and the print is so small, that I can hardly see what I am typing.

    Thanks again for the info.

    Helgi

    [Reply]

    Reply
  4. aprigio simões says:
    August 26, 2012 at 8:52 AM

    No
    uname -m
    or
    arch

    [Reply]

    Reply
  5. Eric Tong says:
    October 11, 2012 at 10:01 PM

    Thank you for your posting!

    Example:
    [root@localhost ~]# getconf LONG_BIT
    64

    [Reply]

    Sathya Meda Reply:
    October 24th, 2012 at 7:53 AM

    Thanks for pointing out getconf and I prefer this over uname. A possible enhancement: use “getconf WORD_BIT” instead of “getconf LONG_BIT”, since WORD represents natural unit of data that c an be handled by a particular processor.

    [Reply]

    Sathya Meda Reply:
    October 31st, 2012 at 12:06 AM

    Seems like “getconf LONG_BIT” is the correct one – I found that on one of my 64 bit OS installs, WORD_BIT yielded 32, whereas LONG_BIT yielded 64.

    [Reply]

    alex Reply:
    December 22nd, 2012 at 4:18 PM

    Hello Sathya,

    Thanks for following up to your post. I wasn’t aware of the getconf command you could issue to provide the same information but now that I am I will be using it in the future. Like you I prefer getconf over uname!

    Thanks.
    alex

    [Reply]

    alex Reply:
    December 22nd, 2012 at 4:03 PM

    Hello Eric,

    Awesome! I was not aware of this command and appreciate you taking the time to share.

    Thanks.
    alex

    [Reply]

    Reply
  6.  
Leave a Reply

*Type the letter/number combination in the abvoe field before clicking submit.

CAPTCHA Image
*