bash starts up, it reads configuration files to set up the environment. These files are known as startup files.
Startup files work by first loading the default environment shared by all users. Then it loads files in the user's home directory to give a more tailored experience per user.
There are two types of shell logins: login and non-login shell sessions. Depending on which one you choose to boot your shell, a different group of startup files are executed.
For a login shell session, a username and password in necessary.
Here is the order in which the startup files are executed in a login shell.
Non-login shells inherit the environment from their parent process.
The main difference in files being executed is that login shells run .bash_profile on startup, while non-login shells run .bashrc. However, .bashrc is usually executed from .bash_profile.
Remember that the . before a file name means that it is hidden. To view hidden files, use
There is a convention of where to store certain variables when configuring your environment.
In the next section, let's talk about how to properly set environment variables so that your settings are loaded upon every login.
Ever feel achy from sitting crunched up on your computer table? Try lying down with these optical glasses that allow you to work on your laptop while lying flat on your back. This is the perfect solution with those with limited mobility or those who wish to prevent neck cramps and back strains.$ Check price
This book approaches system administration in a practical way and is an invaluable reference for both new administrators and experienced professionals. It details best practices for every facet of system administration, including storage management, network design and administration, email, web hosting, scripting, and much more.$ Check price