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.

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID

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.

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:

» all commands
» commands with 3 up-votes (commandlinefu3)
» commands with 10 up-votes (commandlinefu10)

Hide

News

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!

Hide

Top Tags

awk, bash, curl, find, grep, Linux, sed

Hide

Functions

Hide

Credits

Maintained by Jon H.

» [email protected]

Site originally by David Winterbottom (user root).

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

» The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
» If you wish to use your user account, you will probably need to reset your password.

Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Get full directory path of a script regardless of where it is run from

Terminal - Get full directory path of a script regardless of where it is run from

BASEDIR=$(dirname $(readlink -f $0))

2011-12-01 09:10:21

User: mackaz

Functions: dirname readlink

Up
Down

Get full directory path of a script regardless of where it is run from

Also resolves symlinks, showing the full path of the link target

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives

STARTING_DIR=$(cd $(dirname $0) && pwd)

2011-11-30 17:35:15

User: bbbco

Functions: cd dirname

Tags: cd dirname pwd variable

Up
Down

Get full directory path of a script regardless of where it is run from

Sometimes you need the full path to your script, regardless of how it was executed (which starting directory) in order to maintain other relative paths in the script.

If you attempt to just use something simple like:

STARTING_DIR="${0%/*}"

you will only get the relative path depending on where you first executed the script from.

You can get the relative path to the script (from your starting point) by using dirname, but you actually have to change directories and print the working directory to get the absolute full path.

Show sample output | Comments (2) | Add to favourites | Report as malicious

FULLPATH=$(perl -e "use Cwd 'abs_path';print abs_path('$0');")

2013-02-01 20:09:34

User: follier

Functions: perl

Tags: perl cd dirname pwd variable cwd abs_path

Up
Down

Get full directory path of a script regardless of where it is run from

Since none of the systems I work on have readlink, this works cross-platform (everywhere has perl, right?).

Note: This will resolve links.

Show sample output | Comments (0) | Add to favourites | Report as malicious

dirname $(readlink -f ${BASH_SOURCE[0]})