Conventions Used in this Book

Typing Conventions

In order to clearly differentiate special words from the text flow, we use different renderings. The following table shows examples of each special word or group of words with its actual rendering, as well as its signification.

 

 

Formatted ExampleMeaning
inodeUsed to stress a technical term.
ls -ltaUsed for commands and their arguments. Also used for options and file names (see the section about the section called “Commands Synopsis”).
ls(1)Reference to a man page. To read the page in a shell (or command line), simply type man 1 ls.
$ ls *.pid
Formatting employed for text snapshots of what you may see on your screen including computer interactions, program listings, etc.
localhostLiteral data which does not generally fit in any of the previously defined categories. For example, a key word taken from a configuration file.
ApacheDefines application names. The example used (“Apache”) is not a command name. However, in some contexts, the application and command name may be the same but formatted differently.
F ilesIndicates menu entries or graphical interface labels. The underlined letter informs you of a keyboard shortcut, if applicable.
SCSI-BusDenotes a computer part or a computer itself.
Le petit chaperon rougeIdentifies foreign language words.
Warning!Reserved for special warnings in order to stress the importance of words. Read out loud :-)

Note

Highlights a note. Generally, it is a remark which gives additional information about a specific context.

Tip

Represents a tip. It can be a general advice on how to perform a particular action, or a nice feature which could make your life easier.

Warning

Be very careful when you see this icon. It always means that very important information about a specific subject will be dealt with.

General Conventions

Commands Synopsis

The example below shows the symbols you will see when the writer describes the arguments of a command:

command <non literal argument> [--option={arg1,arg2,arg3}] 
[optional arg. ...]

These conventions are standard and you may find them elsewhere such as in the man pages.

The “<” (less than) and “>” (greater than) symbols denote a mandatory argument not to be copied verbatim, which should be replaced according to your needs. For example, <filename> refers to the actual name of a file. If this name is foo.txt, you should type foo.txt, not <foo.txt> or <filename>.

The square brackets (“[ ]”) denote optional arguments, which you may or may not include in the command.

The ellipsis (“...”) means an arbitrary number of items can be included.

The curly brackets (“{ }”) contain the arguments authorized at this specific place. One of them is to be placed here.

Special Notations

From time to time, you will be asked to press, for example, the keys Ctrl+R, which means you need to press and hold the Ctrl key and tap the R character as well. The same applies for the Alt and Shift keys.

Also about menus, going to menu item File->Reload user config (Ctrl+R) means: click on the File text displayed on the menu (generally located in the upper-left of the window). Then in the pull-down menu, click on the Reload user config item. Furthermore you are informed that you can use the Ctrl+R key combination (as described above) to get the same result.

System-Generic Users

Whenever possible, we use two generic users in our examples:

Queen PingusaThis user is created at installation time.
Peter PingusThis user is created afterwards by the system administrator.