Right from the early days of vendor provided Unix, two things wererelatively obvious to people: first, you were going to need to adda bunch of local programs to make the system really useful to yourusers, and second, adding local programs to vendor areas like /bin or /usr/bin was a pretty sure road to doom and disaster. So peoplestarted putting them somewhere else.

(The most famous example is that BSD Unix put a bunch of their additionsin /usr/ucb , which then

ZFS needs a zfsdump program for the same reasons that every filesystemneeds a *dump program: you need something that can fully and completelyreproduce the state of the on-disk data, complete with sparse files andweird permissions and so on, and can restore small portions of thebackup not just the whole thing.

(In this day of more and more people turning off atime , it's probably no longer so important tohave a backup tool that is guaranteed not to change the state of files.)

Generalized

I think that you should prewire experimental racks for power. By thisI don't mean just making sure that they have some PDUs in them; I meanrunning actual power cords up the sides, with unconnected ends tiedoff every so often ready to be plugged into machines. If you turn outto need more power cords for a machine, don't try to run more powercables along the side unless they too are going to be permanent; justdangle them down the back, where they are easy to