Conventions

In this book, you will find a number of styles of text 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: "Using the auditallow statement, we can track SELinux policy decisions and assist in the development of policies and debugging of application behavior."

A block of code is set as follows:

write_files_pattern(syslogd_t, named_conf_t, named_conf_t)
allow syslogd_t named_conf_t:file setattr_file_perms;

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

policy_module(mysysadm, 0.1)
gen_require(`
  type sysadm_t;
')
logging_exec_syslog(sysadm_t)

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

~# setsebool cron_userdomain_transition on
~# grep crond_t /etc/selinux/mcs/contexts/users/user_u
system_r:crond_t user_r:user_t

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Capabilities are well explained on Chris Friedhoff's POSIX Capabilities & File POSIX Capabilities page."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.