Customizing Files

When you customize the files, either the template files or the host files, there are some parts that must be copied exactly from the original files.

Customizing Template Files

BMI template files belong to a specific architecture-distribution. Modifying the files affects all future system provisioning for that distribution.

When you change or add a template file, you must copy the macros from the original file in the exact text and order.

Customizing Host Files

A host file affects the installation and provisioning of one system. To ensure consistency, copy your customized files to every relevant /MAC-address/ directory.

The kickstart host file is the BMI name for the file created with either Kickstart or YaST. In the kickstart file there is a post section containing data that leads the installation of the Sun Update Connection – Enterprise agent and notifies the BMI server of successful provisioning. The post-install section must be copied exactly into all your customized files.

To Create Customized Template Files

1. Maintain the default template files for copying and backup:

   # cd /tftpboot/images/TYPE/ARCH/DISTRO # mv kickstart kickstart.orig # mv netboot netboot.orig

2. Maintain the default host files for copying and backup:

   # cd /tftpboot/pxelinux.cfg/MAC-address/ # mv kickstart kickstart.orig # mv netboot netboot.orig

3. In either or both directories, make another copy for customization:

   # cp kickstart.orig kickstart.significant-suffix # cp netboot.orig netboot.significant-suffix

4. Change the files as needed:

   • If you change a template file, make sure the macro lines are exactly as in the original template file, in the same order and the same text.

   • If you change a host file, make sure your host file has the post-install section copied exactly, in the same location in the file as in the original host file.

   • If you want to keep multiple versions of a file, give each version a different suffix and make sure to copy over the needed macros or post-install section.

5. Decide which version will be used for the next BMI server session. Make a backup of this file. This is important, because if any user changes the configuration through the BMI Server Setup feature, your active files will be overwritten.

6. Create a symlink for the BMI server to find the files that you want to use for the next BMI provisioning session:

   # ln -s kickstart.your-suffix kickstart # ln -s netboot.your-suffix netboot

Example 2–1 Symlink For the BMI Server

kickstart.orig
kickstart.myServers
kickstart.myWorkstations_partA
kickstart.myWorkstations_partB
kickstart.myWorkstations_partA_backup
kickstart -> kickstart.myWorkstations_partA