Here is something that I have learned the hard way: at least on Solaris10 x86, you cannot create a metaset unless you have a local metadb. Itcan be completely empty, but you have to have one to start with, evenif you are never going to create any local meta-disks and the like.

This is a non-trivial issue because you have to put that local metadb ona disk partition and a default Solaris install doesn't create any spareones. The result

I've recently been forcefully reminded of an important thing about naming machines , namely that you should give yourmachines hostnames that are not English words that you will use inyour email and notes. That way you can actually find where you mentionyour machines when you go searching through the same, instead of gettinglost in the clutter.

(For example, we had a machine called 'mix'. I rapidly gave up searchingour work email archive for information about its history.)

This doesn't mean that

One of the more advanced things you'd like to do with Linux's policybased routing and a dual identity scenario isto be able to make more flexible decisions about what goes out whatinterface. Consider the case where you have two internet connections,one slow but reliable and the other one fast but currently flaky, andyou have a different IP address on each. You would like to send notso important traffic (such as web browsing) over the fast but flakyconnection while still having important traffic like