Building custom appliance distributions with rBuilder

And if you use vservers and vhashify, some of this bloatware may actually be shared with
special vserver COW, Copy On Write, hardlinks.  This means that if different appliances use
certain matching libraries they will actually be shared (yet isolated) on disk and in memory!


I use vservers even without vhashify (since I want separate partitions for my vservers so that
I can fail them over to other machines) on my systems at home, and it still seems worth the
penalty to have isolated systems for each server application.  This eliminates most software
upgrade nightmares.  Think about the natural version hell of using various php/database
applications, all eliminated.   ~300MB on debian per major application does not seem like a
severe penalty to pay in the days when a standard HD is probably ~500GB and 4GB of memory is
cheap even for the home user.  

The editor should not dismiss this as a unreasonable solution so easily.  In fact I am
beginning to believe that it is becoming the ONLY reasonable solution to managing server
applications. ;)