What is the difference between ~ . profile and ~ . bash_profile? The profile was the original profile configuration for the Bourne shell (a k a , sh) bash, being a Bourne compatible shell will read and use it The bash_profile on the other hand is only read by bash It is intended for commands that are incompatible with the standard Bourne shell
Setting PATH vs. exporting PATH in ~ . bash_profile [duplicate] Any of the ENV files first invoked by a shell such as bashrc or profile will set variable values for the life of that shell So any variables that are set and export ed within those files will maintain that export characteristic and be export ed to all child processes invoked by that shell for the life of the shell or until they are unset
What do the scripts in etc profile. d do? - Unix Linux Stack Exchange @AvindraGoolcharan Different distros may use different schemes for this kind of thing The profile d directory only works because its contents are sourced by etc profile, which is specified by shells such as bash as a startup file (see INVOCATION in man bash); if you edit etc profile, you can disable etc profile d
How to permanently set environmental variables To do if for all users shells, depending on distro you could use etc environment or etc profile Creating a new file in etc profile d may be preferable if it exists, as it will be less likely to conflict with updates made by the packaging system
bash - How to correctly add a path to PATH? - Unix Linux Stack Exchange The profile file is read by login shells, so it will only take effect the next time you log in (Some systems configure terminals to read a login shell; in that case you can start a new terminal window, but the setting will take effect only for programs started via a terminal, and how to set PATH for all programs depends on the system )
path - How do I set a user environment variable? (permanently, not . . . Note: If either of these files exists and your login shell is bash, profile is not read when you log in over ssh or on a text console, but it might still be read instead of bash_profile if you log in from the GUI Also, if there is no bash_profile, then use bashrc If you've set zsh as your login shell, use ~ zprofile instead of ~ profile
New tmux sessions do not source bashrc file This is related to the Bash init files By default, ~ bashrc is used in an interactive, non-login shell It won't be sourced in a login shell
Calendar