Locate a system on which to test the profile.
Test an initial installation profile on a system that is running at least the Solaris 10 1/06 software.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
Create a temporary mount point.
# mkdir /tmp/mnt
Mount the directory that contains the profile or profiles that you want to test. Type the instructions that apply.
# SYS_MEMSIZE=memory-size # export SYS_MEMSIZE
Depending on whether you mounted a directory in Step 4, do one of the following:
Test the profile.
# /usr/sbin/install.d/pfinstall -D:-d disk-config-file -c path profile
You must include the -d option or the -D option when using the pfinstall command. If you do not include one of these options, the command uses the profile you that specify for installing the Solaris software. As a result, all of the system data is overwritten.
pfinstall uses the current system's disk configuration to test the profile.
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.
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.
The path to the Solaris software image. You use this option, for example, if the system is using Solaris Volume Manager to mount the Solaris Software - 1 CD for your platform.
The -c option is not required if you booted from at least the Solaris 10 1/06 DVD or the Solaris 10 1/06 Software - 1 CD image for your platform. The DVD or CD image is mounted on /cdrom as part of the booting process.
The name of the profile to test. If profile is not in the directory where pfinstall is being run, you must specify the path.