I don't use Gnome on my primary machine (it runs a peculiar, entirelycustom environment), but I do use it on a number of secondary machinesand I keep making more or less the same customizations each time. So I'mwriting them down, if only for my own reference on the next machine.

• I disable gnome-terminal's blinking cursor .

• I turn CapsLock into an additional Ctrl. This is in the Keyboardpreferences area, Layout tab, 'Layout options' button, and

I recently ran across MC/S vs MPIO , which is about why iSCSI's 'multipleconnections per session' feature is apparently considered a bad ideaand is not likely to be implemented in Linux, the short summary beingthat it is an iSCSI specific duplication of generic multipathingfunctionality. Unfortunately, I sort of disagree with this in practice.

In theory I don't care about how my multipathing is done, I just wantsomething that makes general iSCSI multipathing work right. In practice,right now generic multipathing

Suppose that you have a 'sender stores message' email system, and thatyou protect yourself against the sender rewriting the message after it'sinitially sent by sending and verifying a secure hash of the messagebefore you show the message to the user. To follow up a recent entry , here are the social and technical issuesthat I can see with this hash protection scheme.

First and largest, you have a social issue; users are going to reactbadly to 'this message is (minorly) corrupt so I