Guidelines for reviewing The Art Of Unix Programming:

When you send a review or correction, please cite the version number. The first printed edition is 1.0. If you're looking at the on-line version, look at the most recent number in the version history.

Try to batch up your error reports, especially the typos. One email with a lot of corrections in it is better than a dozen single-character fixes.

Please cite chapters, sections, and examples by name rather than number. The chapter numbering has changed often enough during the writing that references by number sometimes confuse me.

Please don't send just diffs against the HTML. They don't map well back to the XML in my masters, and they're hard to read. A copy of the text around the changed location, with the change called out, is much more useful.

Suggest illustrations and pictures, appropriate diagrams and charts. The book-design people like it when they can break up long dry stretches of text with a visual.

If you think you have a better epigraph for any of the chapters, do tell me. Also, I'm lacking sources and dates for some of the quotes; if you can fill in an attribution, please do.

I'm also open to more case studies. But don't just say "You should mention project foo in the discussion of bar"; explain why the software is a good case study, and what design principles and conventions it illustrates. All case studies must be open-source. Small projects with clean code are best, so they can easily be read.

The following are not errors.

Don't assume you've been ignored if you don't get a response; that may just mean that your suggestions were obviously correct and needed no comment. I tend not to reply to routine reports of typos, in any case.