Hide

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.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Commands by unixmonkey57489 from sorted by
Terminal - Commands by unixmonkey57489 - 13 results
sudo apt-get install ffmpeg libavcodec-extra-53
for f in *.mp4; do avconv -i "$f" -b 256k "${f%.mp4}.mp3"; done
for i in *.pdf ; do convert "$i" "${i%.*}.jpg" ; done
ls -1 | while read file; do new_file=$(echo $file | sed s/\ /_/g); mv "$file" "$new_file"; done
sudo systemctl enable lxdm
sudo reboot
sudo nano /etc/modules-load.d/virtualbox.conf
2013-05-16 14:41:51
Functions: sudo
-1

To do this, we?ll use nano to create a new configuration file called ?virtualbox.conf?. This file will go in the ?/etc/modules-load.d? directory, which contains files that need to be loaded when Arch boots up. Since adding a file to this directory requires administrative permissions, we?ll need to precede our command with ?sudo? once again.

When nano brings up the blank file, add these three lines to it:

vboxguest

vboxsf

vboxvideo

As usual, when you?re finished entering text in nano, type Control-X to exit to the command line, and answer ?y? for yes when you?re asked whether you want to save your work, and then hit ?Return? to accept the filename. At this point, reboot your machine for the Guest Additions to take effect.

sudo pacman -S virtualbox-guest-utils
2013-05-16 14:39:38
Functions: sudo
0

Here you have to choose the correct kernel number, for example linux38.

mhwd --help
2013-05-16 14:30:18
0

One base component is our hardware detection. It is a C++ library and app and is designed after a dynamic structure. Any kind of hardware, no matter if usb or pci, can be configured by mhwd. There is just a simple configuration file which tells mhwd what to do. This way we also support hybrid graphics cards out of the box. However there are currently only mhwd configs for nvidia optimus setups. But this gap will be filled soon. Just play with some of those commands to get a feeling about mhwd.

sudo pacman -Scc
sudo mhwd-kernel linux00
2013-05-16 14:02:46
Functions: sudo
1

00 is the number of the linux kernel e.g. linux39

sudo pacman-mirrors -g
sudo pacman -Syu
2013-05-16 13:49:14
Functions: sudo
0

Warning: Instead of immediately updating as soon as updates are available, users must recognize that due to the nature of Arch's rolling release approach, an update may have unforeseen consequences. This means that it is not wise to update if, for example, one is about to deliver an important presentation. Rather, update during free time and be prepared to deal with any problems that may arise.

Pacman is a powerful package management tool, but it does not attempt to handle all corner cases. Read The Arch Way if this causes confusion. Users must be vigilant and take responsibility for maintaining their own system. When performing a system update, it is essential that users read all information output by pacman and use common sense. If a user-modified configuration file needs to be upgraded for a new version of a package, a .pacnew file will be created to avoid overwriting settings modified by the user. Pacman will prompt the user to merge them. These files require manual intervention from the user and it is good practice to handle them right after every package upgrade or removal. See Pacnew and Pacsave Files for more info.

Tip: Remember that pacman's output is logged in /var/log/pacman.log.