Today we had a fun problem created by a combination of entirely rational find optimizations and a corrupted, damaged filesystem.

An important Linux server took some kind of hit that turned some filesinto directories (with contents, presumably stolen from some other poordirectory). We found some but were pretty sure there were others lurkingout there too, and wanted to do our best to find them. (If only tofigure out what we needed to restore from the last good backups.)

As it happens, most of the

Although documentation is not free , it shouldbe cheap. By that, I mean that documentation should cost as little aspossible to produce, so that you get as much of it as possible for yourbudget. Again, the major cost is in people's time, so you want writingdocumentation to be as fast (and easy) as possible.

The golden rule is that time that people are spending doing anythingexcept writing down the actual content is overhead. You get the mostbang to the buck by minimizing