4 Configuration and Installation Options #

If you set this entry to false, the default systemd target will not be activated via the call systemctl isolate. Setting this value is optional. The default is true.

<general>
 <mode>
  <activate_systemd_default_target config:type="boolean">
   true
  </activate_systemd_default_target>
 </mode>
 ...
</general>

By default, the installation stops at the Installation Settings screen. Up to this point, no changes have been made to the system and settings may be changed on this screen. To proceed and finally start the installation, the user needs to confirm the settings. By setting this value to false the settings are automatically accepted and the installation starts. Only set to false to carry out a fully unattended installation. Setting this value is optional. The default is true.

<general>
 <mode>
  <confirm config:type="boolean">true</confirm>
 </mode>
 ...
</general>

If you set this to true, the EULA of the base product will be shown. The user needs to accept this license. Otherwise the installation will be canceled. Setting this value is optional. The default is false. This setting applies to the base product license only. Use the flag confirm_license in the add-on section for additional licenses (see Section 4.9.3, “Installing Additional/Customized Packages or Products” for details).

<general>
 <mode>
  <confirm_base_product_license config:type="boolean">
   false
  </confirm_base_product_license>
 </mode>
 ...
</general>

When set to true, the machine shuts down after everything is installed and configured at the end of the second stage. If you enable final_halt, you do not need to set the final_reboot option to true.

<general>
 <mode>
  <final_halt config:type="boolean">false</final_halt>
 </mode>
 ...
</general>

When set to true, the machine reboots after everything is installed and configured at the end of the second stage. If you enable final_reboot, you do not need to set the final_halt option to true.

<general>
 <mode>
  <final_reboot config:type="boolean">true</final_reboot>
 </mode>
 ...
</general>

If you set this entry to false, services will not be restarted at the end of the installation (when everything is installed and configured at the end of the second stage). Setting this value is optional. The default is true.

<general>
 <mode>
  <final_restart_services config:type="boolean">
   true
  </final_restart_services>
 </mode>
 ...
</general>

Shuts down the machine after the first stage. All packages and the boot loader have been installed and all your chroot scripts have run. Instead of rebooting into stage two, the machine is turned off. If you turn it on again, the machine boots and the second stage of the autoinstallation starts. Setting this value is optional. The default is false.

<general>
 <mode>
  <halt config:type="boolean">false</halt>
 </mode>
 ...
</general>

Specifies how long AutoYaST waits (in seconds) at most for systemd to set up the default target. Setting this value is optional and should not normally be required. The default is 30 (seconds).

<general>
 <mode>
  <max_systemd_wait config:type="integer">30</max_systemd_wait>
 </mode>
 ...
</general>

Specify the NTP server with which to synchronize time before starting the installation. Time synchronization will only occur if this option is set. Keep in mind that you need a network connection and access to a time server. Setting this value is optional. By default no time synchronization will occur.

<general>
     <mode>
      <ntp_sync_time_before_installation>
       &ntpname;
      </ntp_sync_time_before_installation>
     </mode>
     ...
    </general>

A regular installation of SUSE Linux Enterprise Server is performed in a single stage. The auto-installation process, however, is divided into two stages. After the installation of the basic system the system boots into the second stage where the system configuration is done. Set this option to false to disable the second stage. Setting this value is optional. The default is true.

<general>
 <mode>
  <second_stage config:type="boolean">true</second_stage>
 </mode>
 ...
</general>

If set to true or false, this option enables or disables the YaST self-update feature. Setting this value is optional. The default is true.

<general>
 <self_update config:type="boolean">true</self_update>
 ...
</general>

Alternatively, you can specify the boot parameter self_update=1 on the kernel command line.

Location of the update repository to use during the YaST self-update. For more information, refer to the Deployment Guide.

Important: Installer Self-Update Repository Only

The self_update_url parameter expects only the installer self-update repository URL. Do not supply any other repository URL—for example the URL of the software update repository.

