On Fri, 2008-02-22 at 14:58 -0800, Randall R Schulz wrote:
On Friday 22 February 2008 14:44, Hans Witvliet wrote:
...
When doing a manual installation, the very, very last question is wether to generate a XML-config file (for cloning).
I don't recall this, but then, I don't maintain a population of installations, just a couple of one-off systems (one still at 10.0, the other at 10.3), so such an option probably didn't attract my attention.
Even more obscure, with opensuse, the checkbox is default "off" With SLE it is default "on" (something for bugzilla....)
If you did this the previous time (when you installed the 32-bit system) It is merely making a backup of you precious data, and re-install the system with the 64-bit version, but this time feed the autoinstaller with the old xml-file.
Is this XML configuration file updated as you modify your system configuration along the way?
needles to say that that xml-file should be kept on a different media :-)) One might even tweak that xml-file (for adjusting partitionsize, other filesystems....)
If YaST doesn't keep it updated to reflect configuration changes made as the system's configuration evolves, it's of limited usefulness when upgrading months or years down the line...
BTW, if you don't have that xml-file, it is possible to generate it with YAST, (that one even includes all the additional changes you've done with yast)
OK. That's good. I looked around in YaST (on my 10.3 system) and didn't see this function. No doubt I just don't know what it's called. Where is it accessed?
With 10.3 autoinstall in not installed by default, you can still add it on later. yast -> miscellaneous -> autoinstallation -> tools -> create reference profile Select what to want to detect file is written (after a save) under: /var/lib/autoinstall/repository/<yourfilename>
remember all other (manual) changes, you have to replay manually again
Eh? By "manual" do you mean direct configuration file editing not mediated by a YaST module?
Yes, For instance, untill recently there was no yast-module for sshd. So just plain good ol' vi..... Perhaps tweaks is inittab or fstab. I used both methods to create a library of xml-files for any sort of machine/xen-image i have to deploy. Only word on caution is when using xml-file generated for older versions. For instance, since 10.3 they have threads and you can define additional repo's (local update-server!) before installing. But within the same release, from 32->64 it will be safe. Save me a huge amount of time -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org