|
|||
1. Where to Find Solaris Installation Planning Information 2. Custom JumpStart (Overview) 3. Preparing Custom JumpStart Installations (Tasks) 4. Using Optional Custom JumpStart Features (Tasks) 5. Creating Custom Rule and Probe Keywords (Tasks) 6. Performing a Custom JumpStart Installation (Tasks) 7. Installing With Custom JumpStart (Examples) x86: Create a Boot Server for Marketing Systems SPARC: Create the Engineering Group's Profile x86: Create the Marketing Group's Profile SPARC: Set Up Engineering Systems to Install From the Network x86: Set Up Marketing Systems to Install From the Network SPARC: Boot the Engineering Systems and Install Solaris Software x86: Boot the Marketing Systems and Install Solaris Software 8. Custom JumpStart (Reference) |
Update the rules FileNow you must add rules to the rules file. The Solaris installation program uses the rules to select the correct installation (profile) for each system during a custom JumpStart installation. At this site, each department is located on its own subnet and has its own network address. The engineering department is located on subnet 255.222.43.0. The marketing department is located on 255.222.44.0. You can use this information to control how the engineering and marketing systems are installed with the Solaris Express 5/07 software. In the /jumpstart directory, you edit the rules file, delete all of the example rules, and add the following lines to the file: network 255.222.43.0 - eng_prof - network 255.222.44.0 - marketing_prof - Basically, these rules state that systems on the 255.222.43.0 network are to be installed with the Solaris Express 5/07 software by using the eng_prof profile. The systems on the 255.222.44.0 network are to be installed with the Solaris Express 5/07 software by using the marketing_prof profile. Note - You can use the sample rules to use a network address to identify the systems to be installed with the Solaris Express 5/07 software by using eng_prof and marketing_prof, respectively. You can also use host names, memory size, or model type as the rule keyword. Table 8-1 contains a complete list of keywords you can use in a rules file. |
||
|