If you are going to charge for things , one ofthe eternal questions is whether you should use detailed usage chargesor simpler, 'flatter' ones. My personal thoughts run something likethis:

If you have a fixed service that you're expanding slowly (if atall), detailed charges theoretically extract the maximum value forit. However, they do so at the cost of driving away users who don't likethe unpredictability of their bills, and every so often you will havesomething go horribly wrong

Let us suppose, as a not entirely hypothetical example, that youare transplanting the system disks from a Solaris 10 install from aSunFire X2100 to a SunFire X2200. While both machines have four onboardnetwork ports, two Broadcom and two nVidia, they are not quite thesame hardware, enough so that if left to its own devices Solaris willconsider the new machine's NICs to be bge2 , bge3 , nge2 , and nge3 (instead of bge

Here's something that I want: I want a version control system (ideally adistributed one) that can preserve file timestamps. I'm looking for sucha weird feature because I happen to have created something that I want to put under version control where (some of the) filetimestamps are significant and need to be preserved.

(This is yet another hazard of using files as entries , albeit in a slightly different form.)

This is an uncommon feature in version control systems at the best oftimes