Creating a Compressed Configuration File

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, a feature of Oracle Solaris, menu

The compressed configuration file can be one of the following types:

• tar

• Compressed tar

• zip

• bzip tar

To Create a Compressed Configuration File

1. Change the directory to the JumpStart directory on the profile server.

   # cd jumpstart_dir_path

2. Use a compression tool to compress the custom JumpStart configuration files into one file.

   ---

   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.

3. Save the compressed configuration file on an NFS server, an HTTP server, or on a local hard disk.

Compressed Configuration File Example

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