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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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



get cpu info from dmesg

Terminal - get cpu info from dmesg
dmesg | grep cpu
2009-04-03 01:57:04
User: kingji
Functions: dmesg grep
get cpu info from dmesg

get cpu info from dmesg


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

cat /proc/cpuinfo sounds good

Comment by servermanaged 381 weeks and 1 day ago

when i do dmesg | grep cpu, i get this:

[ 0.000000] Initializing cgroup subsys cpuset

[ 0.000000] Initializing cgroup subsys cpu

[ 16.245264] Initializing cgroup subsys cpuacct

[ 18.120872] cpuidle: using governor ladder

[ 18.120921] cpuidle: using governor menu

[ 133.714393] Marking TSC unstable due to: cpufreq changes.

Not too helpful. (I'm using Ubuntu)

Comment by alperyilmaz 381 weeks and 1 day ago

sudo dmidecode | awk '/AMD/,/^$/'

sudo dmidecode | awk '/Intel/,/^$/'

Comment by Williebee 381 weeks and 1 day ago

try `cat /proc/cpuinfo` for some actually useful info.

Comment by sirlewk 375 weeks and 6 days ago

You can use lshw or hwinfo

hwinfo --cpu lshw -class processor

You shouldn't rely on dmesg for hardware info.


Comment by unixmonkey4372 370 weeks ago

Your point of view

You must be signed in to comment.