<general>
 <self_update_url>
  http://example.com/updates/$arch
 </self_update_url>
 ...
</general>

The URL may contain the variable $arch. It will be replaced by the system's architecture, such as x86_64, s390x, etc.

Alternatively, you can specify the boot parameter self_update=1 together with self_update=URL on the kernel command line.

If set to true, AutoYaST will accept unsigned files like the content file.

<general>
 <signature-handling>
  <accept_unsigned_file config:type="boolean">
   false
  </accept_unsigned_file>
 </signature-handling>
 ...
<general>

If set to true, AutoYaST will accept files without a checksum in the content file.

<general>
 <signature-handling>
  <accept_file_without_checksum config:type="boolean">
   false
  </accept_file_without_checksum>
 </signature-handling>
 ...
<general>

If set to true, AutoYaST will accept signed files even when the signature verification fails.

<general>
 <signature-handling>
  <accept_verification_failed config:type="boolean">
   false
  </accept_verification_failed>
 </signature-handling>
 ...
<general>

If set to true, AutoYaST will accept new GPG keys of the installation sources, for example the key used to sign the content file.

<general>
 <signature-handling>
  <accept_unknown_gpg_key config:type="boolean">
   false
  </accept_unknown_gpg_key>
 </signature-handling>
 ...
<general>

Set this option to true to accept known keys you have not yet trusted.

<general>
 <signature-handling>
  <accept_non_trusted_gpg_key config:type="boolean">
   false
  </accept_non_trusted_gpg_key>
 </signature-handling>
 ...
<general>

If set to true, AutoYaST will accept and import new GPG keys on the installation source in its database.

<general>
 <signature-handling>
  <import_gpg_key config:type="boolean">
   false
  </import_gpg_key>
 </signature-handling>
 ...
<general>

Defines scripts and sleep time executed before a configuration module starts. The following code shows an example setting the sleep time to ten seconds and executing an echo command before running the network configuration module.

<general>
 <wait>
  <pre-modules config:type="list">
   <module>
    <name>networking</name>
    <sleep>
     <time config:type="integer">10</time>
     <feedback config:type="boolean">true</feedback>
    </sleep>
    <script>
     <source>echo foo</source>
     <debug config:type="boolean">false</debug>
    </script>
   </module>
  </pre-modules>
  ...
 </wait>
<general>

Defines scripts and sleep time executed after a configuration module starts. The following code shows an example setting the sleep time to ten seconds and executing an echo command after running the network configuration module.

<general>
 <wait>
  <post-modules config:type="list">
   <module>
    <name>networking</name>
    <sleep>
     <time config:type="integer">10</time>
     <feedback config:type="boolean">true</feedback>
    </sleep>
    <script>
     <source>echo foo</source>
     <debug config:type="boolean">false</debug>
    </script>
   </module>
  </post-modules>
  ...
 </wait>
<general>

Set the boot flag on the boot partition. The boot partition can be / if there is no separate /boot partition. If the boot partition is on a logical partition, the boot flag is set to the extended partition.

<activate>true</activate>

Kernel parameters added at the end of boot entries for normal and recovery mode.

<append>nomodeset vga=0x317</append>

Write GRUB 2 to a separate /boot partition. If no separate /boot partition exists, GRUB 2 will be written to /.

<boot_boot>false</boot_boot>

Write GRUB 2 to a custom device.

<boot_custom>/dev/sda3</boot_custom>

Write GRUB 2 to the extended partition (important if you want to use generic boot code and the /boot partition is logical). Note: if the boot partition is logical, you should use boot_mbr (write GRUB 2 to MBR) rather than generic_mbr.

<boot_extended>false</boot_extended>

Write GRUB 2 to the MBR of the first disk in the order. (device.map includes the order of the disks).

<boot_mbr>false</boot_mbr>

Write GRUB 2 to / partition.

<boot_root>false</boot_root>

Write generic boot code to the MBR (will be ignored if boot_mbr is set to true).

