questions:
objectives:
keypoints:
A shell is a computer program that presents a command line interface which allows you to control your computer using commands entered with a keyboard instead of controlling graphical user interfaces (GUIs) with a mouse/keyboard combination.
There are many reasons to learn about the shell:
In this lesson you will learn how to use the command line interface to move around in your file system.
On a Mac or Linux machine, you can access a shell through a program called Terminal, which is already available on your computer. If you're using Windows, you'll need to download a separate program to access the shell.
We will spend most of our time learning about the basics of the shell by manipulating some experimental data. Some of the data we're going to be working with is quite large, and we're also going to be using several bioinformatic packages in later lessons to work with this data. To avoid having to spend time downloading the data and downloading and installing all of the software, we're going to be working with data on a remote server.
You can log-in to the remote server using the instructions here. Your instructor will supply the hostname that you need to login.
After logging in, you will see a screen showing something like this:
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 6.8.0-1027-aws x86_64)
* Documentation: https://help.ubuntu.com/
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Thu Aug 21 12:34:57 UTC 2025
System load: 0.16 Processes: 109
Usage of /: 86.2% of 28.89GB Users logged in: 0
Memory usage: 7% IPv4 address for ens5: 10.0.1.94
Swap usage: 0%
=> / is using 86.2% of 28.89GB
Expanded Security Maintenance for Applications is not enabled.
2 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
9 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
*** System restart required ***
Last login: Fri Aug 8 22:34:53 2019 from 3.70.236.93
This provides a lot of information about the remote server that you're logging in to. We're not going to use most of this information for our workshop, so you can clear your screen using the clear command.
$ clear
This will scroll your screen down to give you a fresh screen and will make it easier to read. You haven't lost any of the information on your screen. If you scroll up, you can see everything that has been output to your screen up until this point.
All Bioinformatics software that will be used during this course is all ready installed but we need tell the system where they are by activating the environment.
$ conda activate metagenomics
The part of the operating system responsible for managing files and directories is called the file system. It organizes our data into files, which hold information, and directories (also called "folders"), which hold files or other directories.
Several commands are frequently used to create, inspect, rename, and delete files and directories.
Preparation Magic
If you type the command: PS1='$ ' into your shell, followed by pressing the Enter key, your window should look like our example in this lesson.
This isn't necessary to follow along (in fact, your prompt may have other helpful information you want to know about). This is up to you!
$
The dollar sign is a prompt, which shows us that the shell is waiting for input; your shell may use a different character as a prompt and may add information before the prompt. When typing commands, either from these lessons or from other sources, do not type the prompt, only the commands that follow it.
Let's find out where we are by running a command called pwd (which stands for "print working directory"). At any moment, our current working directory is our current default directory, i.e., the directory that the computer assumes we want to run commands in, unless we explicitly specify something else. Here, the computer's response is /home/user, which is the top level directory within our cloud system:
$ pwd
/home/user
Let's look at how our file system is organized. We can see what files and subdirectories are in this directory by running ls, which stands for "listing":
$ ls
Analyses Support_files databases miniforge shell_data
ls prints the names of the files and directories in the current directory in alphabetical order, arranged neatly into columns. We'll be working within the shell_data subdirectory, and creating new subdirectories, throughout this workshop.
The command to change locations in our file system is cd, followed by a directory name to change our working directory. cd stands for "change directory".
Let's say we want to navigate to the shell_data directory we saw above. We can use the following command to get there:
$ cd shell_data
Let's look at what is in this directory:
$ ls
sra_metadata untrimmed_fastq
We can make the ls output more comprehensible by using the flag -F, which tells ls to add a trailing / to the names of directories:
$ ls -F
sra_metadata/ untrimmed_fastq/
Anything with a "/" after it is a directory. Things with a "*" after them are programs. If there are no decorations, it's a file.
ls has lots of other options. To find out what they are, we can type:
$ man ls
Some manual files are very long. You can scroll through the file using your keyboard's down arrow or use the Space key to go forward one page and the b key to go backwards one page. When you are done reading, hit q to quit.
Challenge
Use the -l option for the ls command to display more information for each item in the directory. What is one piece of additional information this long format gives you that you don't see with the bare ls command?
Solution
$ ls -ltotal 8 drwxr-x--- 2 user user 4096 Jul 30 2015 sra_metadata drwxr-xr-x 2 user user 4096 Nov 15 2017 untrimmed_fastqThe additional information given includes the name of the owner of the file, when the file was last modified, and whether the current user has permission to read and write to the file.
No one can possibly learn all of these arguments, that's what the manual page is for. You can (and should) refer to the manual page or other help files as needed.
Let's go into the untrimmed_fastq directory and see what is in there.
$ cd untrimmed_fastq
$ ls -F
SRR097977.fastq SRR098026.fastq
This directory contains two files with .fastq extensions. FASTQ is a format for storing information about sequencing reads and their quality. We will be learning more about FASTQ files in a later lesson.
Typing out file or directory names can waste a lot of time and it's easy to make typing mistakes. Instead we can use tab complete as a shortcut. When you start typing out the name of a directory or file, then hit the Tab key, the shell will try to fill in the rest of the directory or file name.
Return to your home directory:
$ cd
then enter:
$ cd she<tab>
The shell will fill in the rest of the directory name for shell_data.
Now change directories to untrimmed_fastq in shell_data
$ cd shell_data
$ cd untrimmed_fastq
Using tab complete can be very helpful. However, it will only autocomplete a file or directory name if you've typed enough characters to provide a unique identifier for the file or directory you are trying to access.
If we navigate back to our untrimmed_fastq directory and try to access one of our sample files:
$ cd
$ cd shell_data
$ cd untrimmed_fastq
$ ls SR<tab>
The shell auto-completes your command to SRR09, because all file names in the directory begin with this prefix. When you hit Tab again, the shell will list the possible choices.
$ ls SRR09<tab><tab>
SRR097977.fastq SRR098026.fastq
Tab completion can also fill in the names of programs, which can be useful if you remember the beginning of a program name.
$ pw<tab><tab>
pwck pwconv pwd pwdx pwunconv
Displays the name of every program that starts with pw.
We now know how to move around our file system using the command line. This gives us an advantage over interacting with the file system through a GUI as it allows us to work on a remote server, carry out the same set of operations on a large number of files quickly, and opens up many opportunities for using bioinformatic software that is only available in command line versions.
In the next few episodes, we'll be expanding on these skills and seeing how using the command line shell enables us to make our workflow more efficient and reproducible.