Chapter 4. Configuration and Installation Options

Table of Contents

General Options
Reporting
The Boot Loader
Device map
Globals
Initrd modules
Loader Type
Sections
Options
Partitioning
Drive Configuration
Partition Configuration
RAID Options
Automated Partitioning
Advanced Partitioning Features
Using Existing Mount Table (fstab)
Logical Volume Manager (LVM)
Enterprise Volume Management System (EVMS) — SLES10 only!
Software RAID
IBM System z Specific Configuration
Software
Package Selections with Patterns
Deploying Images
Installing Additional and Customized Packages
Kernel Packages
Removing Automatically Selected Packages
Installing Packages in Stage 2
Installing Patterns in Stage 2
Online Update in Stage 2
Services and Runlevels
Network Configuration
Network Devices, DNS and Routing.
Proxy
(X)Inetd
NIS
LDAP Client
NFS Client and Server
NTP Client
Mail Configuration (Sendmail or Postfix)
Security Settings
Password Settings Options
Boot Settings
Login Settings
New user settings (useradd settings)
Monitor and X11 Configuration
Users
Custom User Scripts
Pre-Install Scripts
Postpartitioning Scripts
Chroot Environment Scripts
Post-Install Scripts
Init Scripts
Script Example
System Variables (Sysconfig)
Adding Complete Configurations
Ask the User for Values during Installation
Kernel Dumps
Memory Reservation
Dump Saving
Email Notification
Kdump Kernel Settings
Expert Settings
Miscellaneous Hardware and System Components
Printer
Sound devices

This chapter introduces important parts of a control file for standard purposes. To learn about other available options, use the configuration management system.

Note that for some of the configuration options to work, additional packages have to be installed, depending on the software selection you have configured. If you choose to install Minimal then some packages might be missing and have to be added to the individual package selection.

YaST will install packages required in the second phase of the installation and before the post-installation phase of AutoYaST has started. However, if necessary YaST modules are not available in the system, important configuration steps will be skipped. For example, no security settings will be configured if yast2-security is not installed.

General Options

General options include all the settings related to the installation process and the environment of the installed system.

Example 4.1. General Options

The mode section configures the behavior of AutoYaST with regard to confirmation and rebooting. The following has to be in the <general><mode> section.

By default, the user must confirm the auto-installation process. This option allows the user to view and change the settings for a target system before they are committed and can be used for debugging. confirm is set to "true" by default to avoid recursive installs when the system schedules a reboot after initial system setup. Only disable confirmation if you want to carry out a fully unattended installation.

With halt you cause AutoYaST to shut down the machine after all packages have been installed. Instead of a reboot into stage two, the machine is turned off. The bootloader is alreay installed and all your chroot scripts have run.

final_halt and final_reboot have been introduced with openSUSE 11.0 and SLES11. You can reboot or halt the machine after installation and configuration are finished at the end of stage 2.

openSUSE 11.0 uses the kexec feature and does not reboot anymore between stage1 and stage2. With the forceboot option you can force the reboot in case you need it for some reason. The value "true" will reboot, "false" will not reboot and a missing forceboot option uses the product's default.


    <general>
      <signature-handling>
        <accept_unsigned_file         config:type="boolean">true</accept_unsigned_file>
        <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum>
        <accept_verification_failed   config:type="boolean">true</accept_verification_failed>
        <accept_unknown_gpg_key       config:type="boolean">true</accept_unknown_gpg_key>
        <import_gpg_key               config:type="boolean">true</import_gpg_key>
        <accept_non_trusted_gpg_key   config:type="boolean">true</accept_non_trusted_gpg_key>
      </signature-handling>
      <mode>
        <halt config:type="boolean">false</halt>
        <forceboot config:type="boolean">false</forceboot>     <! -- since 11.0 -->
        <final_reboot config:type="boolean">false</final_reboot>   <! -- since 11.0 -->
        <final_halt config:type="boolean">false</final_halt>       <! -- since 11.0 -->
        <confirm config:type="boolean">true</confirm>
        <second_stage config:type="boolean">true</second_stage>
      </mode>
      <proposals config:type="list">        <!-- since 11.1 -->
        <proposal>partitions_proposal</proposal>
      </proposals>
      <wait>  <!-- since 11.1 / SLES11 -->
          <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>
                          sleep 5
                      </source>
                      <debug config:type="boolean">false</debug>
                  </script>
              </module>
          </pre-modules>
          <post-modules config:type="list">
              <module>
                  <name>networking</name>
                  <sleep>
                      <time config:type="integer">3</time>
                      <feedback config:type="boolean">true</feedback>
                  </sleep>
                  <script>
                      <source>
                          sleep 7
                      </source>
                      <debug config:type="boolean">false</debug>
                  </script>
              </module>
          </post-modules>
      </wait>

      <!-- the storage section was invented with openSUSE 11.3 and SLES11 SP2 -->
      <storage>
        <!--
            partition_alignment:

            `align_optimal  - That's the default. Partitions are aligned like the kernel suggests.
                              This can lead to problem with some machines/bioses that are unable to boot with that
                              alignment
            `align_cylinder - that's the alignment like it was in pre-openSUSE 11.3 time for years. Partitions
                              always start on a cylinder boundary
        -->
        <partition_alignment config:type="symbol">align_cylinder</partition_alignment>
      </storage>

    </general>



AutoYaST in openSUSE 11.1 allows you to configure the proposal screen with the <proposals config:type="list"> option in the profile. All proposals that are listed in that section are shown in the proposal screen if you set the confirm option to "true".

This is the proposal list openSUSE 11.1, which you can also find in the control.xml file on the installation source:

  • partitions_proposal

  • bootloader_proposal

  • country_simple_proposal

  • timezone_proposal

  • users_proposal

  • hwinfo_proposal

  • mouse_proposal

  • software_proposal

  • runlevel_proposal

  • deploying_proposal

The wait section has been introduced with openSUSE 11.1 and SLES11. You can let AutoYaST sleep before and after each module run during the second stage. You can run scripts and/or pass a value (in seconds) for AutoYaST to sleep. In the example above AutoYaST will sleep for 15 seconds (10+5) before the network configuration starts and 10 seconds (3+7) after the network configuration is done. The scripts in the example don't really make a lot of sense because you could pass that value as "time" value too. They are only used to show how scripts in the wait section work now.

[Note]Changes since SUSE Linux 10.1/SLES10

The language, keyboard and clock properties in the general resource were moved to the root (profile) element of the autoyast profile. Do not use them in the general section anymore.

Now you can use the second_stage property to turn off AutoYaST after the first reboot (set to "false"). Then the complete second stage is a manual installation. Default is "true", which means AutoYaST is doing a complete installation. Since openSUSE 11.0 you can set the boolean final_reboot and final_halt to reboot or turn off the machine at the end of stage 2.

For signature handling, read the the section called “ Software ”.