Executed before YaST2 does any real change to the system (Before partitioning and package installation but after the hardware detection)

You can use the pre-script to modify your profile and let autoyast read it again. If you want to do that, you can find your profile in "/tmp/profile/autoinst.xml". Do what you want to do with that file and store the modified version in "/tmp/profile/modified.xml". Autoyast will read that modified script then again after the pre-script is done.

With SUSE Linux 10.0 and all following versions it's possible to change the partitioning with fdisk in your pre-script. With pre 10.0 versions of SUSE Linux (like SLES9), that was not possible.

	Pre-Install Scripts with confirmation
	Pre-scripts are executed at an early stage of the installation. This means if you have requested to confirm the installation, the pre-scripts will be executed before the confirmation screen shows up. (profile/install/general/mode/confirm)

The following elements must be between the <pre-scripts config:type="list"><script> ... </script></pre-scripts> tags

<location>http://10.10.0.1/myPreScript.sh</location>

<source>
<![CDATA[ 
echo "Testing the pre script" > /tmp/pre-script_out.txt 
]]>
</source>

<interpreter>perl</interpreter>

<filename>myPreScript5.sh</filename>

<feedback config:type="boolean">true</feedback>

<debug config:type="boolean">true</debug>

Chroot scripts are executed before the machine reboots for the first time. Actually chroot scripts are two differnt kind of script with one name. You can execute chroot script before the installation chroots into the installed system and configures the boot loader and you can execute a script after the chroot into the installed system has happend (look at the "chrooted" parameter for that). Both types of scripts are executed before yast2 boots for the first time.

The following elements must be between the <chroot-scripts config:type="list"><script> ... </script></chroot-scripts> tags

<location>http://10.10.0.1/myChrootScript.sh</location>

<source>
<![CDATA[ 
echo "Testing the chroot script" > /tmp/chroot_out.txt 
]]>
</source>

<chrooted config:type="boolean">true</chrooted>

<interpreter>perl</interpreter>

<filename>myPreScript5.sh</filename>

<feedback config:type="boolean">true</feedback>

<debug config:type="boolean">true</debug>

These scripts are executed after AutoYaST has completed the system configuration and after it has booted the system for the first time.

Starting from SLES9, network is not available during post-installation script execution. To access the network, network device has to be configured in the script.

It is possible to execute the post scripts in an earlier phase while the installation network is still up and before AutoYaST configures the system. To run network enabled post scripts, the boolean property network_needed has to be set to true.

The following elements must be between the <post-scripts config:type="list"><script> ... </script></post-scripts> tags

<location>http://10.10.0.1/myPostScript.sh</location>

<source>
<![CDATA[ 
echo "Testing the chroot script" > /tmp/chroot_out.txt 
]]>
</source>

<network_needed config:type="boolean">true</network_needed>

<interpreter>perl</interpreter>

<filename>myPostScript5.sh</filename>

<feedback config:type="boolean">true</feedback>

<debug config:type="boolean">true</debug>

	Note
	Available starting from SLES9 only.

These scripts are executed during the initial boot process and after YaST2 has finished. The final scripts are executed using a special init.d script which is executed only once. The final scripts are executed toward the end of the boot process and after network has been intialized.

Init scripts are configured using the tag init-scripts and are run using the special purpose init.d script /etc/init.d/autoyast.

The following elements must be between the <init-scripts config:type="list"><script> ... </script></init-scripts> tags

<location>http://10.10.0.1/myInitScript.sh</location>

<source>
<![CDATA[ 
echo "Testing the init script" > /tmp/init_out.txt 
]]>
</source>

<filename>mynitScript5.sh</filename>

    <?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
        <scripts>
            <chroot-scripts config:type="list">
                <script>
                    <chrooted config:type="boolean">true</chrooted>
                    <filename>chroot.sh</filename>
                    <interpreter>shell</interpreter>
                    <source><![CDATA[
#!/bin/sh
echo "Testing chroot (chrooted) scripts"
ls
]]>                    
                    </source>
                </script>
                <script>
                    <filename>chroot.sh</filename>
                    <interpreter>shell</interpreter>
                    <source><![CDATA[
#!/bin/sh
echo "Testing chroot scripts"
df
cd /mnt
ls
]]>                    
                    </source>
                </script>
            </chroot-scripts>
            <post-scripts config:type="list">
                <script>
                    <filename>post.sh</filename>
                    <interpreter>shell</interpreter>
                    <source><![CDATA[
#!/bin/sh

echo "Running Post-install script"
/etc/init.d/portmap start
mount -a 192.168.1.1:/local /mnt
cp /mnt/test.sh /tmp
umount /mnt
]]>
                </source>
                </script>
                <script>
                    <filename>post.pl</filename>
                    <interpreter>perl</interpreter>
                    <source><![CDATA[
#!/usr/bin/perl
print "Running Post-install script";

]]>
                    </source>
                </script>
            </post-scripts>
            <pre-scripts config:type="list">
                <script>
                    <interpreter>shell</interpreter>
                    <location>http://192.168.1.1/profiles/scripts/prescripts.sh</location>
                </script>
                <script>
                    <filename>pre.sh</filename>
                    <interpreter>shell</interpreter>
                    <source><![CDATA[
#!/bin/sh
echo "Running pre-install script"
]]>
                    </source>
                </script>
            </pre-scripts>
        </scripts>
</profile>


	

After installation is finished, the scripts and the output logs can be found in the directory /var/adm/autoinstall. The scripts are located in scripts and the output logs of the scripts are located in the log directory.

The log is the output resulting when executing the shell scripts using the following command:

      
      /bin/sh -x <script_name> 2&> /var/adm/autoinstall/logs/<script_name>.log