<generic_mbr config:type="boolean">false</generic_mbr>

Graphical resolution of the GRUB 2 screen (requires <terminal> to be set to gfxterm).

Valid entries are auto, HORIZONTALxVERTICAL, or HORIZONTALxVERTICAL xCOLOR DEPTH. You can see the screen resolutions supported by GRUB 2 on a particular system by using the vbeinfo command at the GRUB 2 command line in the running system.

<gfxmode>1280x1024x24</gfxmode>

If set to true, automatically searches for operating systems already installed and generates boot entries for them during the installation.

<os_prober>false</os_prober>

Allows choosing a default setting of kernel boot command line parameters for CPU mitigation (and at the same time strike a balance between security and performance).

Possible values are:

<cpu_mitigations>auto</cpu_mitigations>

If not set in AutoYaST, the respective settings can be changed via kernel command line. By default, the (product-specific) settings in the /control.xml file on the installation medium are used (if nothing else is specified).

Obsolete and no longer used. Booting from Btrfs snapshots is automatically enabled.

Command to execute if the GRUB 2 terminal mode is set to serial.

<serial>serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1</serials>

If set to false, then UEFI secure boot is disabled. Works only for grub2-efi boot loader.

<secure_boot>false</secure_boot>

Specify the GRUB 2 terminal mode to use. Valid entries are console, gfxterm, and serial. If set to serial, the serial command needs to be specified with <serial>, too.

<terminal>serial</terminal>

The timeout in seconds until the default boot entry is booted automatically.

<timeout config:type="integer">10</timeout>

If set to true, then Trusted GRUB is used. Trusted GRUB supports Trusted Platform Module (TPM). Works only for grub2 boot loader.

<trusted_boot">true</trusted_boot>

Adds the kernel parameter vga=VALUE to the boot entries.

<vgamode>0x317</vgamode>

Kernel parameters added at the end of boot entries for Xen guests.

<xen_append>nomodeset vga=0x317</xen_append>

Kernel parameters added at the end of boot entries for Xen kernels on the VM Host Server.

<xen_kernel_append>dom0_mem=768M</xen_kernel_append>

Creates an LVM-based proposal. The default is false.

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

When set to true, AutoYaST resizes Windows partitions if needed to make room for the installation.

<resize_windows config:type="boolean">false</resize_windows>

Enables encryption using the specified password. By default, encryption is disabled.

<encryption_password>some-secret</encryption_password>

This level increases your disk performance. There is no redundancy in this mode. If one of the drives crashes, data recovery will not be possible.

This mode offers the best redundancy. It can be used with two or more disks. An exact copy of all data is maintained on all disks. As long as at least one disk is still working, no data is lost. The partitions used for this type of RAID should have approximately the same size.

This mode combines management of a larger number of disks and still maintains some redundancy. This mode can be used on three disks or more. If one disk fails, all data is still intact. If two disks fail simultaneously, all data is lost.

This mode allows access to the same physical device via multiple controllers for redundancy against a fault in a controller card. This mode can be used with at least two devices.

<cache_mode>writethrough</cache_mode>

Cache mode for bcache. Possible values are writethrough, writeback, writearound and none.

SUSE Linux Enterprise Server

SUSE Linux Enterprise High Performance Computing

SUSE Linux Enterprise Real Time

SUSE Linux Enterprise Server for SAP Applications

SUSE Linux Enterprise Desktop

SUSE Manager Server

SUSE Manager for Retail

SUSE Manager Proxy

Product URL. Can have the prefix cd:///, http://, ftp://, etc. This entry is mandatory.

If you use a multi-product medium such as the SUSE Linux Enterprise Packages DVD, then the URL path should point to the root directory of the multi-product medium. The specific product directory is selected using the product_dir value (see below).

Internal product name if the add-on is a product. The command zypper products shows the names of installed products.

Repository alias name. Defined by the user.

Optional subpath. This should only be used for multi-product media such as the SUSE Linux Enterprise Packages DVD.

