Linux/Unix: Environment Configuration – Profile Scripts & I/O Streams Explained

Introduction – Control the Shell Environment Like a Pro

Every time you log in or run a shell in Linux/Unix, your environment is automatically configured behind the scenes using profile scripts and I/O stream redirection. These two features are essential for creating efficient, repeatable, and personalized shell sessions.

In this guide, you’ll learn:

• What profile scripts like .bashrc and /etc/profile do
• How to customize user environments
• How Linux handles input/output (stdin, stdout, stderr)
• How to redirect and pipe output effectively in shell scripting

Topics Covered

Linux/Unix: Profile Scripts – .bashrc, .profile, /etc/profile

Linux profile scripts are executed during shell session initialization. They define aliases, environment variables, PATHs, and custom functions.

Key Configuration Files

Example – .bashrc Customization

# ~/.bashrc
export EDITOR=nano
alias ll='ls -la'
PS1="\u@\h:\w$ "

• EDITOR=nano: sets default editor
• alias ll: makes ll shortcut for ls -la
• PS1: custom shell prompt

To apply changes:

source ~/.bashrc

Linux/Unix: I/O Streams – stdin, stdout, stderr

Linux programs use file descriptors for input/output:

Input Example (stdin)

read name
echo "Hello, $name!"

Waits for user input and stores it in name.

Output Redirection (stdout)

ls > files.txt

Saves output to a file instead of screen.

Error Redirection (stderr)

ls nonexisting 2> error.log

Saves the error message into error.log.

Combined Redirection

command > output.txt 2>&1

Merges both stdout and stderr into one file.

Use of tee for Output + Logging

ls | tee log.txt

Displays output on screen and writes to file.

Summary – Recap & Next Steps

Understanding profile scripts and I/O stream redirection helps you automate, debug, and customize your Linux environment. These foundational tools ensure your shell behaves exactly the way you want.

Key Takeaways:

• ~/.bashrc, .profile, and /etc/profile are used to set up the shell environment
• Use source ~/.bashrc to reload changes
• File descriptors 0, 1, 2 correspond to stdin, stdout, and stderr
• Redirect and combine outputs using >, 2>, &>, tee, and pipes

Practical Applications:

• Automate terminal setup on login
• Capture logs and errors in scripts
• Set up language/tool environments (e.g., Java, Python paths)

Frequently Asked Questions

What’s the difference between .bashrc and .profile?
.bashrc is for interactive non-login shells; .profile is for login shells. Some systems source .bashrc from .profile.

How do I reload .bashrc after editing?
Run:

source ~/.bashrc

How do I redirect both output and errors to the same file?
Use:

command > file.txt 2>&1

Where can I set environment variables permanently?
In ~/.bashrc or ~/.profile. Use export VAR=value.