Tasks to Set up Custom JumpStart Installations

Creating a JumpStart directory on a diskette or on a server  

You must create a JumpStart directory to hold the custom JumpStart files. If you are going to use a diskette for custom JumpStart installations, see "Creating a JumpStart Directory on a Diskette ". If you are going to use a server for custom JumpStart installations, see "Creating a JumpStart Directory on a Server".

Enabling all clients to access the JumpStart directory 

When you use a server to provide the JumpStart directory, you can enable all clients to access the JumpStart directory. See "Enabling Access to the JumpStart Directory" for detailed information.

Creating profiles  

A profile is a text file used as a template by the custom JumpStart installation software. It defines how to install the Trusted Solaris software on a workstation (for example, initial installation option, system type, disk partitioning, software group), and it is named in the rules file. See "Creating a Profile" for detailed information.

Creating a rules file

The rules file is a text file used to create the rules.ok file. The rules file is a look-up table consisting of one or more rules that define matches between system attributes and profiles. See "Creating the rules File" for detailed information.

Using check to validate the rules file

The rules.ok file is a generated version of the rules file, and it is required by the custom JumpStart installation software to match a workstation to a profile. You must use the check script to create the rules.ok file. See "Using check to Validate the rules File" for detailed information.