Sets the repository libzypp priority. Priority of 1 is the highest. The higher the number, the lower the priority. Default is 99.

AutoYaST can ask the user to make add-on products, modules or extensions available instead of reporting a time-out error when no repository can be found at the given location. Set ask_on_error to true (the default is false).

The user needs to confirm the license. Default is false.

Repository name. The command zypper lr shows the names of added repositories.

If set to true, AutoYaST will accept unsigned files like the content file.

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

If set to true, AutoYaST will accept files without a checksum in the content file.

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

If set to true, AutoYaST will accept signed files even when the verification of the signature failed.

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

If set to true, AutoYaST will accept new GPG keys of the installation sources, for example the key used to sign the content file.

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

Set this option to true to accept known keys you have not yet trusted.

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

If set to true, AutoYaST will accept and import new GPG keys on the installation source in its database.

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

If set to true, AutoYaST will accept unsigned files like the content file for this add-on product.

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

If set to true, AutoYaST will accept files without a checksum in the content file for this add-on.

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

If set to true, AutoYaST will accept signed files even when the verification of the signature fails.

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

If all is set to true, AutoYaST will accept new GPG keys on the installation source.

<accept_unknown_gpg_key>
  <all config:type="boolean">true</all>
</accept_unknown_gpg_key>

Otherwise you can define single keys too.

<accept_unknown_gpg_key>
  <all config:type="boolean">false</all>
  <keys config:type="list">
    <keyid>3B3011B76B9D6523</keyid>
  </keys>
</accept_unknown_gpg_key>

This means, the key is known, but it is not trusted by you.

You can trust all keys by adding:

<accept_non_trusted_gpg_key>
  <all config:type="boolean">true</all>
</accept_non_trusted_gpg_key>

Or you can trust specific keys:

<accept_non_trusted_gpg_key>
  <all config:type="boolean">false</all>
  <keys config:type="list">
    <keyid>3B3011B76B9D6523</keyid>
  </keys>
</accept_non_trusted_gpg_key>

If all is set to true, AutoYaST will accept and import all new GPG keys on the installation source into its database.

<import_gpg_key>
  <all config:type="boolean">true</all>
</import_gpg_key>

This can be done for specific keys only:

<import_gpg_key>
  <all config:type="boolean">false</all>
  <keys config:type="list">
    <keyid>3B3011B76B9D6523</keyid>
  </keys>
</import_gpg_key>

Selects the network back-end to be used. Supported values are wicked, network_manager or none, the latter of which will disable the network service.

<backend>network_manager</backend>

As described in Section 4.12.1, “Configuration Workflow”, by default, AutoYaST merges the network configuration from the running system with the one defined in the profile. If you want to use only the configuration from the profile, set this element to false. The value is true by default.

<keep_install_network config:type="boolean">false</keep_install_network>

Determines whether to use NetworkManager instead of Wicked.

Deprecated. Use backend instead.

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

Forces AutoYaST to restart the network just after writing the configuration.

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

Use the network configuration defined in the profile during the installation process. Otherwise, AutoYaST relies on the configuration set by linuxrc.

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

After setting up the network, AutoYaST checks whether the assigned IP address is duplicated. In that case, it shows a warning whose timeout in seconds is controlled by this element. If it is set to 0, the installation is stopped.

<strict_IP_check_timeout config:type="integer">5</strict_IP_check_timeout>

AutoYaST configures a bridge when a virtualization package is selected to be installed (e.g., Xen, QEMU or KVM). You can disable such a behaviour by setting this element to false.

<virt_bridge_proposal config:type="boolean">false</virt_bridge_proposal>

As described in Section 4.12.1, “Configuration Workflow”, by default, AutoYaST merges the network configuration from the running system with the one defined in the profile. If you want to use just the configuration from the profile, set this element to false. The value is true by default.

<keep_install_network config:type="boolean">false<keep_install_network>

Determines whether to use NetworkManager instead of Wicked.

