Slide 16 of 18
Notes:
Normally, the install server also provides the boot program for booting install clients. But if the install client is on a different subnet, you need a system with just enough information to boot an install client over the network.
If your site uses NIS or NIS+ you can have default values set in the name service for date and time, time zone, site netmask, and the language-specific version of Solaris provided for the sysidtool program. Otherwise you’ll be forced to specify this for each system install .
The profile server has the rules file and the set of profiles, all in the JumpStart directory which is nfs exported.
The rules file is text file lookup table that defines how clients are installed, based on their system attributes. The file is read from the first line to the first complete match, which is used. The entry specifies the begin script, profile for install, and finish script used for the install.
The profile files are the templates used during the install. It defines how the install software should install the Solaris software on an install client. Standalone/server/dataless install, disk and filesystem layout, what software clusters/packages, swap configuration and much else.
The begin and finish scripts is where the true site customization installs begins. These scripts allow admin tasks to be automated for modifications, patch installs, custom software installs, and whatever else you can dream up.
