Navigating and manipulating files and folders in the filesystem is a key part of working with most computers. Cloud servers mostly use the same common Linux shells, and common Linux commands, for working with files and folders. This terminal will introduce some fundamental skills for using these commands.
In order to follow along with this guide, you will need to have access to a Linux server. If you need information about connecting to your server for the first time, you can follow our guide on connecting to a Linux server using SSH.
You will also want to have an understanding of how the terminal works and what Linux commands look like. This guide covers an introduction to the terminal.
All of the material in this guide can be accomplished with a regular, non-root (non-administrative) user account. You can learn how to configure this type of user account by following your distribution’s initial server setup guide, such as for Ubuntu 22.04.
When you are ready to begin, connect to your Linux server using SSH and continue below.
The most fundamental skills you need to master are moving around the filesystem and getting an idea of what is around you. You will review the tools that allow you to do this in this section.
When you log into your server, you are typically dropped into your user account’s home directory. A home directory is a directory set aside for your user to store files and create directories. It is the location in the filesystem where you have full dominion.
To find out where your home directory is in relation to the rest of the filesystem, you can use the
pwd command. This command displays the directory that you are currently in:
The home directory is named after the user account. This directory is within a directory called
/home, which is itself within the top-level directory, which is usually called the “root” directory, and is represented by a single slash
Now that you know how to display the directory that you are in, you can look at the contents of a directory.
Currently, your home directory does not have much to look at, so you can go to another, more populated directory to explore. Use
cd to move to this directory. Afterward, you’ll use
pwd to confirm that you successfully moved:
- cd /usr/share
Now that you are in a new directory, let’s look at what’s inside. To do this, you can use the
Outputadduser groff pam-configs applications grub perl apport grub-gfxpayload-lists perl5 apps hal pixmaps apt i18n pkgconfig aptitude icons polkit-1 apt-xapian-index info popularity-contest . . .
As you can see, there are many items in this directory. You can add some optional flags to the command to modify the default behavior. For instance, to list all of the contents in an extended form, you can use the
-l flag (for “long” output):
- ls -l
Outputtotal 440 drwxr-xr-x 2 root root 4096 Apr 17 2022 adduser drwxr-xr-x 2 root root 4096 Sep 24 19:11 applications drwxr-xr-x 6 root root 4096 Oct 9 18:16 apport drwxr-xr-x 3 root root 4096 Apr 17 2022 apps drwxr-xr-x 2 root root 4096 Oct 9 18:15 apt drwxr-xr-x 2 root root 4096 Apr 17 2022 aptitude drwxr-xr-x 4 root root 4096 Apr 17 2022 apt-xapian-index drwxr-xr-x 2 root root 4096 Apr 17 2022 awk . . .
This view gives us plenty of information. The first block describes the file type (if the first column is a “d” the item is a directory, and if it is a “-”, it is a normal file) and permissions. Each subsequent column, in order, describes the number of hard links to that file elsewhere on the system, the owner, group owner, item size, last modification time, and the name of the item.
To get a listing of all files, including hidden files and directories, you can add the
-a flag. Since there are no real hidden files in the
/usr/share directory, let’s go back to your home directory and try that command. You can get back to the home directory by typing
cd with no arguments:
- ls -a
Output. .. .bash_logout .bashrc .profile
As you can see, there are three hidden files, along with
.., which are special indicators. You will find that often, configuration files are stored as hidden files, as is the case here.
For the dot and double dot entries, these aren’t exactly directories as much as built-in methods of referring to related directories. The single dot indicates the current directory, and the double dot indicates this directory’s parent directory. This will come in handy in the next section.
You have already made two directory moves in order to demonstrate some properties of
ls in the last section. Let’s take a better look at the command here.
Begin by going back to the
- cd /usr/share
This is an example of changing a directory by providing an absolute path. In Linux, every file and directory is under the top-most directory, which is called the “root” directory, but referred to by a single leading slash “/”. An absolute path indicates the location of a directory in relation to this top-level directory. This lets us refer to directories in an unambiguous way from any place in the filesystem. Every absolute path must begin with that slash.
The alternative is to use relative paths. Relative paths refer to directories in relation to the current directory. For directories close to the current directory in the hierarchy, this is usually shorter, and it is sometimes beneficial to not need to make assumptions about where a directory is located in the broader filesystem. Any directory within the current directory can be referenced by name without a leading slash. You can change to the
locale directory within
/usr/share from your current location by typing:
- cd locale
You can also move multiple directory levels with relative paths by providing the portion of the path that comes after the current directory’s path. From here, you can get to the
LC_MESSAGES directory within the
en directory by typing:
- cd en/LC_MESSAGES
To go back up, traveling to the parent of the current directory, you can use the special double dot indicator. For instance, you are now in the
/usr/share/locale/en/LC_MESSAGES directory. To move up one level, you can type:
- cd ..
This takes us to the
You can always return to your home directory by running
cd without specifying a directory. You can also use
~ in place of your home directory in any other commands:
cd ~ pwd
To learn more about how to use these three commands, you can check out our guide on exploring the Linux filesystem.
In the last section, you learned how to navigate the filesystem. You probably saw some files when using the
ls command in various directories. In contrast to some operating systems, Linux and other Unix-like operating systems rely on plain text files for vast portions of the system.
The main way that you will view files in this tutorial is with the
less command. This is what is called a “pager”, because it allows you to scroll through pages of a file. While the previous commands immediately executed and returned you to the command line,
less is an application that will continue to run and occupy the screen until you exit.
You will open the
/etc/services file, which is a configuration file that contains service information that the system knows about:
- less /etc/services
The file will be opened in
less, allowing you to see the portion of the document that fits in the area of the terminal window:
Output# Network services, Internet style # # Note that it is presently the policy of IANA to assign a single well-known # port number for both TCP and UDP; hence, officially ports have two entries # even if the protocol doesn't support UDP operations. # # Updated from http://www.iana.org/assignments/port-numbers and other # sources like http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/services . # New ports will be added on request if they have been officially assigned # by IANA and used in the real-world or are needed by a debian package. # If you need a huge list of used numbers please install the nmap package. tcpmux 1/tcp # TCP port service multiplexer echo 7/tcp . . .
To scroll, you can use the up and down arrow keys on your keyboard. To page down, you can use either the space bar, the “Page Down” button on your keyboard, or the
To scroll back up, you can use either the “Page Up” button, or the
CTRL-b keyboard shortcut.
To search for some text in the document, you can type a forward slash “/” followed by the search term. For instance, to search for “mail”, you would type:
This will search forward through the document and stop at the first result. To get to another result, you can type the lower-case
To move backwards to the previous result, use a capital
To exit the
less program, you can type
q to quit:
There are many other ways of viewing a file that come in handy in certain circumstances. The
cat command outputs a file’s contents and returns you to the prompt immediately. The
head command, by default, shows the first 10 lines of a file. Likewise, the
tail command shows the last 10 lines. These commands display file contents in a way that is useful for “piping” to other programs. This concept is covered later in this tutorial series.
In this section, you’ll create and manipulate files and directories.
Many commands and programs can create files. The most straightforward method of creating a file is with the
touch command. This will create an empty file using the name and location specified.
First, make sure you are in your home directory, since this is a location where you have permission to save files. Then, you can create a file called
file1 by typing:
- touch file1
Now, if you view the files in the directory, you can see your newly created file:
If you use the
touch command on an existing file, it updates the “last modified” time associated with that file. This can be helpful to keep in mind.
You can also create multiple files at the same time. You can use absolute paths as well. For instance, you could type:
- touch /home/sammy/file2 /home/sammy/file3
Outputfile1 file2 file3
Similar to the
touch command, the
mkdir command allows you to create empty directories.
For instance, to create a directory within your home directory called
test, you could type:
- mkdir test
You can make a directory within the
test directory called
example by typing:
- mkdir test/example
For the above command to work, the
test directory must already exist. To tell
mkdir that it should create any directories necessary to construct a given directory path, you can use the
-p option. This allows you to create nested directories in one step. You can create a directory structure that looks like
some/other/directories by typing:
- mkdir -p some/other/directories
The command will make the
some directory first, then it will create the
other directory inside of that. Finally it will create the
directories directory within those two directories.
You can move a file to a new location using the
mv command. For instance, you can move
file1 into the
test directory by typing:
- mv file1 test
You can move that file back to your home directory by using the special dot reference to refer to the current directory. Make sure you’re in your home directory, and then run the
- mv test/file1 .
mv command is also used to rename files and directories. In essence, moving and renaming are both just adjusting the location and name for an existing item.
So to rename the
test directory to
testing, you could type:
- mv test testing
Note: The shell will not prevent you from making accidentally destructive actions. If you are renaming a file and choose a name that already exists, the previous file will be overwritten by the file you are moving. There is no way to recover the previous file if you accidentally overwrite it.
mv command, you could move or rename a file or directory, but you could not duplicate it. The
cp command can make a new copy of an existing item.
For instance, you can copy
file3 to a new file called
- cp file3 file4
mv operation, after which
file3 would no longer exist, you now have both
Note: As with the
mv command, it is possible to overwrite a file if you are not careful about the filename you are using as the target of the operation. For instance, if
file4 already existed in the above example, its content would be completely replaced by the content of
In order to copy entire directories, you must include the
-r option to the command. This stands for “recursive”, as it copies the directory, plus all of the directory’s contents.
For instance, to copy the
some directory structure to a new structure called
again, you could type:
- cp -r some again
Unlike with files, with which an existing destination would lead to an overwrite, if the target is an existing directory, the file or directory is copied into the target:
- cp file1 again
This will create a new copy of
file1 and place it inside of the
To delete a file, you can use the
Note: Be extremely careful when using any destructive command like
rm. There is no “undo” command in the shell, so it is possible to accidentally destroy important files permanently.
To remove a regular file, just pass it to the
- rm file4
Likewise, to remove empty directories, you can use the
rmdir command. This will only succeed if there is nothing in the directory in question. For instance, to remove the
example directory within the
- rmdir testing/example
To remove a non-empty directory, you will use the
rm command with the
-r option, which removes all of the directory’s contents recursively, plus the directory itself.
For instance, to remove the
again directory and everything within it, you can type:
- rm -r again
Currently, you know how to manipulate files as objects, but you have not learned how to actually edit them and add content to them.
nano is one of a few common command-line Linux text editors, and is a great starting point for beginners. It operates somewhat similarly to the
less program discussed above, in that it occupies the entire terminal for the duration of its use.
nano editor can open existing files, or create a file. If you decide to create a new file, you can give it a name when you call the
nano editor, or later on, when you save your content.
You can open the
file1 file for editing by typing:
- nano file1
nano application will open the file (which is currently blank). The interface looks something like this:
GNU nano 4.8 file1 [ New File ] ^G Get Help ^O WriteOut ^R Read File ^Y Prev Page ^K Cut Text ^C Cur Pos ^X Exit ^J Justify ^W Where Is ^V Next Page ^U UnCut Text ^T To Spell
Along the top, you have the name of the application and the name of the file you are editing. In the middle, the content of the file, currently blank, is displayed. Along the bottom, you have a number of key combinations that indicate some controls for the editor. For each of these, the
^ character means the
To get help from within the editor, press
When you are finished browsing the help, type
Ctrl+X to get back to your document.
For this example, you can just type these two sentences:
Hello there. Here is some text.
To save your work, press
File Name to Write: file1 ^G Get Help M-D DOS Format M-A Append M-B Backup File ^C Cancel M-M Mac Format M-P Prepend
As you can see, the options at the bottom have also changed. These are contextual, meaning they will change depending on what you are trying to do. To confirm writing to
After saving, If you make additional changes and try to exit the program, you will see a similar prompt. Add a new line, and then try to exit
nano by pressing
If you have not saved, you will be asked to save the modifications you made:
Save modified buffer (ANSWERING "No" WILL DESTROY CHANGES) ? Y Yes N No ^C Cancel
You can press
Y to save your changes,
N to discard your changes and exit, or
Ctrl+C to cancel quitting. If you choose to save, you will be given the same file prompt that you received before, confirming that you want to save the changes to the same file. Press
Enter to save the file and exit the editor.
You can see the contents of the file you created using either the
cat program to display the contents, or the
less program to open the file for viewing. After viewing with
less, remember that you should press
q to get back to the terminal.
- less file1
OutputHello there. Here is some text. Another line.
Another editor that you may see referenced in certain guides is
vi. This is a more advanced editor that is very powerful, but comes with a steep learning curve. If you are ever told to use
vi, feel free to use
nano instead. To learn how to use
vim, read our guide to getting started with vim.
By now, you should have an understanding of how to get around your Linux server and how to see the files and directories available. You should also know file manipulation commands that will allow you to view, copy, move, or delete files. Finally, you should be comfortable with some editing using the
nano text editor.
With these few skills, you should be able to continue on with other guides and learn how to get the most out of your server. In our next guide, you will understand how to view and understand Linux permissions.
If you’ve enjoyed this tutorial and our broader community, consider checking out our DigitalOcean products which can also help you achieve your development goals.
If you are new to Linux and its command line interface, it may seem like a daunting task to get started with it. This series will bring you up to speed with essential Linux basics, and provide a solid foundation for working with Linux servers. If you have little to no knowledge about using Linux, this is where you will want to start.