Here's a paradox about bug reporting: while details are good, too muchdetail is bad (and by this I don't just mean too much verbosity).

Specifically, you should not go into too much detail about what is goingon unless you are certain that you know what you're talking about andyou're sure you're correct about it. By what is going on I don't meansymptoms (those are relatively easy, although tedious, to get right) butwhat

Several times now we've had cases of 'accidental BitTorrent' on ournetworks (and generally gotten email from the campus network peopleabout it); people running BitTorrent clients on our networks withoutintending to. It turns out that this is an amusing (to me) consequenceof the pervasiveness of laptops and laptop hibernation these days.

(You might reasonably ask why we 'allow' BitTorrent at all. There's atleast two reasons; first, without deep packet inspection (and maybeeven then ) we

Here is an aphorism:

Filesystem snapshots preserve mistakes, and so public snapshots preserve mistakes publicly.

This isn't an issue unique to snapshots; it's common to any backupsystem that offers public or 'self serve' restores. In theory a systemthat only let you see or restore files that you owned would avoid theproblem, but the simple version would make certain files inaccessible(files you owned inside directories that other people owned, unless thesystem made an exception for that). Plus it only really