On 3/16/10 3:22 PM, "686f6c6d" <686f6c6d@googlemail.com> wrote:
For pre-scripts, note these are run *before* the target system is even mounted. So if you write anything anywhere, it doesn't mean it will end up in the target system. The example from the docs[0] for a pre-script is to edit the autoyast profile and reread it. Try something like that, too (because I can't think of anything else useful right now; well, if you have access to the webserver logs, you could put something useless like "wget http://pxe/script1-success" in there).
I use pre-install scripts extensively... my solution to capture the output was to run all my work in a subdirectory in /tmp (call it /tmp/myinstall for the purpose of the example) and install a chroot script, executed before the first reboot but after the install, set to run in the default mode which is <chrooted config:type="boolean">false</chrooted> it's actually run before chrooting, so the new root is available on /mnt. My chroot script basically cp -R /tmp/myinstall and into /mnt/var/adm/autoinstall/myinstall ... thus all my logs, scripts and everything else done in pre-install space may be found with the rest of the autoinstall stuff. http://suse.de/%7Eug/autoyast_doc/createprofile.scripts.html#chroot.scripts Works like a charm Tim -- Tim Kirby 651-605-9074 trk@cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org