Errata

LPI Linux Certification in a Nutshell

Errata for LPI Linux Certification in a Nutshell

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
PDF Page 25
Table 4-1, Typical runlevels

This is a suggestion, regarding the level 4 runlevel explanation. Currently it is too vague.

Current text = "4" : "Typically unused."
Suggestion = "4" : "Typically unused / User definable, for special purposes"

Tatiana Al-Chueyr  Feb 16, 2012 
PDF Page 28
Change Runlevels and Shut Down or Reboot System (Topics 101.2 and 101.3)

Again, there is a description a bit vague. I suggest you clarify it:

Current text = "If two services have an identical start order number,
the order is indeterminate but probably alphabetical."

Suggestion = "If two services have an identical start order number,
the ordering can vary.Usually alphabetic order is applied, but this
can be redefined editing the init script."

Tatiana Al-Chueyr  Feb 16, 2012 
Printed Page 80
line 10 and following

The explanation of the join command is not clear and the example does not work.

-----------------
join --version
join (GNU coreutils) 8.13
--------------------------

join -j1 file1 file2 will yield the following error:

join -j1 file1 file2
join: file1:3: is not sorted: three

Even if the file1 is sorted first, join will output nothing because the field 1 has no matching entries for both files.

S. Peters  Aug 10, 2014 
Printed Page 93
Chapter 6: GNU and Unix Commands

cp command
-f
Force an overwrite of existing files in the destination.

It is not true. Based on man page of cp command it is :
-f, --force
if an existing destination file cannot be opened, remove it
and try again

You can try below to find out :
See the difference between output of these two commands that are run by a
normal user :
cp ~/mypasswd /etc/passwd
cp: cannot create regular file `/etc/passwd': Permission denied

$ cp -f ~/mypasswd /etc/passwd
cp: cannot remove `/etc/passwd': Permission denied

In second case cp tries to open /etc/passwd for writing and since it does
not have permission so -f option tries to remove destination file first and
we see a different error than first case.

Anonymous  Dec 04, 2012 
PDF Page 99
Frequently used options of rm, lower half of page, PDF edition

"-d
Remove directories even if they are not empty. This option is reserved for privileged users."

This option does not exist for rm or rmdir in either Debian 6.0.10 or RHEL 6.x.

Both versions fail to execute the command rm -d /tmp/directory whether or not the directory is empty. Neither man page lists the option.

The -d option exists in BSD, but BSD is decidedly NOT Linux. There is no official distro statement on the LPI site, but it is generally accepted to cover the RedHat and Debian families of Linux. NOTE: This is a LINUX exam, not UNIX. BSD-only options are not part of the curriculum.

Von Hawkins  Jan 21, 2015 
PDF Page 112
second paragraph where option "-q" specified

it wrote about option "-q" which was usable in past but in new version of ؛top؛ command on linux there is no "-q" option .

ali  Jul 24, 2012 
Printed Page 117
3rd command

Single quotes are used in command instead of backticks (as indicated by the second paragraph below the command).

Written: kill -HUP 'cat /var/run/httpd.pid'

Should be: kill -HUP `cat /var/run/httpd.pid`

Anonymous  Aug 02, 2011 
Printed Page 129
Last paragraph

In Example 4 of sed it states that the command sed 's/^&/@/' file1 will replace all blank lines with @, however this will only replace the first instance. The correct command should be: sed 's/^&/@/g' file1

Kevin Nelson  Aug 11, 2011 
Printed Page 147
Example 1,2,3

Example 1
Display all lines from file1 that contain ab, abc, abcc, abccc, and so on:
$ grep 'abc*' file1 → grep 'ab*' file1

Example 2
Display all lines from file1 that contain abc, abcc, abccc, and so on, but not ab:$ grep 'abcc*' file1 → grep 'abc*' file1


Example 3
Display all lines from file1 that contain two or more adjacent digits:
$ grep '[0-9][0-9][0-9]*' file1 → grep '[09][09]*' file1

Anonymous  Aug 23, 2016 
Printed Page 190-191
Third full paragraph on 190 and/or Figure 7-3 on 191

The paragraph explains how jdoe created a symbolic link on /dev/sda9 to a file, but Figure 7-3 lists it as /dev/sdaq

