What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

32 bits or 64 bits?

Terminal - 32 bits or 64 bits?
getconf LONG_BIT
2009-08-08 21:22:19
User: caiosba
Functions: getconf
32 bits or 64 bits?

Easy and direct way to find this out.


There is 1 alternative - vote for the best!

Terminal - Alternatives
getconf LONG_BIT
2012-12-12 23:51:51
User: varghjarta
Functions: getconf

Needed a quick way to see if my server distro that I setup years ago was running 32bit or not, since with time I had forgotten.

Note: does not check _hardware_ e.g. /proc/cpuinfo but rather the kernel installed

sudo lshw -C cpu|grep width
grep -q '\<lm\>' /proc/cpuinfo && echo 64 bits || echo 32 bits
2013-02-09 13:01:36
User: sputnick
Functions: echo grep

This command tell you if your hardware is 32 or 64 bits even if you install a 32bits OS on a 64 bits hardware.

If your distro don't support the -q switch, try doing :

grep &>/dev/null '\<lm\>' /proc/cpuinfo && echo 64 bits || echo 32 bits
isainfo -v
2013-01-04 03:07:28
User: halcyonblue

This is likely only valid on Solaris based systems. Unfortunately a lot of the more universal techniques for determining if a system is 32bit or 64bit on x86 solaris fail to give much more information than "i86pc"

Know a better way?

If you can do better, submit your command here.

What others think

Does this return the system's capability or merely its current configuration? I ask because on the new box I recently built to learn with, it reported only 32-bit but I assume it's be 64-bit-capable. (I know this also depends on what version of the OS I installed so I'll do a little more digging on that too since I don't remember offhand.)

Comment by bithaze 381 weeks and 6 days ago

I've run this command on many different systems including Linux, SunOS, etc, and it works great. I've yet to find a POSIX based system it doesn't work on.

I just saw the alternative, 'arch' command and that seems to work good too, but that will output x86 or x86_64 not an integer with the number of bits.

As for looking at /proc/cpuinfo, that will just tell you what your processor is capable of. A lot of times, you'll find a system that is running a 32 bit OS but has a 64 bit processor. So, I would avoid getting details on the processor itself if what you really want to know what your OS is supporting. I suspect that some of the other alternatives might just be checking CPU hardware and not the OS.

I'll stick with getconf LONG_BIT, although now that I know the arch command exists, I'll see if it works on all POSIX systems like the getconf LONG_BIT command seems to.

Comment by sonic 75 weeks and 4 days ago

Your point of view

You must be signed in to comment.