On 12/11/2015 10:18 AM, Per Jessen wrote:

ellanios82 wrote:

...

Hello List ,

autoyast=/path-to/autoinst.xml ________________________________

- is it now recommended practice , to use autoinst.xml when upgrading to new Distribution release ?

Hi ellianos,

Using autoyast is surely an advanced practice, only recommended to advanced users. ...............

- have no 1st-hand experience, however, this sounds so very good that it deserves to be recommended to ALL users :) .......... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, Dec 11, 2015 at 3:15 PM, Oliver Kurz wrote: s :)

I don't see how this should properly work or why. IMHO autoyast is intended to clone a configuration - using the same distribution variant and version. yast offers "yast2 clone_system" generating an autoyast configuration file.

autoyast is intended to automate deployment. Whether configuration comes from existing system or you create it yourself is more or less irrelevant. Quite often you want to base it on some standard configuration but still allow variance based on e.g. hardware difference (memory, disks, etc). I was actually impressed how flexible it is (it is heavily used in one of projects I am involved in). Unfortunately I have not see good documentation either ... :p -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Friday 11 December 2015 15:21:48 you wrote:

On Fri, Dec 11, 2015 at 3:15 PM, Oliver Kurz wrote: s :)

...

I don't see how this should properly work or why. IMHO autoyast is intended to clone a configuration - using the same distribution variant and version. yast offers "yast2 clone_system" generating an autoyast configuration file. autoyast is intended to automate deployment. Whether configuration comes from existing system or you create it yourself is more or less irrelevant. Quite often you want to base it on some standard configuration but still allow variance based on e.g. hardware difference (memory, disks, etc). I was actually impressed how flexible it is (it is heavily used in one of projects I am involved in). Unfortunately I have not see good documentation either ... :p

here is a good reference: https://doc.opensuse.org/projects/autoyast/configuration.html TL;:DR: You can do *everything* with autoyast, just make sure you understand the content of the XML file :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/16/2015 09:58 AM, Hans Witvliet wrote:

On Fri, 2015-12-11 at 13:28 +0200, ellanios82 wrote:

...

On 12/11/2015 10:18 AM, Per Jessen wrote:

...

ellanios82 wrote:

...

Hello List ,

autoyast=/path-to/autoinst.xml ________________________________

- is it now recommended practice , to use autoinst.xml when upgrading to new Distribution release ?

Hi ellianos,

Using autoyast is surely an advanced practice, only recommended to advanced users. ...............

- have no 1st-hand experience, however, this sounds so very good that it deserves to be recommended to ALL users :) I've been using it for quite some time. For some it appears something highly advanced, but using it is a real gem! Specially when supplying the xml file to a PXE-boot server. (re-) installing done in a fraction of the time, and with guaranteed exact the same results.

At work we used to do installation with a checklist, whicj took quite some time of tedious work in a server-room. Now the machines spent more time in the bios, than the rest of the installation.

perhaps worthwhile mentioning, you can add self defined scripts for almost all stages during the installation (pre, post)

hw .........

many thanks for encouragement . please help me understand some starting steps : - i have an usb-hub ~ my Install ISO is on an usb-stick , which i plug into my usb-hub - next i plug a Second usb-stick into my usb-hub , containing the vital "autoinst.xml" file - finally, before issuing the 'Install' command , I must enter in to Boot Options Line : autoyast=usb:// ? ? ? my worry is that i am not sure how my boot iso is seeing the TWO usb sticks that I now will have plugged in to the usb-hub perhaps autoyast=floppy/ is a catch-all solution or , do i need to say autoyast=usb://dev/sdd [hoping that is how my second usb stick holding file "autoinst.xml" is seen ?? ......... thanks for your enlightenment ellan ...... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/16/2015 02:02 PM, Oliver Kurz wrote:

On Wednesday 16 December 2015 11:45:27 ellanios82 wrote:

...

On 12/16/2015 09:58 AM, Hans Witvliet wrote: […] I must enter in to Boot Options Line :

autoyast=usb:// ? ? ? […] see https://doc.opensuse.org/projects/autoyast/Invoking.html#bootmedium for reference.

"you can omit specifying the device and trigger AutoYaST to search all devices (autoyast=device:///my.xml)" might work (not tested by me).

It might be easier to supply an absolute http link as autoyast supports network and that is a more standard usecase, e.g. have the autoinst.xml on a private web server or maybe just as a dropbox link if you don't use any personal data in the xml file.

Regards, Oliver ............

thanks , Oliver : i read from your link the helpful info : " autoyast=usb://<path> (since SLES10 SP1) Retrieve the control file from USB devices (AutoYaST will search all connected USB devices). ...... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org