Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "MySQL and MariaDB create their log files in the /var/log/mysql directory."

A block of code is set as follows:

subnet 192.168.1.0 netmask 255.255.255.0 {
       range 192.168.1.100 192.168.1.240; 
       option routers 192.168.1.1; 
       option domain-name-servers 192.168.1.1;

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

[Documents]  
        path = /share/documents
        force user = myuser
        force group = users
        public = yes
        writable = no

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Clicking the Next button moves you to the next screen."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Any command line input or output is written as follows:

dpkg --get-selections > installed_packages.txt

Some commands need to be executed as the root user or with sudo. I'll mark these commands with the hash symbol (#) such as in the following example:

# apt-get install openssh-server

If you don't see a hash symbol preceding a command, then sudo or root privileges aren't necessary for you to run it. But if you do see this symbol, take note that you'll need root privileges. I won't always remind you of this beforehand. In most cases, it usually doesn't matter if you use sudo or switch to the root user, I'll leave that up to you. But if it does matter in a particular example, I will let you know.