Here is a modest suggestion for email clients: when you forward amessage, you should put some marker of this at the front of the Subject: header. Similarly, if you are configuring your email clientand you have a choice, you should set it up this way.

(Some but not all clients do this today.)

Many anti-spam systems that I've seen put a spam status marker at thestart of the Subject: line; it's a relatively obvious place, andputting it

Once upon a time, hard disk transfer rates were an issue of seriousconcern. It mattered a great deal how fast your disks and their IOchannels could run, and changing technologies could have significantperformance effects; IDE versus SCSI and so on really made a difference.

For a lot of people, those days are long over. Disk interconnects areessentially irrelevant (for this) and streaming read and write bandwidthhas become if not irrelevant then generally not important. What matters,what limits performance, is seek time.

Given the previous entry , here's my opinions so faron when you should let ZFS handle your redundancy and when you shouldhave your storage backend do RAID. (This assumes that you have a storagebackend; if not, well, you don't have much choice.)

• if you are doing mirroring, you really want to let ZFS handleit because ZFS will do a much better job of handling small problemsthan your storage backend can.

• if you have a SAN and need your frontends to survive temporary