Chapter 4. Configuration and Installation Options

Table of Contents

4.1. General Options
4.2. Reporting
4.3. The Boot loader
4.4. Partitioning
4.4.1. drive configuration
4.4.2. partition configuration
4.4.3. raid options
4.4.4. Automated Partitioning
4.4.5. Advanced Partitioning features
4.4.5.1. Wipe out partition table
4.4.5.2. Mount Options
4.4.5.3. Keeping Specific Partitions
4.4.6. Using existing mount table (fstab)
4.4.7. Logical Volume Manager (LVM)
4.4.8. Enterprise Volume Management System (EVMS)
4.4.9. Software RAID
4.5. Software
4.5.1. Package Selections with patterns
4.5.2. Installing additional and customized Packages
4.5.3. Kernel packages
4.5.4. Removing automatically selected packages
4.5.5. Installing packages during stage 2
4.6. Services and Run-levels
4.7. Network configuration
4.7.1. Network devices, DNS and Routing.
4.7.2. Proxy
4.7.3. (X)Inetd
4.7.4. NIS
4.7.5. LDAP client
4.7.6. NFS Client and Server
4.7.7. NTP Client
4.8. Mail Configuration (Sendmail or Postfix)
4.9. Security settings
4.9.1. Password Settings Options
4.9.2. Boot Settings
4.9.3. Login Settings
4.9.4. New user settings (useradd settings)
4.10. Monitor and X11 Configuration
4.11. Users
4.12. Custom user scripts
4.12.1. Pre-Install Scripts
4.12.2. Chroot environment scripts
4.12.3. Post-Install Scripts
4.12.4. Init Scripts
4.12.5. Script example
4.13. System variables (Sysconfig)
4.14. Adding complete configurations
4.15. Miscellaneous hardware and system components
4.15.1. Printer
4.15.2. Sound devices
4.16. Ask the user for values during installation

This chapter introduces important parts of a control file for standard purposes. To have an idea about the other options available, 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 those have to be added to the individual package selection.

YaST will install packages required by YaST modules in the second phase of the installation and before the post-installation phase of AutoYaST has started, however if the YaST modules are not available in the system, this will not happen. For example, no security settings will be configured if yast2-security is not installed.

4.1.  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

  

    <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>
    </general>


	  
	

By default, the auto-installation process has to be confirmed by the user. The confirmation should be disabled if a fully unattended installation is desired. This option is used to view and change the settings on a target system before anything is committed and can be used for debugging. It is set to true by default to avoid recursive installs when the system schedules a reboot after initial system setup.

With halt you make autoyast to turn off the machine after all packages have been installed. So instead of the 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 are new with openSUSE 11.0 and SLES11. You can reboot or halt the machine, when everything with installation and configuration is done, with that.

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. true will reboot, false will not reboot and a missing forceboot option uses the products default.

[Note]Change starting from 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. So don't use them in the general section anymore.

Since now you can use the second_stage property, which can turn off autoyast after the first reboot. So the complete second stage is a manual installation (default is true, which means that autoyast is doing a complete installation). Since openSUSE 11.0 you can set the boolean final_reboot and final_halt to reboot/turn off the machine at the end of stage two.

For the signature-handling, please read the Software chapter of this documentation.