13
distribution in use. The /etc/inittab file is the configuration file for init in the SysV startup system, but
it doesn’t hold symbolic links, so option A is incorrect. The /etc/init directory holds Upstart scripts on
Upstart-based systems, not SysV startup scripts or links to them, so option B is incorrect.
10.
A. The chkconfig command displays information on or modifies the status of services started by
SysV startup scripts. The --list option displays the status of a service by the specified name, so
option A does as the question asks. The info command is a system documentation
tool; option B displays the info page, if it’s
present,
for the waiter command, which is not what the
question asks. Option C displays process information on any processes called waiter or that include the
string waiter in the command line. This won’t reveal in what runlevels these processes run, so option C is
incorrect. The runlevel command displays the current and previous runlevel, but it won’t tell you in
which runlevels a particular program runs, so option D is incorrect.
11.
B, C, D. Runlevels 2, 3, and 5 are all reasonable default runlevels, because
they all correspond to working multi-user modes. Debian and related distributions generally use runlevel 2
as a default, and runlevels 3 and 5 are generally used as defaults without
and
with
X running, respectively,
on Red Hat and related distributions. Runlevel 0 is not a reasonable default, since runlevel 0 corresponds to
system shutdown; if you set it as the default, the system will shut down as soon as it boots. Thus, option A is
not correct.
12.
D. The update-rc.d utility affects the runlevels in which services run. It takes a service name, an
action, and a runlevel or list of runlevels as arguments. Thus,
enable is a service name, albeit a confusing
one, and disable is a command to disable the service. This command is applied to runlevels 2 and 3.
Option D describes this effect, and the remaining options do not.
13.
C. Source code that’s compiled locally is traditionally extracted to
/usr/src
,
into
a subdirectory named after the package to be installed. Thus, option C is correct, although there’s no
guarantee that the relevant directory will be found—it’s possible the previous administrator deleted the
files or used a non-standard location to compile them. Option A describes a
temporary holding location for source tarballs on a Gentoo Linux system, but it’s not a likely location for
a source directory on a Fedora system, so this option is incorrect. The /var/lib/rpm directory is used by
RPM to store its package database and related files, but it’s not a likely location for an administrator
to extract source code for local compilation, so option B is incorrect. Binaries that are
distributed in tarball form are sometimes installed in /opt, but this isn’t a standard location for source code,
so option D is incorrect.
14.
D. Many programs have an uninstall target to make, meaning that if you do
as
option
D suggests, the
software will be uninstalled. This action isn’t guaranteed
to
work,
but it is a common approach, as the
question suggests. Option A is incorrect because it will delete any other unrelated binaries, it will miss
any non-binary files
(such
as
man pages), and it might not even uninstall the binary, if it was installed in
a
non-standard
location. Option B will delete the source code directory, but unless the program was run
directly from that location (an unusual configuration), it won’t delete the installed binary program, so this
option is incorrect. Option C is incorrect because it’s a way to uninstall a package installed via the RPM
Package Manager (RPM), not from a source tarball.
15.
C. Tarballs are files archived with tar and, frequently, compressed with gzip or bzip2. They
usually have filenames that end in .tgz, .tar.gz, .tbz, .tbz2, or .tar.bz2. Only option C describes such
a file. Although the filename doesn’t contain a hint that it contains source code, this is not uncommon for
Unix and Linux source tarballs. Option A’s .pkg filename extension identifies it as a probable Mac OS X
binary package file, not a source tarball, so option A is incorrect. A .zip filename extension
identifies a PkZip archive. Although such files are comparable to tarballs in features,
they aren’t technically tarballs. These files are more commonly used in the Windows world,
so it’s likely that option B contains a Windows binary. Even if it contains source code, its non-tarball
nature means that this option is incorrect. Option D takes the form for a source RPM file. Although such
files contain source code, they aren’t source tarballs, as the question specifies, so option D is incorrect.