Or some such terminology. What I am realizing is as I work in one vserver
I add, mostly, perl packages that I then need to add in another vserver
that does a similar job to the first. Then if I create a new vserver I'm
putzing around in the reference vserver before hand and in the new vserver
trying to get them up-to-date.
So I am working on what may turn out to be a clever idea to keep my
reference and other vserver syncronized, perl package wise at least, but
wanted to see if I am re-inventing the wheel.
Do any of you try to keep your vservers software up-to-date *and*
syncronized and if so what methods do you use?
Best,
Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
_______________________________________________
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
