Why environment setup customizes the shell in Linux CLI - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to display the current shell environment variable.

Linux CLI

echo $[1]

Drag options to blanks, or click blank then click option'

ASHELL

BHOME

CPATH

DUSER

Attempts:

3 left

💡 Hint

Common Mistakes

Using PATH instead of SHELL will show executable search paths, not the shell.

HOME shows your home directory, not the shell.

The SHELL variable shows which shell is currently used. This helps customize the environment.

2fill in blank

medium

Complete the command to list all environment variables including custom shell settings.

Linux CLI

printenv | grep [1]

Drag options to blanks, or click blank then click option'

APATH

BUSER

CHOME

DSHELL

Attempts:

3 left

💡 Hint

Common Mistakes

Using PATH will show many unrelated variables.

USER or HOME do not relate to shell customization.

Using grep SHELL filters environment variables related to the shell, showing customizations.

3fill in blank

hard

Fix the error in the command to set a custom prompt variable in the shell.

Linux CLI

export PS1=[1]

Drag options to blanks, or click blank then click option'

A"\u@\h:\w$ "

B'\u@\h:\w$ '

C\u@\h:\w$

D"\u@\h:\w$"

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes causes the prompt to show raw backslashes.

No quotes cause syntax errors.

The prompt variable PS1 needs double quotes to interpret escape sequences like \u and \w.

4fill in blank

hard

Fill both blanks to create an alias for listing files with details and human-readable sizes.

Linux CLI

alias ll='ls [1] [2]'

Drag options to blanks, or click blank then click option'

A-l

B-a

C-h

D-r

Attempts:

3 left

💡 Hint

Common Mistakes

Using -a shows hidden files but not size format.

Using -r reverses order, not size format.

The -l option lists files in long format, and -h shows sizes in human-readable form.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps words to their lengths only if length is greater than 3.

Linux CLI

lengths = { [1] : [2] for [3] in words if len([3]) > 3 }

Drag options to blanks, or click blank then click option'

Aword

Blen(word)

Ditem

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names causes errors.

Not using len(word) as value misses the length.

The comprehension uses word as key, len(word) as value, and iterates over word in words.

Practice

1. Why do we customize the shell environment using setup files like .bashrc or .zshrc?

easy

A. To delete all files automatically when the shell starts

B. To make the shell easier and faster to use by setting variables and shortcuts

C. To slow down the shell for security reasons

D. To prevent any commands from running in the shell

Solution

1. Step 1: Understand the purpose of shell customization

   Shell setup files like .bashrc allow users to set environment variables and aliases that make daily tasks easier and faster.

2. Step 2: Eliminate incorrect options

   Options A, B, and D describe harmful or incorrect behaviors that are not the purpose of environment setup.

3. Final Answer:

   To make the shell easier and faster to use by setting variables and shortcuts -> Option B

4. Quick Check:

   Environment setup = easier, faster shell use [OK]

Hint: Setup files speed up work by adding shortcuts and variables [OK]

Common Mistakes:

• Thinking setup slows down the shell
• Confusing setup with deleting files
• Believing setup blocks commands

2. Which of the following is the correct syntax to create an alias named ll for ls -l in your shell setup?

easy

A. alias ll='ls -l'

B. export ll='ls -l'

C. alias ll=ls -l

D. set alias ll='ls -l'

Solution

1. Step 1: Recall alias syntax

   The correct way to create an alias is using the keyword alias followed by the name, an equals sign, and the command in single quotes.

2. Step 2: Check each option

   alias ll='ls -l' matches the correct syntax. export ll='ls -l' uses export which is for variables, not aliases. alias ll=ls -l misses quotes, causing syntax errors. set alias ll='ls -l' uses an invalid command.

3. Final Answer:

   alias ll='ls -l' -> Option A

4. Quick Check:

   Alias syntax = alias name='command' [OK]

Hint: Use alias name='command' with quotes for shortcuts [OK]

Common Mistakes:

• Using export instead of alias
• Omitting quotes around the command
• Using invalid commands like set alias

3. Given the following shell commands in your setup file:

export PATH="$HOME/bin:$PATH"
alias gs='git status'

What will be the effect when you open a new shell?

medium

A. The shell will look for programs in $HOME/bin first and 'gs' runs 'git status'

B. The shell will ignore $HOME/bin and 'gs' will cause an error

C. The PATH variable will be empty and 'gs' will list files

D. The shell will crash due to syntax errors

Solution

1. Step 1: Understand PATH modification

   The command export PATH="$HOME/bin:$PATH" adds the user's bin directory at the front of the PATH, so programs there run first.

2. Step 2: Understand alias effect

   The alias gs='git status' means typing gs runs git status command.

3. Final Answer:

   The shell will look for programs in $HOME/bin first and 'gs' runs 'git status' -> Option A

4. Quick Check:

   PATH prepended + alias set = The shell will look for programs in $HOME/bin first and 'gs' runs 'git status' [OK]

Hint: PATH prepends directories; alias shortcuts commands [OK]

Common Mistakes:

• Thinking PATH ignores new directories
• Assuming alias commands cause errors
• Believing PATH resets to empty

4. You added this line to your shell setup file:

export PATH=$HOME/bin:$PATH

But after restarting the shell, your custom programs in $HOME/bin are not found. What is the likely problem?

medium

A. You forgot to export PATH

B. You used double quotes instead of single quotes

C. You did not reload the shell setup file or restart the shell

D. You assigned PATH without including the old $PATH

Solution

1. Step 1: Check the export command correctness

   The line export PATH=$HOME/bin:$PATH is correct and includes the old PATH.

2. Step 2: Consider shell reload

   Changes in setup files only take effect after restarting the shell or reloading the file with source ~/.bashrc.

3. Final Answer:

   You did not reload the shell setup file or restart the shell -> Option C

4. Quick Check:

   Reload shell after changes = You did not reload the shell setup file or restart the shell [OK]

Hint: Reload or restart shell to apply setup changes [OK]

Common Mistakes:

• Not restarting or sourcing the setup file
• Thinking export is missing when it is present
• Confusing quotes usage here

5. You want your shell prompt to show your username and current directory in green color every time you open the shell. Which setup snippet achieves this?

hard

A. set prompt='\e[32m\u:\w\e[0m'

B. alias prompt='green \u \w'

C. export PS1='\u:\w'

D. export PS1='\[\e[32m\]\u:\w\$ \[\e[0m\]'

Solution

1. Step 1: Understand PS1 and color codes

   The prompt variable PS1 controls the shell prompt. Color codes use escape sequences like \e[32m for green and \e[0m to reset color.

2. Step 2: Analyze each option

   export PS1='\[\e[32m\]\u:\w\$ \[\e[0m\]' correctly sets PS1 with green color, username (\u), current directory (\w), and resets color. alias prompt='green \u \w' uses alias incorrectly. export PS1='\u:\w' lacks color. set prompt='\e[32m\u:\w\e[0m' uses invalid syntax.

3. Final Answer:

   export PS1='\[\e[32m\]\u:\w\$ \[\e[0m\]' -> Option D

4. Quick Check:

   PS1 with color codes = export PS1='\[\e[32m\]\u:\w\$ \[\e[0m\]' [OK]

Hint: Use PS1 with \e[32m for green prompt [OK]

Common Mistakes:

• Using alias instead of PS1 for prompt
• Forgetting to reset color with \e[0m
• Incorrect escape sequences or syntax