If you want to clone a running system, I autoyast isn't really your answer, IMHO. Take a look at mkcdrec or mondo rescue (neither of which are part of SLES, unfortunately). You will then be able to get an _exact copy_ of your running system, not just a "similarly configured", which will be the best you can hope to achieve with autoyast. Yan
On Mon, Jun 11, 2007 at 2:48 PM, in message <1181569684.5696.89.camel@localhost>, Elmar Marschke <elmar.marschke@schenker.at> wrote: Am Freitag, den 08.06.2007, 19:53 +0200 schrieb Yan Fitterer: If you want to closely match both machines, better to install both using the same process (i.e. install both with Autoyast, using the same installation source and autoyast file).
Thanks for your answer, Yan, but unfortunately my real goal is to "clone" some production servers which are running since a long time; i can't install these from scratch. As i wrote: "Besides that i got the same problem trying to do the same on some production servers, which are running since a long time. However in those cases the difference is even bigger, there are around 80 packages reported to be installed on just the second machine, which i expected to be an exact clone (also identical hardware and so on)."
So what would be of special interest to me is an answer to this assumption; as i wrote: "My assumption in this case is that some packages are being installed on the "clone", because an "addon" section like "KDE" is in the profile.xml; while some packages of the "kde" selection were separately removed from the "original" machine after installation (without removing the whole selection "kde"). Could this be the cause?"
Has anyone an idea or experience in that?
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org