paint-brush
[Review] bash_profile vs bashrc vs /bin/bash vs etc/bashby@peterchang_82818
1,860 reads
1,860 reads

[Review] bash_profile vs bashrc vs /bin/bash vs etc/bash

by November 13th, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

I believe that every developers has seen that <code class="markup--code markup--p-code"><em>$ xxx command not found</em></code>, and we all found solution by <code class="markup--code markup--p-code">$ source ~/.profile&nbsp;</code>, or $ source <code class="markup--code markup--p-code">~/.bash_profile, </code>this is a note to make things clear of those file.
featured image - [Review] bash_profile vs bashrc vs /bin/bash vs etc/bash
 HackerNoon profile picture

I believe that every developers has seen that _$ xxx command not found_, and we all found solution by $ source ~/.profile , or $ source ~/.bash_profile, this is a note to make things clear of those file.

  • .profile is for things that are not specifically related to Bash, like environment variables PATH and friends, and should be available anytime. For example, .profile should also be loaded when starting a graphical desktop session.
  • .bashrc is for the configuring the interactive Bash usage, like Bash aliases, setting your favorite editor, setting the Bash prompt, etc.
  • .bash_profile is for making sure that both the things in .profile and .bashrc are loaded for login shells. For example, .bash_profile could be something simple like


. ~/.profile. ~/.bashrc

Reference:

http://stefaanlippens.net/bashrc_and_others/

https://stackoverflow.com/questions/18791486/differences-uses-and-similarities-between-bashrc-bash-profile-and-etc-profil