Hello, On Oct 16 16:58 Ladislav Slezak wrote (excerpt):
So here we go: https://github.com/yast/yast-installation/wiki/New-Installer
https://github.com/yast/yast-installation/wiki/New-Installer%3A-SLE12-Instal... therein in section "3. Deployment (step 7 above) (§5)" reads: ------------------------------------------------------------------------- o Create filesystem, optionally untar pre-installed images, install RPMs. The images here are tar.xz images with pre-installed RPMs as are currently used in openSUSE. For SLE the image functionality will be probably not needed... ------------------------------------------------------------------------- I disagree that "for SLE the image functionality is not needed". In particular for SLE it is needed that after a system disaster the new installer can re-create the system on new (compatible) replacement hardware as it was before by using a saved config of the system and deploying one or more backup.tar.gz images that contain the files of the system. To support this the new installer has to do those steps: 1. Boot New Machine 2. Use given config (i.e. the saved system config) 3. Disk Activation (e.g. special stuff to make SAN accessible) 4. Storage/Partitioning 5. Create filesystems and mount them at the right mount points 6. Deploy the files (i.e. untar backup.tar.gz images) 7. Install bootloader 8. Reboot Ideally "Deploy the files" should support any mixture of installing RPMs and whatever kind of software packages plus untar backup.tar.gz images so that it would be possible to have only user data in backup.tar.gz but use RPMs for the basic system software and whatever kind of software packages for other software like third-party software. Is it planned that such system recovery/restore functionality will be supported by the new installer in particular for SLE? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer