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.
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 14
Last 3 Lines |
I am attempting to installing ruby per directions on Lion 10.7.3 and I got derailed on the very first step because one needs to install "apt-get" first which requires Fink...... after a long install of Fink and updates and setup - An hour or so, I went back to the first command
sudo apt-get install git-core
While apt-get is present and the command begins.... it stops with....
Couldn't find package git-core
Tue Mar 20 12:32:26 tjadmin@macpro:/Volumes/Development/git >>sudo apt-get install git-core
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package git-core
Not a good start for a follow along set of directions....
Still looking for the problem.... but thought I'd come to O'Reily pubs to check for updates.....
None found.
|
Terry J Fundak |
Mar 20, 2012 |
| PDF |
Page 17
item 9-16 are duplicates of 1-8 |
1. Go to the Opscode website (http://www.opscode.com) and look for the form that
says ?Instant Hosted Chef.?
2. Fill out the form with your email address and your name, then click ?Create my
platform account.?
3. You?ll be taken to a contact details page. Fill out the form, check the box to indicate
that you accept the terms and conditions, and click Submit.?
4. Space robots will provision your account; wait a short while.
5. Check your email for a message from Opscode, containing a link.
6. Clicking on the link will take you straight to the Opscode Platform management
console, as a logged-in user.
7. As a user, interacting with the platform is done via two public/private key pairs?
a user key and an organization or validation key. Your user key can always be
obtained from your user profile. You can get to your user profile by clicking on
your user name at the top of the page, or by going directly to http://community.opscode.
com/users/YOURNAME.
? The platform requires full contact details?including phone number. While your account will work if you
provide bogus details, Opscode?s ability to support you will be hampered.
16 | Chapter 3: Getting Started with Chef
8. Look for the ?Get private key? link, and click it. The Opscode platform won?t store
your private key, so be careful not to lose it! Don?t worry though, you can always
regenerate your key by finding this link again or going directly to http://community.
opscode.com/users/YOURNAME/user_key/new.
9. Go to the Opscode website (http://www.opscode.com) and look for the form that
says ?Instant Hosted Chef.?
10. Fill out the form with your email address and your name, then click ?Create my
platform account.?
11. You?ll be taken to a contact details page. Fill out the form, check the box to indicate
that you accept the terms and conditions, and click Submit.?
12. Space robots will provision your account; wait a short while.
13. Check your email for a message from Opscode, containing a link.
14. Clicking on the link will take you straight to the Opscode Platform management
console, as a logged-in user.
15. As a user, interacting with the platform is done via two public/private key pairs?
a user key and an organization or validation key. Your user key can always be
obtained from your user profile. You can get to your user profile by clicking on
your user name at the top of the page, or by going directly to http://community.opscode.
com/users/YOURNAME.
16. Look for the ?Get private key? link, and click it. The Opscode platform won?t store
your private key, so be careful not to lose it! Don?t worry though, you can always
regenerate your key by finding this link again or going directly to http://community.
opscode.com/users/YOURNAME/user_key/new.
|
Steve Robillard |
Jun 13, 2011 |
| PDF |
Page 22
Sentence after 1st code sample |
states that the keys be available in "~/.ec2", whereas the code sample above uses ~/.chef
|
Terry Ip |
Jul 14, 2011 |
| Printed |
Page 22
First code sample |
In the first code sample the "client_key" line has a syntax error.
The line reads:
client_key "#ENV['HOME']}/.chef/#{user}.pem"
it is missing a { after the initial # . It should be:
client_key "#{ENV['HOME']}/.chef/#{user}.pem"
|
gsandie |
Oct 25, 2011 |
| PDF |
Page 25
1st paragraph under Behavior-Driven Development section |
The first sentence in the first paragraph in the section Behavior-Driven Development has "starting" instead of "started." The full correct sentence should be:
"However, around four years ago, a group of Agile practitioners started rocking the boat."
|
Matthew's O'Reilly Account |
Mar 22, 2012 |
| PDF |
Page 36
2nd paragraph |
When the spaceship operator is explained, the author describes the same comparison (with different wording) yielding different results:
"If the one on the left is less than the one on the right, it returns +1. (...) if the one on the right is greater than the one on the left, it returns -1."
This would turn out to be:
if a < b then +1 (first phrase)
if a < b then -1 (second phrase)
|
Cassiano Leal |
Feb 06, 2014 |
| PDF |
Page 38
United States |
Chapter 5 ends with a list of cucumber-chef options, including what setup does, but does not walk through the process of running the setup command.
Ch 6 starts with a list of assumptions, the last of which is:
" A provisioned test lab generated by Cucumber-Chef setup"
It's almost as if there's a section missing from the end of chapter 5, for what to do after installation.
Simply running 'cucumber-chef setup' will fail because after following along in chapter 5 no ami_image_id will be configured.
|
neilk |
Nov 17, 2011 |
| PDF, Other Digital Version |
Page 48
2nd code sample |
The example consists of three blocks, where the second block is incorrectly repeated.
The correct third block is found at the bottom of the page (continuing onto p49), where the text explains its meaning.
|
Zachary Stevens |
Jul 07, 2011 |
| Printed |
Page 56
Second paragraph |
When talking about the postfix recipe, there is a mention of a "default.rb" file for "recipe[postfix]". However when mentioning the "recipe[postfix::sasl_auth]" recipe, the syntax is shown but there is no mention of the filename that should be used (sasl_auth.rb).
Further in the paragraph there is a mention that using the default recipe for the users recipe wouldn't make sense, and that it would be be better to use "recipe[users::techies]". However after saying we would use "recipe[users::techies]" the section then said that we should edit "cookbooks/users/recipes/default.rb" instead of "cookbooks/users/recipes/techies.rb".
|
gsandie |
Oct 25, 2011 |
| Printed |
Page 59
Third code sample, the JSON example |
The second JSON sample has incorrect syntax, the closing } of the stickers properties is missing a ,
e.g.
{
"id": "laptop",
"owner": "Stephen Nelson-Smith",
"manufacturer": "Apple",
"covered_in_stickers": "Yes",
"stickers": {
"Amazon": "I build my datacenter in 5 minutes",
"Opscode": "Generic logo"
},
"color": "red"
}
|
gsandie |
Oct 25, 2011 |
| PDF |
Page 67
1st sentence |
Mentions a 'test' environment, but the code it refers to (on the preceding page), sets up a 'production' environment
|
Terry Ip |
Jul 20, 2011 |