In iistn, the user configuration script can be used to create an independent user Development Environment configuration script in the $ HOME directory of the user in Linux. The script is automatically loaded and executed when the user logs on to the system. Recently I have been working on the ipvtn 12.10 server and created my own under the $ HOME directory. the bashrc environment configuration script is not automatically loaded every time the login system is installed. I didn't care about it at first. After logging in, configure it manually in the source. Today, I had a dream about this problem and thought it was not appropriate. By the way, I solved this small problem. The possible names of the user configuration script are :. bashrc. bash_profile. profile, because in addition to ipvtn, the Fedora system has been used, so these files have been used and mixed together. It is not clear what their differences are (it is estimated that there is no difference, it is also a different release version of Linux ...). When searching online, some. bash_profile contents call the corresponding. bashrc: 1 #! /Bin/bash2if [-f ~ /. Bashrc]; 3then4 .~ /. Bashrc5fi, however, I used a simpler method to directly create one. bash_profile. bashrc soft connection: 1 $ ln-s. bashrc. bash_profile and then logout, and then login tests again. This time, the system automatically loads and executes the configuration script to solve the problem. If it still does not automatically load, it is possible that your system and login shell are using. profile script to create a soft link: 1 $ ln-s. bashrc. profile should be OK, because the Internet says :. bashrc is loaded when bash shell is logged on, while. profile cannot be used with the logon shell. But I did not verify this.