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

Determine whether a CPU has 64 bit capability or not

Terminal - Determine whether a CPU has 64 bit capability or not
if cat /proc/cpuinfo | grep " lm " &> /dev/null; then echo "Got 64bit" ; fi
2010-04-10 15:31:58
User: xeor
Functions: cat echo grep
Determine whether a CPU has 64 bit capability or not

Check if you have 64bit by looking for "lm" in cpuinfo. lm stands for "long mem". This can also be used without being root.


There are 4 alternatives - vote for the best!

Terminal - Alternatives
sudo dmidecode --type=processor | grep -i -A 1 charac

Know a better way?

If you can do better, submit your command here.

What others think

This is a bit cleaner and simpler:

grep -q " lm " /proc/cpuinfo && echo "Got 64bit"
Comment by eightmillion 367 weeks ago

Just a nitpick: "lm" stands for long mode (not long mem), meaning that the processor registers are 64bit long in this mode.

By the way, /proc/cpuinfo works on Linux only, of course, so this is not portable (except that it also works on FreeBSD when the "Linuxulator" is enabled and linprocfs mounted on /compat/linux/proc).

On Solaris use this command to find out if 64bit is supported by the platform:

isainfo -bv

On FreeBSD, this command can be be used:

grep -w "LM" /var/run/dmesg.boot && echo "Got 64bit"
Comment by inof 367 weeks ago

My two cents, for Red Hat flavours:


sample output:

Comment by KoRoVaMiLK 366 weeks and 6 days ago

Your point of view

You must be signed in to comment.