Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 9/10 Installation Guide: Custom JumpStart and Advanced Installations |
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)
Important Information About Begin Scripts
Creating Derived Profiles With a Begin Script
Tracking Installation Duration With a Begin Script and Finish Script
Important Information About Finish Scripts
To Add Files With a Finish Script
Adding Packages or Patches With a Finish Script
Customizing the Root Environment With a Finish Script
Non-Interactive Installations With Finish Scripts
Creating Disk Configuration Files
SPARC: To Create a Disk Configuration File
SPARC: Disk Configuration File Example
x86: To Create a Disk Configuration File
x86: Disk Configuration File Example
Using a Site-Specific Installation Program
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
Instead of using the add_install_client command to specify the location of the custom JumpStart configuration files, you can specify the location of the files when you boot the system. However, you can only specify the name of one file. As a result, you must compress all of the custom JumpStart configuration files into one file.
For SPARC based systems, you specify the location of the file in the boot command
For x86 based systems, you specify the location of the files by editing the GRUB entry in the GRUB menu
The compressed configuration file can be one of the following types:
tar
Compressed tar
zip
bzip tar
# cd jumpstart_dir_path
Note - The compressed configuration file cannot contain relative paths. The custom JumpStart configuration files must be in the same directory as the compressed file.
The compressed configuration file must contain the following files:
Profile
rules
rules.ok
You can also include the sysidcfg file in the compressed configuration file.
The following example shows how to use the tar command to create a compressed configuration file that is named config.tar. The custom JumpStart configuration files are located in the /jumpstart directory.
Example 4-8 Creating a Compressed Configuration File
# cd /jumpstart # tar -cvf config.tar * a profile 1K a rules 1K a rules.ok 1K a sysidcfg 1K