On Tue, 18 Oct 2005 11:34:34 -0500, Ryan Nowakowski wrote: > As said, this is not the fastest restore method but with regards to > reinstalling a server it might be pretty quick and versatile. > > 1. Is this doable? Any things i'm overlooking/comments/... > 2. What would be an easy way to making such custom packages be it for > installing config files or fake packages used to install your favourite > apps?
There are folks who have been thinking about this problem for a lot longer than you or me. Check out http://infrastructures.org for the concepts and ISConf[1] for the software. 1. http://trac.t7a.org/isconf Hi, Ryan, very interesting site. Wish I had know it earlier. Just that there is not much said on the web. Can you give more links? Because skimming through it, I get a feeling that we are talking about apple and banners here. The OP's goal is a flexible restore/install system, but I think the site talks about a monster organization wide distributed cloning system. ,----- | It's not for use in environments where you want to still make manual or | ad-hoc changes to machines at the same time. | | * No gold server. You work from the command line of any representative | target machine. | | * No central repository. Packages and change orders are stored in a | distributed cache, checksummed, replicated, and spread across all | participating machines. | | * No CVS server. See the previous point. | | * No single point of failure. See above. | | * Better workflow. No more futzing around with CVS checkins, rsync updates, | or ssh'ing back to the gold server -- there isn't one. You log into one of | the machines you want to change -- more of a natural sysadmin workflow. `----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]