Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Installation Guide: Custom JumpStart and Advanced Installations Oracle Solaris 10 8/11 Information Library |
1. Where to Find Oracle Solaris Installation Planning Information
2. Custom JumpStart (Overview)
3. Preparing Custom JumpStart Installations (Tasks)
Task Map: Preparing Custom JumpStart Installations
Creating a Profile Server for Networked Systems
To Create a JumpStart Directory on a Server
Allowing All Systems Access to the Profile Server
To Allow All Systems Access to the Profile Server
Creating a Profile Diskette for Standalone Systems
SPARC: To Create a Profile Diskette
x86: To Create a Profile Diskette With GRUB
To Create a Temporary Oracle Solaris Environment to Test a Profile
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)
8. Custom JumpStart (Reference)
9. Installing a ZFS Root Pool With JumpStart
Before you can use a profile and rules file, you must run the check script to validate that the files are set up correctly. If all rules and profiles are correctly set up, the rules.ok file is created, which is required by the custom JumpStart installation software to match a system to a profile.
Table 3-2 describes what the check script does.
Table 3-2 What Happens When You Use the check Script
|
$ ./check -p path -r file_name
Validates the rules by using the check script from the Oracle Solaris software image instead of the check script from the system you are using. path is the image on a local disk or a mounted Oracle Solaris Operating System DVD or a Oracle Solaris Software - 1 CD.
Use this option to run the most recent version of check if your system is running a previous version of Oracle Solaris.
Specifies a rules file other than the one that is named rules. Using this option, you can test the validity of a rule before you integrate the rule into the rules file.
As the check script runs, the script reports the checking of the validity of the rules file and each profile. If no errors are encountered, the script reports the following information.
The custom JumpStart configuration is ok
See Also
After you validate the rules file, you can learn more about optional custom JumpStart features in Chapter 4, Using Optional Custom JumpStart Features (Tasks). You can learn about performing custom JumpStart installations in Chapter 6, Performing a Custom JumpStart Installation (Tasks).