|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations Oracle Solaris 10 1/13 Information Library|
When setting up JumpStart installations for systems on the network, you need to create a JumpStart directory on a server. The JumpStart directory contains all of the essential JumpStart files, for example, the rules file, rules.ok file, and profiles. You must save the JumpStart directory in the root (/) directory of the profile server.
The server that contains a JumpStart directory is called a profile server. A profile server can be the same system as an install server or a boot server, or the server can be a completely different server. A profile server can provide JumpStart files for different platforms. For example, an x86 server can provide JumpStart files for both SPARC based systems and x86 based systems.
Note - After you create a profile server, you must allow systems to access the server. For detailed instructions, see Using a Wildcard Entry to Allow All Systems Access to the Profile Server.
Note - This procedure assumes that the system is running Solaris Volume Manager. If you are not using Solaris Volume Manager to manage discs, refer to System Administration Guide: Devices and File Systems for detailed information about managing removable media without Solaris Volume Manager.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
# mkdir -m 755 jumpstart-dir-path
In the command, jumpstart-dir-path is the absolute path of the JumpStart directory.
For example, the following command creates a directory that is called jumpstart in the root (/) directory and sets the permissions to 755:
# mkdir -m 755 /jumpstart
share -F nfs -o ro,anon=0 jumpstart-dir-path
For example, the following entry shares the /jumpstart directory:
share -F nfs -o ro,anon=0 /jumpstart
# cp -r media-path/Solaris_10/Misc/jumpstart_sample/* jumpstart-dir-path
The path to the CD, DVD, or image on the local disk
The path on the profile server where you are placing the example JumpStart files
For example, the following command copies the jumpstart_sample directory into the /jumpstart directory on the profile server:
cp -r /cdrom/cdrom0/Solaris_10/Misc/jumpstart_sample/* /jumpstart
For detailed instructions, see Using a Wildcard Entry to Allow All Systems Access to the Profile Server.
When you create a profile server, you must ensure that systems can access the JumpStart directory on the profile server during a JumpStart installation. Use one of the methods described in the following table to ensure access.
In the /etc/bootparams file
In the naming service bootparams database
The systems must be of the same type, such as all SPARC systems.
Add the following entry to the file or database:
The host name of the profile server where the JumpStart directory is located
The absolute path of the JumpStart directory
For example, the following entry enables all systems to access the /jumpstart directory on the profile server that is named sherlock:
Caution - Use of this procedure might produce the following error message when an installation client is booted:
WARNING: getfile: RPC failed: error 5: (RPC Timed out).
Booting From the Network, Error Messages in Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations contains details about this error message.
All systems can now access the profile server.