Before you begin, you need to have some basic knowledge of how Linux works. That is to say, you need to know what a desktop environment is, or how to work with a package manager. You also need to know how to troubleshoot basic errors. Knowing the very basics of what a for loop is, or what Switch–Case is, would help you learn faster.

Also, if you are new to PowerShell, reading the first chapter is recommended. This chapter contains a couple of important guidelines for working efficiently with PowerShell.

The book also assumes that you are working on either Ubuntu or CentOS. While PowerShell constructs themselves do not behave differently with different Linux flavors (or even different platforms), the installation—and sometimes the configuration—may be different on different flavors of Linux.

You can download the example code files for this book from your account at www.packt.com. If you purchased this book elsewhere, you can visit www.packt.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packt.com.
2. Select the SUPPORT tab.
3. Click on Code Downloads & Errata.
4. Enter the name of the book in the Search box and follow the on-screen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/PowerShell-Core-Linux-Administrators-Cookbook. In case there is an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalogue of books and videos available at https://github.com/PacktPublishing/. Check them out!

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

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, path names, dummy URLs, user input, and Twitter handles. Here is an example: "Create a file called simply script.ps1."

A block of code is set as follows:

Get-Date
hostname
Write-Output "Hello, $env:username!"

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

$Date = Get-Date
if ($Date.DayOfWeek -in 'Saturday', 'Sunday') {
    Write-Host 'It is a weekend!'
}
else {
    Write-Host 'It is a weekday.'
}

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

PS> Get-Process dconf-editor
PS> Stop-Process -Id 20608

Bold: Indicates a new term, an important word, or words that you see on screen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Click the Cloud Shell icon in the top navigation bar of the Azure portal; select either Bash or PowerShell."