|
- What is the difference between ~ . profile and ~ . bash_profile?
The original sh sourced profile on startup bash will try to source bash_profile first, but if that doesn't exist, it will source profile Note that if bash is started as sh (e g bin sh is a link to bin bash) or is started with the --posix flag, it tries to emulate sh, and only reads profile Footnotes: Actually, the first one of bash_profile, bash_login, profile See also: Bash
- bash - What is the difference between . profile and . bash_profile and . . .
The profile dates back to the original Bourne shell known as sh Since the GNU shell bash is (depending on its options) a superset of the Bourne shell, both shells can use the same startup file That is, provided that only sh commands are put in profile For example, alias is a valid built-in command of bash but unknown to sh Therefore, if you had only a profile in your home directory and
- What do the scripts in etc profile. d do? - Unix Linux Stack Exchange
It says that the etc profile file sets the environment variables at startup of the Bash shell The etc profile d directory contains other scripts that contain application-specific startup files, which are also executed at startup time by the shell
- Why might one add ~ . profile to ~ . bash_profile?
Even if you have bash as your login shell, profile is often the one that's executed when you log in in graphical mode — many distributions set up the X session startup script to run under sh and load profile Hence the advice to use profile instead of bash_profile to do things like defining environment variables
- Setting PATH vs. exporting PATH in ~ . bash_profile
What's the difference and which is better to use when customizing my bash profile? Documentation on the export command is scarce, as it's a builtin cmd Excerpt from version 1 of my ~ bash_profil
- What is the purpose of . bashrc and how does it work?
My comment is just a stronger statement of Ilmari Karonen's 2014 comment It is factually incorrect to say " bashrc runs on every interactive shell launch" A login shell is an interactive shell, and it's the counterexample: a login shell does not run bashrc It would be correct to say " bashrc is run by every interactive non-login shell" Bash Reference Manual, section 6 2, "Bash Startup FIles"
- ubuntu - AppArmor Error preventing removing AA, Repairing AA or install . . .
Issue the following: dpkg -S <offending profile> This should tell us the package the profile belongs to Use the Ubuntu Launchpad to search for the package See if there is already a bug related to your profile, or report a new one Note: If the above testing approach fails on the first profile or every profile there is something worse going on
- Why does non-interactive login bash run as -bash reads ~ . profile . . .
When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file etc profile, if that file exists
|
|
|