The problem with GNU Texinfo is not that it is a bad format fordocumentation as such. The problem is what sort of documentationgets written in GNU texinfo format.

To simplify, there are at least two forms of documentation: tutorialsand references. Where I draw the line between the two is that is thattutorial documentation is intended to be read from start to finish,while reference documentation is intended to be skimmed and skippedthrough.

Writing something as a tutorial has at least three effects that arerelevant here:

• it

So you've carefully isolated your management interfaces , making sure that packets can't leak fromone side to another because they literally can't see the other side.You're safe, right?

Well, not quite. While an attacker can't get their own packets across toyour management interface, they may still be able to trick things onyour machine into generating outgoing packets for them. There's a numberof cases:

• packets with a management origin to your management IP: this should

I admit that every so often the freakish superintelligence of the GNUversions of programs has its appeal. Consider, say, units :

You have: 7 feet + 2.5 inchYou want: mm        * 2197.1        / 0.00045514542

GNU date is another good one:

; date -d 'last sunday'Sun Apr 13 00:00:00 EDT 2008

Or even better:

; date -d

One of my little computer terrors is that someday I won't be able tofind good quality plain three button mice any more, because everyonewill have stopped making them. In fact it may already be too late to getdecent USB three button mice, which worries me; although I have a stashof PS/2 ones, I may someday have to migrate to a USB-only machine.

(Searching the web is basically no help in finding out, and since I havea reasonably large stash of suitable