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/
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.
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
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:
Display the machine "hardware name" 32 or 64 bit.
"x86_64" is shown on 64 bit machines
"i686" is typically shown on 32 bit machines (although, you might also see "i386" or "i586" on older Linuxen).
On other "unix-like" systems, other hardware names will be displayed.
For example, on AIX, "uname -m" gives the "machine sequence number".
For whatever reason, IBM decided that "uname -M" would give the machine type and model.
(ref: http://www.ibm.com/developerworks/aix/library/au-aix-systemid.html )
On Sun Solaris, "uname -m" can be used to determine the chip type and "isainfo -v" will reveal
if the kernel is 64 or 32 bit.
(ref: http://www.ibiblio.org/pub/packages/solaris/sparc/html/32.and.64.bit.packages.html )
A more reliable way to determine "64-bit ness" across different Unix type systems is to compile the following simple C program:
cat <<eeooff > bits.c
/*
* program bits.c
* purpose Display "32" or "64" according to machine type
* written January 2013
* reference http://www.unix.org/whitepapers/64bit.html
*/
/* hmm, curious that angle-brackets removed by commandlinefu.com data input processing? */
#include "/usr/include/stdio.h"
long lv = 0xFFFFFFFF;
main ( ) {
printf("%2d\n",(lv < 0)?32:64);
}
eeooff
Compile and run thusly: cc -o bits bits.c; ./bits
This command adds a urpmi media source called "google-talkplugin" to the urpmi configuration on Mandriva or Mageia. Needs to be run as root. We specify the option "--update" so that when Google provides a newer version of Google Talk plugin in their download system then running a system update (eg: "urpmi --auto-update") will result in our copy of Google Talk plugin getting updated (along with any other Mandriva/Mageia pending updates).
To install Google Talk plugin from this source, use:
urpmi google-talkplugin # install plugin used for voice and video Google chat via gmail
This command adds a urpmi media source called "google-chrome" to the urpmi configuration on Mandriva or Mageia. Needs to be run as root. We specify the option "--update" so that when Google provides a newer version of Google Chrome web browser in their download system then running a system update (eg: "urpmi --auto-update") will result in our copy of Google Chrome getting updated (along with any other Mandriva/Mageia pending updates).
To install Google Chrome from this source, use:
urpmi google-chrome-stable #install Google chrome web browser
i686 = 32 bits
x86_64 = 64 bits
the command "getconf LONG_BIT" will work just as well.
You can use this one-liner for a quick and dirty (more customizable) alternative to the watch command. The keys to making this work: everything exists in an infinite loop; the loop starts with a clear; the loop ends with a sleep. Enter whatever you'd like to keep an eye on in the middle.