| 7.4. System Configuration | ||
|---|---|---|
 | Chapter 7. The Auto-Installation Process |  |
| 7.4. System Configuration | ||
|---|---|---|
| | Chapter 7. The Auto-Installation Process | |
The system configuration during auto-installation can be seen as the most important part of the whole process. Customizing a system to your environment needs is what makes an auto-installation system attractive, not the installation part.
As you have seen in the previous chapters, almost anything can be configured automatically on the target system. In addition to the pre-defined directives, you can always use post-scripts to change other things in the system. Additionally you can change any system variables and if required, copy complete configuration files into the target system.
The Post-Installation and the System Configuration are initiated directly after the last package is installed in the target system and is continued after the system has booted for the first time.
Before the system is booted for the first time, YaST2 writes all data collected during installation into the system and finally it writes the boot loader in the specified location. In addition to these regular tasks, which are also done when performing a regular installation, YaST2 executes the chroot-scripts as specified in the control file. Note that these scripts are executed while the system is still not mounted.
If a different kernel than the default is installed, a hard reboot will be required. A hard reboot can also be forced during auto-installation, independent of the installed kernel. This can be accomplished using the reboot property of the general resource. (See General Options)
Most of the system customization is done in the second stage of the installation. YaST2 provides most of the important resources needed to bring up a system to a usable , general state. However, you may have other requirements for the installed system. If the required customizations can't be done using YaST2 resources, then the post-install scripts can be used to accomplish this task.
You can define an unlimited number of custom scripts in the control file either by editing the control file or by using the configuration system.
| |  | |
| 7.3. Invoking the Auto-Installation process |  | Appendix A. Handling Rules |