Posted By: Anonymous
I’m trying to add a directory to my path so it will always be in my Linux path. I’ve tried:
This works, however each time I exit the terminal and start a new terminal instance, this path is lost, and I need to run the export command again.
How can I do it so this will be set permanently?
There are multiple ways to do it. The actual solution depends on the purpose.
The variable values are usually stored in either a list of assignments or a shell script that is run at the start of the system or user session. In case of the shell script you must use a specific shell syntax and
/etc/environmentList of unique assignments, allows references. Perfect for adding system-wide directories like
PATHvariable or defining
JAVA_HOME. Used by PAM and SystemD.
/etc/environment.d/*.confList of unique assignments, allows references. Perfect for adding system-wide directories like
PATHvariable or defining
JAVA_HOME. The configuration can be split into multiple files, usually one per each tool (Java, Go, NodeJS). Used by SystemD that by design do not pass those values to user login shells.
/etc/xprofileShell script executed while starting X Window System session. This is run for every user that logs into X Window System. It is a good choice for
PATHentries that are valid for every user like
/usr/local/something/bin. The file is included by other script so use POSIX shell syntax not the syntax of your user shell.
/etc/profile.d/*Shell script. This is a good choice for shell-only systems. Those files are read only by shells in login mode.
/etc/<shell>.<shell>rc. Shell script. This is a poor choice because it is single shell specific. Used in non-login mode.
~/.pam_environment. List of unique assignments, no references allowed. Loaded by PAM at the start of every user session irrelevant if it is an X Window System session or shell. You cannot reference other variables including
PATHso it has limited use. Used by PAM.
~/.xprofileShell script. This is executed when the user logs into X Window System system. The variables defined here are visible to every X application. Perfect choice for extending
PATHwith values such as
~/go/binor defining user specific
NPM_HOME. The file is included by other script so use POSIX shell syntax not the syntax of your user shell. Your graphical text editor or IDE started by shortcut will see those values.
~/.<shell>_loginShell script. It will be visible only for programs started from terminal or terminal emulator. It is a good choice for shell-only systems. Used by shells in login mode.
~/.<shell>rc. Shell script. This is a poor choice because it is single shell specific. Used by shells in non-login mode.
Gnome on Wayland starts user login shell to get the environment. It effectively uses login shell configurations