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:
only for sudo-style systems.
Use this construct instead of I/O re-directors ``>'' or ``>>'' because
sudo only elevates the commands and *not* the re-directors.
***warning: remember that the `tee` command will clobber
file contents unless it is given the ``-a'' argument
Also, for extra security, the "left" command is still run unprivileged.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
sudo vim /etc/system-file.cfg
[quote]sudo vim /etc/system-file.cfg[/quote]
Yes, of course, but if all you need to do is replace the contents of a file with a one-liner,
the pipe is quicker - esp. when remotely managing a server.
If you need to type the full path of some file into a config file,
the pipe is quicker **and more accurate**
such as:
ls /var/log/samba/log.winbindd | sudo tee -a /etc/some-file.cfgsudo vi /etc/some-file.cfg... you will know if your path and file are correct before
even vim-ing the config file.