I'm used to putting common scripts in /usr/local/bin so that I can execute them from anywhere with the terminal.

For example, I make a shell script named 1, make it executable with chmod +x 1 and put it in /usr/local/bin, and inside the script I type #!/bin/sh on the first line, and then my commands. From there on, it's very conveniently usable and quick to execute by typing


on the terminal, from inside any folder.

My problem is that I'm currently working on a computer where can't do sudo and I can't expect to get it either, so I can't place my script in /usr/local/bin.

What are my options? Is there another path with the same "run from anywhere" capability, which I can access without sudo, or another way to achieve something equivalent?

The accepted answer to this post says

For user-scoped scripts, use bin/ in your home directory.

Which I tried, but there is no bin folder in my home directory, and when I created one, I still could not run the script from anywhere else.

I'm running on Ubuntu 12.04 LTS.

  • 2
    Don't use 1 or something like that as script name. Try to calculate something in your shell: e.g. expr 1 + 1 (and if not you are doing it, some script will do it at some point for sure)
    – frlan
    Commented Jul 1, 2015 at 8:27
  • 1
    @frlan: How would expr 1 + 1 be affected by the presence of a script named 1?
    – psmears
    Commented Jul 1, 2015 at 20:39
  • True... not affecting expr, nor bash arithmetic $(( 1 + 1 )).
    – Campa
    Commented Jul 8, 2015 at 9:10

4 Answers 4


What are my options? Is there another path with the same "run from anywhere" capability, which I can access without sudo, or another way to achieve something equivalent?

How to do it?

Create some dir in your home to hold your scripts normally named as bin as convention.

mkdir ~/bin

Now move your scripts to bin

mv somescript ~/bin

Now how to make it tun from everywhere?!

You have to add the bin to the PATH

open your .bashrc

gedit .bashrc

and add this line:

export PATH=$PATH:/home/username/bin

Don't forget to replace username with your User Name

Save and exit, then source the bashrc

source .bashrc

and now you are fine, you can run your script as you used to do! but you have to notice this is related to your user only.

Note: It's better to rename your scripts other than 1 ,2 since you may face some issues with that names


You can do same just create the bin dir in your home then source ~/.profile instead of ~/.bashrc. Since adding the ~/bin to your PATH is already listed in .profile

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
  • I use export PATH=$PATH:$HOME/bin so I can use the same bashrc for other accounts with different user names. Commented Jul 1, 2015 at 8:23
  • 1
    Just to mention ~/bin is in $PATH by default on Ubuntu. Just run source ~/.profile or log out/in after you created the directory. Commented Jul 1, 2015 at 8:26
  • @JacobVlijm In which version?!!! I use 12.04, 14.04, 15.04 and none of them has ~/bin in PATH
    – Maythux
    Commented Jul 1, 2015 at 8:29
  • In all of them, I always use it, in many of my (accepted) answers as well, never got any comment on that, works her at home on five systems as well, but, as said, after running source ~/.profile . See (e.g.) here: askubuntu.com/a/247422/72216 Commented Jul 1, 2015 at 8:33
  • 1
    He said source ~/.profile, he never said source ~/.bashrc. :) Also, as a general rule, environmental variables should go in .profile and not .bashrc since they only need to be set up once. (none of this is to say that your answer is not good, mind you, and +1 from me)
    – terdon
    Commented Jul 1, 2015 at 8:58

In addition to https://askubuntu.com/a/643030/218015 you might can also define an alias inside your .bashrc for small, often used tasks. E.g.

alias ll='ls -l'
alias ls='ls --color=auto'

will create you a "command" ll, which is doing ls -l and ls will be coloured after defining the alias. https://wiki.ubuntuusers.de/alias is having some more examples and a howto for setting it up.


Try ~/.local/bin/.

(I acknowledge this answer isn't adding anything new but there's a short answer to this question that shouldn't require reading everything else.)

  • 1
    Also see the answers here and here for more reasons to use ~/.local/bin. Commented May 24, 2022 at 18:25

There really should be a per-user bin because it would be really helpful in multi user environments, where people are denied root privledges in order to make everyone more safe. Use the following in a bash script to automatically create it.

if [ ! -d "$HOME/.local/bin" ] ; then
  mkdir -p "$HOME/.local/bin"
  printf '\nexport "PATH=$PATH:'"$HOME"/.local/bin'"' >> "$HOME/.bashrc"
  # Change the PATH right now:

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .