To get the most out of this book

The only requirement of this book is basically any computer that works!

If you are using the digital version of this book, we advise you to type the commands and scripts yourself. Doing so will help you avoid any potential errors related to the copying and pasting of commands and scripts.

I am a big believer of the “practice makes perfect” principle. The more you practice with Linux, the more you will get comfortable with it. You can install Linux as your main OS on your computer; this way you get to work with Linux on a daily basis. If that's not an option for you, then why not get a cheap Raspberry Pi and start playing around with it?

Download the color images

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: http://www.packtpub.com/sites/default/files/downloads/9781800566002_ColorImages.pdf.

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "The exit and cd commands are two examples of a shell builtin command."

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

[default]
exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)

Any command-line input or output is written as follows:

$ mkdir css
$ cd css

Bold: Indicates a new term, an important word, or words that you see onscreen. Here is an example: "The File Name is a part of the inode data structure."