<managed config:type="boolean">true>managed<

Forces AutoYaST to restart the network just after writing the configuration.

<start_immediately config:type="boolean">true<start_immediately>

Use the network configuration defined in the profile during the installation process. Otherwise, AutoYaST relies on the configuration set by linuxrc.

<setup_before_proposal config:type="boolean">true<setup_before_proposal>

After setting up the network, AutoYaST checks whether the assigned IP address is duplicated. In that, it shows a warning whose timeout is controlled by this element. If it is set to 0, the installation is stopped.

<strict_IP_check_timeout config:type="integer">5<strict_IP_check_timeout>

Boot protocol used by the interface. Possible values:

Required.

Broadcast IP address.

Used only with static boot protocol.

Device name.

Deprecated. Use name instead.

Device name, for example: eth0.

Required.

IP address assigned to the interface.

Used only with static boot protocol. It can include a network prefix, for example: 192.168.1.1/24.

Remote IP address for point-to-point connections.

Used only with static boot protocol.

Network mask, for example: 255.255.255.0.

Deprecated. Use prefixlen instead or include the network prefix in the ipaddr element.

Network IP address.

Deprecated. Use ipaddr with prefixlen instead.

Network prefix, for example: 24.

Used only with static boot protocol.

When to bring up an interface. Possible values are:

Priority for ifplugd daemon. It determines in which order the devices are activated.

Used only with ifplugd start mode.

Parameter is no longer used.

Deprecated.

Name of the bonding device.

Required for bonding devices. X is replaced by a number starting from 0, for example bonding_slave0. Each slave needs to have a unique number.

Options for bonding device.

Used only with bond device.

Maximum transmission unit for the interface.

Optional.

Ethtool options during device activation.

Optional.

Firewall zone name which the interface is assigned to.

Optional.

Identifier used for this VLAN.

Used only with a vlan device.

Device to which VLAN is attached.

Used only with a vlan device and required for it.

yes if interface is a bridge.

Deprecated. It is inferred from other attributes.

Space-separated list of bridge ports, for example, eth0 eth1.

Used only with a bridge device and required for it.

Spanning tree protocol. Possible values are on (when enabled) and off (when disabled).

Used only with a bridge device.

Forward delay for bridge, for example: 15.

Used only with bridge devices. Valid values are between 4 and 30.

Host name, excluding the domain name part. For example: foo instead of foo.bar. The Linux kernel allows using the fully-qualified domain name (FQDN) in place of the host name, and so does YaST. However, this is not the correct usage in the dns section of YaST. The resolver should determine the FQDN. (See "THE FQDN" section of man 1 hostname for information on how FQDNs are resolved.)

If a host name is not specified and is not taken from a DHCP server (see dhcp_hostname), AutoYaST will generate a random hostname.

List of name servers. Example:

<nameservers config:type="list">
  <nameserver>192.168.1.116</nameserver>
  <nameserver>192.168.1.117</nameserver>
</nameservers>

Search list for host name lookup.

<searchlist config:type="list">
  <search>example.com</search>
</searchlist>

Optional.

Specifies whether the host name must be taken from DHCP or not.

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

Required: Route destination. An address prefix can be specified, for example: 192.168.122.0/24.

The heading default can be used to indicate that the route is the default gateway in the same address family (ipv4 or ipv6) as the gateway

Required: Interface associated to the route.

Optional: Gateway's IP address.

(Deprecated.) Destination's netmask.

Specifying the prefix as part of the destination value is preferred.

Optional: Further route options like the metric, mtu or table.

qeth, ctc or iucv

channel ids separated by a colon (preferred) or a space

<chanids>0.0.0700:0.0.0701:0.0.0702</chanids>

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

boolean; default: false

QETH port name (deprecated since SLE 12 SP2)

CTC / LCS protocol, a small number (as a string)

<protocol>1</protocol>

optional

IUCV router/user

