You can have all that with kickstart too .. if the install tree is kept up to date, then it's already patched - and you can include any layered products and packages you want to. Customization can be done with scripting, local config files, whatever.. There's usually no good reason those things need to be done manually after a server is created - unless you're avoiding automation and scripting. (whether cloning or kickstarting)
Scott On Wed, Jun 10, 2009 at 9:09 AM, Marcy Cortes <marcy.d.cor...@wellsfargo.com > wrote: > One other thing to consider is that cloning allows you to bring up an > already patched server [some of us can't bring up unpatched servers on the > prod network]. > > You can also have all of your customization done and other layered products > and packages installed. > > For those reasons we clone. > > > Marcy > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
