To Test a Profile

If you are using the locale keyword, the pfinstall -D command fails to test the profile. For a workaround, see the error message “could not select locale,” in the section, Upgrading the Solaris OS.

1. Locate a system on which to test the profile that is the same type of platform, SPARC or x86, for which the profile was created.

   If you are testing an upgrade profile, you must test the profile on the actual system that you intend to upgrade.

2. Use the following decision table to determine what to do next.

   Test Scenario	Instructions
   Test an initial installation profile and have a system that is running the Solaris 10 11/06 software.	Become superuser on the system and go to Step 5.
   Test an upgrade profile, or you do not have a system that is running Solaris 10 11/06 to test an initial installation profile.	Create a temporary Solaris 10 11/06 environment to test the profile. For details, see To Create a Temporary Solaris Environment to Test a Profile. Then, go to Step 3.

3. Create a temporary mount point.

   # mkdir /tmp/mnt

4. Mount the directory that contains the profile or profiles that you want to test.

   Mount Scenario	Typing Instructions
   Mount a remote NFS file system for systems on the network.	mount -F nfs server_name:path /tmp/mnt
   SPARC: Mount a UFS-formatted diskette.	mount -F ufs /dev/diskette /tmp/mnt
   Mount a PCFS-formatted diskette.	mount -F pcfs /dev/diskette /tmp/mnt

5. 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

6. Did you mount a directory in Step 4?

   • If yes, change the directory to /tmp/mnt.

     # cd /tmp/mnt

   • If no, change the directory to where the profile is located, which is usually the JumpStart directory.

     # cd jumpstart_dir_path

7. Test the profile with the pfinstall(1M) command.

   # /usr/sbin/install.d/pfinstall -D:-d disk_config_file -c path profile

   ---

   Caution –

   You must include the -d or -D option. If you do not include one of these options, pfinstall uses the profile you specify to install the Solaris software. All of the data on the system is overwritten.

   ---

   -D

   pfinstall uses the current system's disk configuration to test the profile. You must use the -D option to test an upgrade profile.

   -d disk_config_file

   pfinstall uses the disk configuration file, disk_config_file, to test the profile. If disk_config_file is not located in the directory where pfinstall is run, you must specify the path.

   For instructions about how to create a disk configuration file, see Creating Disk Configuration Files.

   ---

   Note –

   You cannot use the -d disk_config_file option with an upgrade profile, install_type upgrade. You must always test an upgrade profile against a system's disk configuration, that is, you must use the -D option.

   ---

   -c path

   The path to the Solaris software image. You use this option, for example, if the system is using Volume Manager to mount the Solaris Software - 1 CD for your platform.

   ---

   Note –

   The -c option is not required if you booted from a Solaris Operating System DVD or a Solaris Software - 1 CD image for your platform. The DVD or CD image is mounted on /cdrom as part of the booting process.

   ---

   profile

   The name of the profile to test. If profile is not in the directory where pfinstall is being run, you must specify the path.