When someone at the console has pressed the Ctrl–Alt–Del key combination, the system usually reboots. Sometimes it is desirable to ignore this event, for example, when the system serves as both workstation and server.

Configure a list of users allowed to shut down the machine from GDM.

Text

<username>lukesw</username>

Required. It should be a valid user name. Check man 8 useradd if you are not sure.

Text

<fullname>Tux Torvalds</fullname>

Optional. User's full name.

Text

<forname>Tux</forename>

Optional. User's forename.

Text

<surname>Skywalker</surname>

Optional. User's surname.

Number

<uid>1001</uid>

Optional. User ID. It should be a unique and must be a non-negative number. If not specified, AutoYaST will automatically choose a user ID. Also refer to Note: Specifying a User ID (uid) for additional information.

Number

<gid>100</gid>

Optional. Initial group ID. It must be a unique and non-negative number. Moreover it must refer to an existing group.

Path

<home>/home/luke</home>

Optional. Absolute path to the user's home directory. By default, /home/username will be used (for example, alice's home directory will be /home/alice).

Boolean

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

Optional. Generates the home directory in a Btrfs subvolume. Disabled by default.

Path

<shell>/usr/bin/zsh</shell>

Optional. /bin/bash is the default value. If you choose another one, make sure that it is installed (adding the corresponding package to the software section).

Text

<user_password>some-password</user_password>

Optional. A user's password can be written in plain text (not recommended) or in encrypted form. To create an encrypted password, use mkpasswd. Enter the password as written in /etc/shadow (second column). To enable or disable the use of encrypted passwords in the profile, see the encrypted parameter. With encrypted passwords disabled, if you enter an exclamation mark (!), a random password will be generated. With encrypted passwords enabled, the value is copied to the password field of /etc/shadow. If you enter an exclamation mark (!) in this case, you get an account with locked password that cannot login on console.

Boolean

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

Optional. Considered false if not present. Indicates if the user's password in the profile is encrypted or not. AutoYaST supports standard encryption algorithms (see man 3 crypt).

Password settings

<password_settings>
  <expire/>
  <max>60</max>
  <warn>7</warn>
</password_settings>

Optional. Some password settings can be customized: expire (account expiration date in format YYYY-MM-DD), flag (/etc/shadow flag), inact (number of days after password expiration that account is disabled), max (maximum number of days a password is valid), min (grace period in days until which a user can change password after it has expired) and warn (number of days before expiration when the password change reminder starts).

List of authorized keys

<authorized_keys config:type="list">
  <listentry>ssh-rsa ...</listentry>
</authorized_keys>

A list of authorized keys to be written to $HOME/.ssh/authorized_keys. See example below.

Text

<group>100</group>

Optional. Default initial login group.

Text

<groups>users</groups>

Optional. List of additional groups.

Path

<home>/home</home>

Optional. User's home directory prefix.

Date

<expire>2017-12-31</expire>

Optional. Default password expiration date in YYYY-MM-DD format.

Number

<inactive>3</inactive>

Optional. Number of days after which an expired account is disabled.

Boolean

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

Optional. Do not use secondary groups.

Path

<shell>/usr/bin/fish</shell>

Default login shell. /bin/bash is the default value. If you choose another one, make sure that it is installed (adding the corresponding package to the software section).

Path

<skel>/etc/skel</skel>

Optional. Location of the files to be used as skeleton when adding a new user. You can find more information in man 8 useradd.

File creation mode mask

<umask>022</umask>

Set the file creation mode mask for the home directory. By default useradd will use 022. Check man 8 useradd and man 1 umask for further information.

Text

<groupname>users</groupname>

Required. It should be a valid group name. Check man 8 groupadd if you are not sure.

Number

<gid>100</gid>

Optional. Group ID. It must be a unique and non-negative number.

Text

<group_password>password</group_password>

Optional. The group's password can be written in plain text (not recommended) or in encrypted form. Check the encrypted to select the desired behavior.

Boolean

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

Optional. Indicates if the group's password in the profile is encrypted or not.