David Dawson  Aug 02, 2011 
Printed Page 205
United States

In the Review questions for System Architecture #5 is What command is used to obtain USB information on a Linux system? The first thing that comes to mind is lsusb, especially considering the other commands that are being talked about within that section of the book: lspci, lsmod, insmod, etc... My guess would be that one of the original lsmods mentioned in the issue brought up by Timothy Bounds on 12 Oct 2010 was actually supposed to be lsusb.

Greg Yeomans  Oct 17, 2011 
Printed Page 247
Third line of Octal bits in the Setting access modes section.

rwxr-xr-- 111101100 = 751 is not correct.
Should read 754

Mark Rogoyski  Aug 08, 2011 
PDF Page 267
top of the page line 3

At top of page line 3 It says the command :
"$ top -Ssd1"
in this command option "s" (lower case s) means "secure mod" but you can't use option "d" to change delay time because it's on secure mod . this is not work even if you run it from root privilege .
In interactive mod of top it says :
"Unavailable in secure mode "
in normal mod it says :
" *** Delay time Not changed *** "

alieblice  Sep 15, 2012 
PDF Page 293
2nd paragraph

The text says "Let’s sort our families by the father’s date of birth, from youngest to oldest." but I think it should be "from oldest to youngest."

Saber Yari  Jun 27, 2016 
Printed Page 373
Figure 19-1

The second field of the binary address for Network Address 192.168.1.0 reads 10101011. It should read 10101000.

Andrew Eddy  Feb 24, 2014 
PDF Page 409
2nd paragraph

Initially, the fdisk command by itself did not work because it was not in the $PATH variable. Once the user returned to her user shell and used su to become root, the $PATH environment variable then contained the /sbin and /usr/sbin directories, so fdisk was found.

Should be something like:

Initially, the fdisk command by itself did not work because it was not in the $PATH variable. If the user used "su" to become root, fdisk command will still not work because $PATH
variable did not change to include the /sbin and /usr/sbin directories. Once the user returned to their user shell and used "su -" to become root, the $PATH environment variable then contained the /sbin and /usr/sbin directories, so fdisk was found.

Anonymous  Sep 02, 2012 
PDF Page 416
2nd paragraph

We can see from this file that the root account has a password, the password was last changed 14,617 days after January 1, 1970, this user can change her password at any time, she does not have to change her password until 99,999 days after January 1, 1970, and if her password is ever set to expire, she will start getting notices 7 days before the actual expiration.

remove " days after January 1, 1970,"
should be something like:

We can see from this file that the root account has a password, the password was last changed 14,617 days after January 1, 1970, this user can change his/her password at any time, he/she does not have to change her password, and if her password is ever set to expire, she will start getting notices 7 days before the actual expiration.

Anonymous  Sep 02, 2012 
PDF Page 416
ssh-keygen description and example

The -b option sets the number of bits in the keys: 512 is the minimum, and 1024 bits is the default.

$ ssh-keygen -t dsa -b 2048
Generating public/private dsa key pair. Enter file in which to save the key

as per ssh-keygen man page:

-b bits
Specifies the number of bits in the key to create. For RSA keys, the minimum size is 768 bits and the default is 2048 bits. Generally, 2048 bits is considered sufficient. DSA keys must be exactly 1024 bits as specified by FIPS 186-2.

in testing:
$ ssh-keygen -t dsa -b 2048
DSA keys must be 1024 bits

$ ssh-keygen -t rsa -b 767
Bits has bad value 767 (too small)

$ ssh-keygen -t rsa1 -b 767
Bits has bad value 767 (too small)

Anonymous  Sep 03, 2012 
PDF Page 427
1st Paragraph

This scan took a little bit longer, but it showed us an additional three open TCP ports that the default scan did not show.

There were only two additional open ports.

Anonymous  Sep 02, 2012 
Printed Page 446
1st Paragraph, 2nd sub-paragraph

The path/filename for the public key is shown as ~/.id_rsa.pub. It should be ~/.ssh/.id_rsa.pub.

Andrew Eddy  Feb 24, 2014 
PDF Page 474
Answer 27

The Answer to Question 27 mentions Telnet and FTP, but the question mentioned *SSH* and FTP!

CH  Aug 15, 2011