How to Run Your Own Linux Scripts from Any Directory by Extending PATH

On Linux, commands like ls, cd, and pwd reside in /bin but can be run from any directory because their locations are listed in the PATH environment variable. By adding your own script directory to PATH, you can achieve the same convenience for your personal scripts.

Method 1: Append the script path to .bashrc

The Bash shell reads .bashrc on startup. Add an export PATH line to this file: export PATH="/home/alvin/scripts:$PATH" After saving, apply the change with: source ~/.bashrc Now any script placed in /home/alvin/scripts (e.g., hello.sh) can be executed from any directory.

Method 2: Append the script path to .profile

.profile

is processed at login to set environment variables. Add the following line at the end of the file (or .bash_profile on some systems): export PATH="$PATH:$HOME/scripts" Log out and log back in for the change to take effect. On Ubuntu‑based distributions, modify .pam_environment instead of .profile and add:

PATH DEFAULT=${PATH}:/home/${PAM_USER}/scripts

Method 3: Edit the system-wide /etc/environment file

For a global solution, edit /etc/environment (requires sudo) and extend the existing PATH line: sudo vim /etc/environment Locate the line similar to: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin" and append your script directory:

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/alvin/scripts"

After saving, log out and back in to apply the new path.

Summary

The article presents three straightforward ways to make custom Linux scripts globally executable by adding their directory to the PATH variable: editing .bashrc, editing .profile (or .pam_environment on Ubuntu), and modifying the system-wide /etc/environment file. Each method requires reloading the shell or logging back in to take effect.