Users list

<userlist>bob,alice</userlist>

Optional. A list of users who belong to the group. User names must be separated by commas.

Boolean

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

Optional. Enables password-less login. It only affects graphical login.

Text

<autologin_user>alice</autologin_user>

Optional. Enables autologin for the given user.

Define a location from where the script gets fetched. Locations can be the same as for the profile (HTTP, FTP, NFS, etc.).

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

Either <location> or <source> must be defined.

The script itself (source code), encapsulated in a CDATA tag. If you do not want to put the whole shell script into the XML profile, use the location parameter.

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

Either <location> or <source> must be defined.

The file name of the script. It will be stored in a temporary directory under /tmp

<filename>mynitScript5.sh</filename>

Optional in case you only have a single init script. The default name (init-scripts) is used in this case. If having specified more than one init script, you must set a unique name for each script.

Normally, a script is only run once, even if you use ayast_setup to run an XML file multiple times. Change this default behavior by setting this boolean to true.

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

Optional. Default is false (scripts only run once).

Define a location from where the script gets fetched. Locations can be the same as for the control file (HTTP, FTP, NFS, etc.). Additionally a relative URL can be used that defines a path relative to the directory with the control file, using the syntax relurl://script.sh.

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

Either location or source must be defined.

The script itself (source code), encapsulated in a CDATA tag. If you do not want to put the whole shell script into the XML control file, refer to the location parameter.

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

Either location or source must be defined.

Specify the interpreter that must be used for the script. Supported options are shell and perl.

<interpreter>shell</interpreter>

Optional; default is shell.

The file name of the script. It will be stored in a temporary directory under /tmp.

<filename>myPreScript5.sh</filename>

Optional; default is the type of the script (pre-scripts in this case). If you have more than one script, you should define different names for each script. If filename is not defined and location is defined, the file name from the location path will be used.

If this boolean is true, output and error messages of the script (STDOUT and STDERR) will be shown in a pop-up. The user needs to confirm them via the OK button.

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

Optional; default is false.

This can be message, warning or error. Set the timeout for these pop-ups in the <report> section.

<feedback_type>warning</feedback_type>

Optional; if missing, an always-blocking pop-up is used.

If this is true, every single line of a shell script is logged. Perl scripts are run with warnings turned on. This only works for the deprecated keyword interpreter. For other languages, give the path to the interpreter as a parameter in the interpreter value, for example "<interpreter>ruby -w</interpreter>".

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

Optional; default is true.

This text will be shown in a pop-up for the time the script is running in the background.

<notification>Please wait while script is running...</notification>

Optional; if not configured, no notification pop-up will be shown.

It is possible to specify parameters given to the script being called. You may have more than one param entry. They are concatenated by a single space character on the script command line. If any shell quoting should be necessary (for example to protect embedded spaces) you need to include this.

<param-list config:type="list">
  <param>par1</param>
  <param>par2 par3</param>
  <param>"par4.1 par4.2"</param>
</param-list>

Optional; if not configured, no parameters get passed to script.

A script is only run once. Even if you use ayast_setup to run an XML file multiple times, the script is only run once. Change this default behavior by setting this boolean to true.

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

Optional; default is false, meaning that scripts only run once.

During installation, the new system is mounted at /mnt. If this parameter is set to false, AutoYaST does not run chroot and does not install the boot loader at this stage. If the parameter is set to true, AutoYaST performs a chroot into /mnt and installs the boot loader. The result is that to change anything in the newly-installed system, you no longer need to use the /mnt prefix.

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

Optional; default is false. This option is only available for chroot environment scripts.

The source code of the script. Whatever you echo to STDOUT will be used as default value for the ask-dialog. If your script has an exit code other than 0, the normal default element is used. Take care you use echo -n to suppress the \n and that you echo reasonable values and not “okay” for a boolean

<source>...</source>

This value is required, otherwise nothing would be executed.

The interpreter to use.

<interpreter>perl</interpreter>

