Reworked errata page

I've reworked the errata page to use color and fonts to classify the errata into three broad types and two levels of "severity".

One reason that I've done this is because there are by now quite a few errata. Another reason is because I earlier received a couple of inquiries along the lines "Because there are a lot of errata, should I wait for the second printing of the book before I buy a copy?" My response to this was "probably not", for reasons that I give below.

As of today, there are 104 errata posted on the errata page. One reason that there are a lot of errata is because there is a lot of book: 1500 pages. Another reason is that I'm very conscientious about fixing and documenting all errors that I find or that are reported to me (by contrast, a lot of books don't even maintain an errata list).

However, the observation that there are a lot of errata also needs to be tempered with some analysis. The current set of errata can be broken down (see the coding on the errata page) as follows:

• 5 fixes to significant code problems.
• 1 significant fix to an explanation in the text.
• 1 significant fix to a technical detail explained in the text.
• 10 minor code fixes. The corresponding code problem is minor and its solution is normally obvious to an attentive reader with a good understanding of C. (The most common culprit here was small code snippets that I wrote directly into the text--complete with syntax errors--rather than extracting directly from source files.)
  
• 24 minor technical fixes. These are typically obvious fixes to minor technical errors or imprecisions in the text. (In many cases, these issues probably wouldn't have impacted the reader's understanding of the topic.)
• 25 minor clarifications. These are improvements or fixes to minor details in the text. In many cases, the fix could simply have been omitted (the problem would have been unlikely to trouble most readers), but I took the opportunity anyway to improve the text because it was easily possible to do so.
• 38 typo fixes. Spelling and grammar corrections and obvious fixes to wording errors.

For most readers, probably only the first three categories of errata will matter--and possibly a few of those in the fourth category. In other words, the number of significant errata fixed between the two print runs is actually quite small, which is why I counseled those wondering whether to wait for the second print run that they probably didn't need to.

PS Meanwhile, we look to still be on target to have the second print run ready and in shops at the start of May.

Low stock

While we wait for the second print run to complete, it looks like some of the online booksellers (such as Amazon.com) have temporarily run out of stock. The second print run should be completed at the start of next month, and sellers will be restocked within a couple of days after that.

man7.org down this weekend

Currently, the company where I work and host my website is going through a move of offices. As a result, access to the man7.org website will see some interruptions. Everything should be right by Monday.

Update 2011-04-17: And we're back

Second print run going to press

Last December, I wrote that we'd be preparing the second print run of the book soon. That time window changed a bit, mainly because it turned out that the lead time with the publisher became much shorter than we expected, so that it was possible to delay preparation of the print run until later. By now however, reserves from the first print run have run low enough that the files for the second print run have already gone to the publisher, and will emerge from the presses in a few weeks time.

The new print run will incorporate all of the errata reported up to the end of March, and I have now reorganized the main errata page so that it breaks the errata down by the print run in which they were applied (as well as a list of errata queued for the next print run).

Updated 2011-04-16 to fix a wording error.

Using TLPI in a university course? Let me know

I didn't specifically target TLPI at the university market as I wrote it. But, by now I've had emails from a number of university teachers who are using TLPI as a required text or as recommended reading for courses on Linux or UNIX system programming.

If you are a teacher or a student using TLPI in a university course, I'd love to hear about it. In particular, I'm very interested to find out more details about how TLPI is being used as a course book, with the idea in mind of improving a future edition of the book for use in that market. If you're a teacher or a student using TLPI, take a look at the questions here, and drop me a mail.

Training course details posted on my web site

I've posted the full training course outline for the Linux/UNIX system programming course that I teach on my web site. You can find it here.

Japanese translation of TLPI

O'Reilly Japan have reached an agreement with No Starch Press to do a Japanese translation of TLPI. I'll add some more details on the web site when I have them.

Update, 2012-02-18: It's likely that this translation will be published toward the end of 2012. Ongoing information about this and other translations can be found on the TLPI translations page.