Locate a system to test the profile that has the same platform type (x86 or SPARC) for which the profile was created.
If you are testing an upgrade profile, you must use the system that you are going to upgrade.
Determine the next step based on your situation.
If You ... |
Then ... |
---|---|
Need to test an initial installation profile and have a system running Solaris 2.6 |
Become superuser on the system and go to Step 9. |
Need to test an upgrade profile, or you don't have a system running Solaris 2.6 to test an initial installation profile |
Go to Step 3. |
Boot the system from a Solaris 2.6 image (just as you would to install), which can be located in the system's local CD-ROM or on an install server.
See Chapter 2, Performing an Interactive Installation for details on booting.
If you are testing an upgrade profile, boot the system that you are going to upgrade.
Answer the system identification questions, if prompted.
If you are presented with a choice of installation options, choose the Solaris Interactive Installation program.
Exit from the first screen of the Solaris interactive installation program.
After the Solaris interactive installation program exits, a shell prompt displays.
Create a temporary mount point.
# mkdir /tmp/mnt |
Mount the directory that contains the profile(s) you want to test.
If You Want To ... |
Then Type ... |
|
---|---|---|
Mount a remote NFS file system (for systems on the network) |
|
|
Mount a UFS-formatted diskette |
|
|
Mount a PCFS-formatted diskette |
|
To test the profile with a specific system memory size, set SYS_MEMSIZE
to the specific memory size in Mbytes.
# SYS_MEMSIZE=memory_size # export SYS_MEMSIZE |
Change directory to where the profile resides, which is usually the JumpStart directory.
If you mounted a directory in Step 8, change directory to /tmp/mnt.
# cd jumpstart_dir_path |
Test the profile with the pfinstall -d or pfinstall -D command.
Without the -d or -D option, pfinstall will perform an actual installation of the Solaris software on the system by using the specified profile, and the data on the system will be overwritten.
# /usr/sbin/install.d/pfinstall -D | -d disk_config [-c path] profile |
Tells pfinstall to use the current system's disk configuration to test the profile against. |
|
Tells pfinstall to use a disk configuration file, disk_config, to test the profile against. If disk_config file is not in the directory where pfinstall is run, you must specify the path. This option cannot be used with an upgrade profile (install-type upgrade). You must always test an upgrade profile against a system's disk configuration (-D option). |
|
Is the path to the Solaris CD image. This is required if the Solaris CD is not mounted on /cdrom. For example, use this option if the system is using Volume Management to mount the Solaris CD. Note - This option is not required if you have booted from a Solaris CD image, because the Solaris CD image is mounted on /cdrom as part of the booting process. |
|
profile |
Is the name of the profile to test. If profile is not in the directory where pfinstall is being run, you must specify the path. |
You have completed testing the profile. To continue, see "Validating the rules File".
The following example tests the basic_prof profile against the disk configuration on a Solaris 2.6 system where pfinstall is being run. The basic_prof profile is located in the /jumpstart directory and the path to the Solaris CD image is specified because Volume Management is being used.
# cd /jumpstart # /usr/sbin/install.d/pfinstall -D -c /cdrom/cdrom0/s0 basic_prof |
The following example tests the basic_prof profile against the 535_test disk configuration file and 64 Mbytes of system memory. This example uses a Solaris CD image located in the /export/install directory, and pfinstall is being run on a Solaris 2.6 system.
# SYS_MEMSIZE=64 # export SYS_MEMSIZE # /usr/sbin/install.d/pfinstall -d 535_test -c /export/install basic_prof |