The default value is shell. You can also set /bin/myinterpreter as value.

The file name of the script.

<filename>my_ask_script.sh</filename>

The default is ask_script.sh

The source code of the script. Together with rerun_on_error activated, you check the value that was entered for sanity. Your script can create a file /tmp/next_dialog with a dialog id specifying the next dialog AutoYaSTwill raise. A value of -1 terminates the ask sequence. If that file is not created, AutoYaST will run the dialogs in the normal order (since 11.0 only).

<source>...</source>

This value is required, otherwise nothing would be executed.

A boolean that passes the value of the answer to the question as an environment variable to the script. The variable is named VAL.

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

Optional. Default is false.

A boolean that turns on feedback for the script execution. STDOUT will be displayed in a pop-up window that must be confirmed after the script execution.

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

Optional, default is false.

A boolean that turns on debugging for the script execution.

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

Optional, default is true. This value needs feedback to be turned on, too.

A boolean that keeps the dialog open until the script has an exit code of 0 (zero). So you can parse and check the answers the user gave in the script and display an error with the feedback option.

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

Optional, default is false. This value should be used together with the feedback option.

Set to true if memory should be reserved and Kdump enabled.

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

required

Use the syntax of the crashkernel command line as discussed above.

<crash_kernel>256M:64M</crash_kernel>

A list of values is also supported.

<crash_kernel config:type="list">
  <listentry>72M,low</listentry>
  <listentry>256M,high</listentry>
</crash_kernel>

required

Exactly one e-mail address to which the e-mail should be sent. Additional recipients can be specified in KDUMP_NOTIFICATION_CC.

<KDUMP_NOTIFICATION_TO
>tux@example.com</KDUMP_NOTIFICATION_TO>

optional (notification disabled if empty)

Zero, one or more recipients that are in the cc line of the notification e-mail.

<KDUMP_NOTIFICATION_CC
>wilber@example.com suzanne@example.com</KDUMP_NOTIFICATION_CC>

optional

Host name of the SMTP server used for mail delivery. SMTP authentication is supported (see KDUMP_SMTP_USER and KDUMP_SMTP_PASSWORD) but TLS/SSL are not.

<KDUMP_SMTP_SERVER>email.suse.de</KDUMP_SMTP_SERVER>

optional (notification disabled if empty)

User name used together with KDUMP_SMTP_PASSWORD for SMTP authentication.

<KDUMP_SMTP_USER>bwalle</KDUMP_SMTP_USER>

optional

Password used together with KDUMP_SMTP_USER for SMTP authentication.

<KDUMP_SMTP_PASSWORD>geheim</KDUMP_SMTP_PASSWORD>

optional

Version string for the kernel used for Kdump. Leave it empty to use the auto-detection mechanism (strongly recommended).

<KDUMP_KERNELVER>2.6.27-default</KDUMP_KERNELVER>

optional (auto-detection if empty)

Additional command line parameters for the Kdump kernel.

<KDUMP_COMMANDLINE_APPEND>console=ttyS0,57600</KDUMP_COMMANDLINE_APPEND>

optional

Overwrite the automatically generated Kdump command line. Use with care. Usually, KDUMP_COMMANDLINE_APPEND should suffice.

<KDUMP_COMMANDLINE_APPEND>root=/dev/sda5 maxcpus=1 irqpoll</KDUMP_COMMANDLINE>

optional

true if the system should be rebooted automatically after the dump has been saved, false otherwise. The default is to reboot the system automatically.

<KDUMP_IMMEDIATE_REBOOT>true</KDUMP_IMMEDIATE_REBOOT>

optional

Bitmask that specifies how verbose the Kdump process should be. Read kdump(5) for details.

<KDUMP_VERBOSE>3</KDUMP_VERBOSE>

optional

Additional options that are passed to kexec when loading the Kdump kernel. Normally empty.

<KEXEC_OPTIONS>--noio</KEXEC_OPTIONS>

optional