Errata

Multiple paragraphs;
Description of the Gnome Power Manager is incorrect. The organization and tab names
listed do not exist in the shipping code. Features listed (backlight brightness
control) do not exist in shipping code.

NOTE: This errata is for the Safari online edition of the book. I don't have a
physical copy of the tome to verify that the errors exist there as well.

Multiple paragraphs;
Description of the Gnome Power Manager is incorrect. The organization and tab names
listed do not exist in the shipping code. Features listed (backlight brightness
control) do not exist in shipping code.

NOTE: This errata is for the Safari online edition of the book. I don't have a
physical copy of the tome to verify that the errors exist there as well.

the Alt-F2 doesn't work.

Note from the Author or Editor:
The text in the book is correct as of Ubuntu release 7.06LTS, which was current at the time of writing. Changes since then may render these instructions obsolete.

Installation of wp-tray is dependent on libgnutls11 library. You need to go to the
Synaptic Package manager and install this before installing wp-tray.

Installation of wp-tray is dependent on libgnutls11 library. You need to go to the
Synaptic Package manager and install this before installing wp-tray.

June 2006: First Edition, Hack #26

The instructions for this hack are valid on Ubuntu 5.10, but not on the newest
release, Dapper Drake 6.06. In the 6.06 release /etc/cups/cupsd.conf does not contain
"RunAsUser Yes" (adding the line "RunAsUser No" to /etc/cups/cupsd.conf does not
alter the following situation. When the "Add a Printer" wizard is opened, the PDF
printer is not detected. Under the Ubuntu 6.06 release, the following workaround is
effective (assuming Gnome desktop environment).

Open a terminal and type "sudo nautilus" and then your password
Go to Filesystem -> usr -> lib -> cups -> backend
Rightclick "cups-pdf" and select Properties
Go to the Permissions tab and click the "Set user ID" special flag

(another way to do the above is from a terminal:

sudo chmod 4755 /usr/lib/cups/backend/cups-pdf)

Now the PDF printer can be added through the "Add a Printer" wizard as described.

Information condensed from here:
http://ubuntuforums.org/showthread.php?t=188860

Not really a technical mistake so much as an update. In Dapper (6.06) the method for
adding a PDF printer has changed. After adding the cups-pdf package the following
command must be run:
sudo chmod +s /usr/lib/cups/backend/cups-pdf
then follow the directions as described in the book (omitting the edit of the
/etc/init.d/cupsd.conf file).

Taken from:
https://help.ubuntu.com/community/PDFPrinting?action=show&redirect=forum%2Fsoftware%2Fcups-
pdf

There is no entry in the cupsd.conf file that has RunAsUser.

Refer to:
https://help.ubuntu.com/community/PDFPrinting?action=show&redirect=forum%2Fsoftware%2Fcups-
pdf
This has an update that you need to set the permission on /usr/lib/cups/backend/cups-
pdf to overcome a bug.
The wiki even says that you need to change RunAsUser, but I was successful in using
the printer without this modification.

June 2006: First Edition, Hack #26

The instructions for this hack are valid on Ubuntu 5.10, but not on the newest
release, Dapper Drake 6.06. In the 6.06 release /etc/cups/cupsd.conf does not contain
"RunAsUser Yes" (adding the line "RunAsUser No" to /etc/cups/cupsd.conf does not
alter the following situation. When the "Add a Printer" wizard is opened, the PDF
printer is not detected. Under the Ubuntu 6.06 release, the following workaround is
effective (assuming Gnome desktop environment).

Open a terminal and type "sudo nautilus" and then your password
Go to Filesystem -> usr -> lib -> cups -> backend
Rightclick "cups-pdf" and select Properties
Go to the Permissions tab and click the "Set user ID" special flag

(another way to do the above is from a terminal:

sudo chmod 4755 /usr/lib/cups/backend/cups-pdf)

Now the PDF printer can be added through the "Add a Printer" wizard as described.

Information condensed from here:
http://ubuntuforums.org/showthread.php?t=188860

Not really a technical mistake so much as an update. In Dapper (6.06) the method for
adding a PDF printer has changed. After adding the cups-pdf package the following
command must be run:
sudo chmod +s /usr/lib/cups/backend/cups-pdf
then follow the directions as described in the book (omitting the edit of the
/etc/init.d/cupsd.conf file).

Taken from:
https://help.ubuntu.com/community/PDFPrinting?action=show&redirect=forum%2Fsoftware%2Fcups-
pdf

There is no entry in the cupsd.conf file that has RunAsUser.

Refer to:
https://help.ubuntu.com/community/PDFPrinting?action=show&redirect=forum%2Fsoftware%2Fcups-
pdf
This has an update that you need to set the permission on /usr/lib/cups/backend/cups-
pdf to overcome a bug.
The wiki even says that you need to change RunAsUser, but I was successful in using
the printer without this modification.

ftp://ftp.nerim.net no longer has a directory "debian-marillat". After a bit of
googling, I found http://debian.video.free.fr/ which states:

07/05/2006 :
Why Marillat's repository doesn't work ? Because now the repository is here debian-
multimedia.org
See at the bottom for news sources.list entries.
Now you can use the distro name or the alias name (stable --> sarge or etch -->
testing).

I can't seem to find the w32codecs_20050412-0.0_i386.deb file in the mirrors, though.

RESPONSE FROM AUTHOR:
That particular file has been superseded by a newer package. The
specific file listed ("w32codecs_20050412-0.0_i386.deb") includes the
version number, so you need to look for the same package but without the
specific version.

The actual package name is the portion before the first underscore, ie:
"w32codecs".

The new packages can be obtained by editing the file
"/etc/apt/sources.list" as specified on the www.debian-multimedia.org
site. Open your "sources.list" file and add a line like this:

deb http://www.debian-multimedia.org testing main

Then "sudo apt-get update" to refresh the package list, and you'll be
able to find the package using "apt-cache search w32codecs" and install
it with "sudo apt-get install w32codecs".

ftp://ftp.nerim.net no longer has a directory "debian-marillat". After a bit of
googling, I found http://debian.video.free.fr/ which states:

07/05/2006 :
Why Marillat's repository doesn't work ? Because now the repository is here debian-
multimedia.org
See at the bottom for news sources.list entries.
Now you can use the distro name or the alias name (stable --> sarge or etch -->
testing).

I can't seem to find the w32codecs_20050412-0.0_i386.deb file in the mirrors, though.

RESPONSE FROM AUTHOR:
That particular file has been superseded by a newer package. The
specific file listed ("w32codecs_20050412-0.0_i386.deb") includes the
version number, so you need to look for the same package but without the
specific version.

The actual package name is the portion before the first underscore, ie:
"w32codecs".

The new packages can be obtained by editing the file
"/etc/apt/sources.list" as specified on the www.debian-multimedia.org
site. Open your "sources.list" file and add a line like this:

deb http://www.debian-multimedia.org testing main

Then "sudo apt-get update" to refresh the package list, and you'll be
able to find the package using "apt-cache search w32codecs" and install
it with "sudo apt-get install w32codecs".

These paragraphs give directions for editing the file "config" for use with a proxy. Both paragraphs discuss editing sections 1.5 and 1.6 of the "config" file.

The correct settings are contained in sections 2.5 and 2.6 of "config".

While I have had success with this hack, during a fresh install today I found the
following error in /var/log/tor/log:
"Aug 11 17:13:43.261 [warn] You are running Tor version 0.1.0.16, which will not work
with this network. Please use one of 0.1.0.18,0.1.1.23."
Following the Tor documentation to
http://wiki.noreply.org/noreply/TheOnionRouter/TorOnDebian , I installed Tor version
0.1.1.23 .

This brings me to figure 7-8. The figure is correct, but the dialog box is
sufficiently confusing that I think a bit more explanation would be helpful. "SOCKS
v4" and "SOCKS v5" have radio buttons, but neither are initially checked and it's not
clear if they refer to the text box "SOCKS Proxy" immediately above them (if the text
box is empty, shouldn't they be grayed out?). Unfortunately, if either is accidently
checked, there's no way to go back to the state of both being unchecked.

If one had to guess, "SOCKS v4" looks kinda sorta like the "forward-socks4a" that was
put into the config file. Unfortunately, that didn't work. Leaving both of them
unchecked or checking "SOCKS v5" does work for me.

While this GUI is (of course) not the fault of the authors, I think it's sufficiently
confusing to deserve a warning in the text.

While I have had success with this hack, during a fresh install today I found the
following error in /var/log/tor/log:
"Aug 11 17:13:43.261 [warn] You are running Tor version 0.1.0.16, which will not work
with this network. Please use one of 0.1.0.18,0.1.1.23."
Following the Tor documentation to
http://wiki.noreply.org/noreply/TheOnionRouter/TorOnDebian , I installed Tor version
0.1.1.23 .

This brings me to figure 7-8. The figure is correct, but the dialog box is
sufficiently confusing that I think a bit more explanation would be helpful. "SOCKS
v4" and "SOCKS v5" have radio buttons, but neither are initially checked and it's not
clear if they refer to the text box "SOCKS Proxy" immediately above them (if the text
box is empty, shouldn't they be grayed out?). Unfortunately, if either is accidently
checked, there's no way to go back to the state of both being unchecked.

If one had to guess, "SOCKS v4" looks kinda sorta like the "forward-socks4a" that was
put into the config file. Unfortunately, that didn't work. Leaving both of them
unchecked or checking "SOCKS v5" does work for me.

While this GUI is (of course) not the fault of the authors, I think it's sufficiently
confusing to deserve a warning in the text.

I don't know if its really an error per se,perhaps an omission, but it did give me
some trouble. I followed the kernel compilation instructions and was greeted by
kernel panic upon rebot. Some searching led to find that I had to use mkinitrd to get
my new kenel to boot. Some more searching led me to the fact that if I pass -initrd
to make-kpkg it will do this for me. I don't know if this problem was due to my setup
or not but thought I would pass it along.

I don't know if its really an error per se,perhaps an omission, but it did give me
some trouble. I followed the kernel compilation instructions and was greeted by
kernel panic upon rebot. Some searching led to find that I had to use mkinitrd to get
my new kenel to boot. Some more searching led me to the fact that if I pass -initrd
to make-kpkg it will do this for me. I don't know if this problem was due to my setup
or not but thought I would pass it along.

The paragraph states that the user should create a symlink to /etc/apache2/mods-enabled/vhosts_alias.load. That file did not exist on a fresh install of Ubuntu Server and Apache2.

The paragraph states that the user should create a symlink to /etc/apache2/mods-enabled/vhosts_alias.load. That file did not exist on a fresh install of Ubuntu Server and Apache2.