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.
[bbbco@bbbco-dt scripts]$ vi startingdir.sh ----------------- #!/bin/bash echo $(cd $(dirname $0) && pwd) ----------------- [bbbco@bbbco-dt scripts]$ ./startingdir.sh /home/bbbco/scripts [bbbco@bbbco-dt scripts]$ cd .. [bbbco@bbbco-dt ~]$ scripts/startingdir.sh /home/bbbco/scripts [bbbco@bbbco-dt ~]$ cd Downloads/ [bbbco@bbbco-dt Downloads]$ /home/bbbco/scripts/startingdir.sh /home/bbbco/scripts [bbbco@bbbco-dt Downloads]$
Also resolves symlinks, showing the full path of the link target
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
work for execute file
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
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:
dirname $(readlink -f $0)