https://bugzilla.novell.com/show_bug.cgi?id=760691 https://bugzilla.novell.com/show_bug.cgi?id=760691#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |ug@suse.com --- Comment #2 from Johannes Meixner 2012-05-04 11:27:25 UTC --- The module "finish" is implemented in the YaST SVN source file installation/src/clients/inst_finish.ycp or in the installed system in /usr/share/YaST2/clients/inst_finish.ycp Therein is ------------------------------------------------------------------------- Wizard::SetContents ( _("Finishing Basic Installation"), [...] "label" : _("Copy files to installed system"), "steps" : [ "autoinst_scripts1", ------------------------------------------------------------------------- This matches what I described in /usr/share/doc/packages/rear-SUSE/README ----------------------------------------------------------------------------- General explanation: [...] After AutoYaST had recreated the basic system, in particular partitioning, filesystems, and mount points, AutoYaST runs a so called 'chroot script' to fill in the backup data into the recreated basic system when the mount points of the recreated system are still below '/mnt' and when the boot loader of the recreated system is not yet installed. While the 'chroot script' runs, the YaST screen "Finishing Basic Installation" shows the step "Copy files to installed system". ----------------------------------------------------------------------------- This means that when the module "finish" would be simply removed from /control.xml then the 'chroot script' which should fill in the backup data would no longer run. But in /control.xml there is the "autoimage" which is perhaps the "experimental imaging feature" that was added to AutoYaST in SLES11 http://www.suse.com/~ug/autoyast_changes_SLES10_SLES11.html If this is the case, it might be possible to re-implement the "skip-second-stage" functionality in RecoveryImage via: 1. Use the "experimental imaging feature" in AutoYaST to fill in the backup data only in case of "skip-second-stage" (but still use the 'chroot script' otherwise). 2. Only in case of "skip-second-stage" modify the autoinstallation workflow in control.xml like ---------------------------------------------------------------------------- <workflow> <stage>initial</stage> <label>Base Installation</label> <mode>autoinstallation</mode> ... <module> <label>Perform Installation</label> <name>prepdisk</name> </module> ... <module> <label>Perform Installation</label> <name>autoimage</name> </module> <module> <label>Perform Installation</label> <name>rpmcopy</name> </module> ... <module> <label>Perform Installation</label> <name>bootloader</name> </module> </modules> </workflow> ---------------------------------------------------------------------------- Uwe, is it true that "autoimage" means the "experimental imaging feature" in AutoYaST or am I wrong here? What do you think in general about this approach? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=760691 https://bugzilla.novell.com/show_bug.cgi?id=760691#c4 --- Comment #4 from Johannes Meixner 2012-05-16 08:58:35 UTC --- I can use the "experimental imaging feature" to restore the backup only if the backup is complete (i.e. when the backup contains all files of the system). I cannot use the "experimental imaging feature" to restore the backup when the backup is not complete, e.g. when the backup only contains those files which were added and changed compared to the files in the RPM packages. RecoveryImage provides two features which can be used independent of each other: skip-RPM-install: Do not istall RPMs, i.e. when the backup is complete. skip-second-stage: Do not configure the system, i.e. when the backup contains all config files. It is possible to restore the system by installing the RPMs and additionally a backup which only contains those files which were added and changed compared to the files in the RPM packages. In this case one would run RecoveryImage ... install-RPMs ... skip-second-stage Therefore I need to run a script after "rpmcopy" was run to restore the backup and afterwards I need to install the bootloader and finally only a plain reboot. I think that the above way could be only a workaround with unwanted limitations. In the end I think AutoYaST should natively support the following minimal installation workflow: - create partitioning, filesystems, and mount-points - install files (image or RPMs plus a backup restore) - install bootloader - boot the system -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=760691 https://bugzilla.novell.com/show_bug.cgi?id=760691#c6 --- Comment #6 from Johannes Meixner 2012-09-19 17:33:54 CEST --- Proposal how to use another control.xml only for the "autorecover" entry in isolinux.cfg: Misuse the DriverUpdate functionality in linuxrc, see http://en.opensuse.org/SDB:Linuxrc and http://ftp.suse.com/pub/people/hvogel/Update-Media-HOWTO/Update-Media-HOWTO.... E.g. by something like ---------------------------------------------------------------------------- # autorecover label autorecover kernel linux append initrd=initrd splash=silent showopts autoyast=default netsetup=default driverupdate=/autorecover_inst-sys_update.cpio ---------------------------------------------------------------------------- autorecover_inst-sys_update.cpio is in the root directory of the medium a cpio archive that contains the new control.xml which is copied by linuxrc into the root directory of the install system where YaST looks for it, see http://doc.opensuse.org/projects/YaST/openSUSE11.3/tdg/inst_in_general_chap.... The crucial point is that the DriverUpdate stuff happens after linuxrc had copied the original control.xml from the root directory of the medium into the root directory of the install system so that via DriverUpdate the control.xml in the root directory of the install system can be overwritten by another one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=760691 https://bugzilla.novell.com/show_bug.cgi?id=760691#c8 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #8 from Johannes Meixner 2013-01-15 13:37:25 CET --- Regarding comment#5 running "bootloader_finish": I tested it and it does really not work because - as expected in comment#5 - the "inst_" prefix is added in any case. At last for now I give up because: 1) The more I try to get it work in YaST the more complicated it becomes (too much hardcoded stuff in YaST during "first stage" that contradicts the idea of my "skip-second-stage" functionality). 2) Modify YaST via DriverUpdate is an even more obscure and dirty hack to get it working. 3) My current dirty hack how "skip-second-stage" is implemented in RecoveryImage is still the least invasive (it doesn't modify the installation system) and for the user the most obvious way to get "skip-second-stage" functionality. Summary: At least for now I do no longer try to implement "skip-second-stage" functionality in a more clean way because - according to my current analysis - the current dirty hack in RecoveryImage is the cleanest way that is currently possible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=760691 https://bugzilla.novell.com/show_bug.cgi?id=760691#c10 --- Comment #10 from Johannes Meixner 2013-01-15 15:25:43 CET --- Many thanks for the info! Lukas Ocilka, is my understanding correct that to run clients/bootloader_finish.ycp directly via control.xml it must be specified therein as ---------------------------------------------------------------------------- <module> <label>Perform Installation</label> <execute>bootloader_finish</execute> </module> ---------------------------------------------------------------------------- ? By the way: In library/control/src/ProductControl.ycp there is ------------------------------------------------------------------------ // BNC #401319 // 'execute; is defined and thus returned if (execute != "" && execute != "") { y2milestone ("Step name '%1' executes '%2'", name, execute); return execute; } ------------------------------------------------------------------------ I do not understand the reasoning behind those (execute != "" && execute != "") condition - it looks duplicate - at least for me? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.