-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Tremblay wrote: > On Thu, 2007-07-05 at 17:22 +0100, G T Smith wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Dave Howorth wrote: >>> On Wed, 2007-07-04 at 17:07 -0400, James Tremblay wrote: >>>> How does on build an image for and what tools does one need to clone a >>>> master image to a lab? >>>> If the simple copying of an image leaves you with an unbootable system >>> What makes you say this? If the systems are identical why can't you just >>> copy the raw disk from the master system? >>> >>> Cheers, Dave >>>
<snip> >> What would be useful is a script could be run against an already >> configured machine, that created a DVD (or network image) containing all >> hardware related RPMS, only the RPMs required for the particular setup, >> Then installed a script which went through the hardware phase, >> automatically installed the defined RPMs and then generated unique >> keys/certificates as the installation CD/DVD does and only prompts for >> things like machine name for a configured machine >> >> The YaST AutoInstall system seems to have some of the this kind of >> capability but seems to be rather complex to use .... In fact page 2 of >> the manual for this answers your question to some extent... >> <snip> > GT, > Thanks for your answer. > I have an SLA with Novell that includes the Zenworks Suite, I'm having a > hard time finding any documentation pertaining to "preparing a SLED10 > \SUSE linux image for Cloning". Spent a lot of time trying to get the Institution I used to work to (allow me to) test and hopefully deploy Zenworks ... No success *sigh* Looking at the AutoInstall documentation further it seems that it uses a XML based script which largely goes through the options described by other posters in cloning a machine. Real problem is that no mechanism seems to exist to import an existing package configuration into the script and support for non-SuSE supported applications and other things (e.g. Netbeans, Funambol) that deploy either using a bin or jar file is a bit limited. The documentation can be found at... http://www.suse.de/~ug/autoyast_doc/index.html there is some further work going on but I would suspect Novell may be moving towards a Zenworks based solution. For my purposes, I want to establish a base-line configuration that has some flexibility on hardware configuration, so the next time I have the kind of messy system collapse I have just had, or I want to move to new hardware I can quickly get going again. Unfortunately, binary level disk image cloning is not an option, and even it was does not have any flexibility (it is rare after a hardware related failure that one is restoring to the same hardware configuration). I intend to research this further when I have rebuilt the failed machine. >> James Tremblay >> Director of Technology >> Newmarket School District >> Newmarket,NH >> http://en.opensuse.org/Education >> "let's make a difference" > - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGjgb7asN0sSnLmgIRAslFAJ9ihgXCBBrvN2bZx4l/am02PF6ChACdEJCj ZL9ujaG/KULwSAL8XGkoDVw= =4i0v -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
