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:



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.

Top Tags



archlinux: find more commands provided by the package owning some command

Terminal - archlinux: find more commands provided by the package owning some command
pkgfile -lb `pkgfile <command>`
2010-10-01 04:54:49
User: infinull
archlinux: find more commands provided by the package owning some command

uses the pkgfile command (part of the community repository), highly suggested.


There is 1 alternative - vote for the best!

Terminal - Alternatives
w=`whereis <command> | awk '{print $2}'`; p=`pacman -Qo $w | sed -e 's/.*is owned by \([[:alpha:]]\+\).*/\1/'`; pacman -Ql $p | grep 'bin'
2010-10-01 04:28:04
User: conan
Functions: awk grep sed
Tags: archlinux

Sometimes when I find a new cool command I want to know:

1.- which package owns it, and

2.- are there any other cool commands provided by this package?

Since I don't necessarily need to know always both, I don't use this version, but I bundle it into two separate functions:

# get command package owner

# it can work without the full path, but sometimes fails, so better to provide it with whereis command

owner () {

pacman -Qo `whereis $1 | awk '{print $2}'`


whatelse () {

package=`owner ${1} | sed -e 's/.*is owned by \([[:alpha:]]\+\).*/\1/'`

pacman -Ql $package | grep 'bin'


Know a better way?

If you can do better, submit your command here.

What others think

While the solution provided by infinull is shorter and looks simpler at first glance I wanted to note that you have to install pkgtools to have the pkgfile command, and also build (pkgfile --update) a filelist before use and maintain this file listing with cron for it to work.

On the other hand my solution doesn't rely on extra tools but standard, already installed commands on any archlinux machine.

Also I timed the two versions and this is what I've got:

time whatelse skill


real 0m0.765s

user 0m0.550s

sys 0m0.187s

time pkgfile -lb `pkgfile skill`

real 0m17.796s

user 0m17.469s

sys 0m0.297s

Comment by conan 237 weeks and 1 day ago

Your point of view

You must be signed in to comment.