pfinstall(1M)
NAME
pfinstall − tests installation profiles
SYNOPSIS
/usr/sbin/install.d/pfinstall −D | −d disk_config [ −c path ] profile [ rootdisk ]
DESCRIPTION
When the initial_install argument is defined in a profile, you can use the pfinstall command to test the profile without performing an actual installation. pfinstall enables you to test a profile by using either:
• The disk configuration on the system where pfinstall is being run.
• A disk configuration file created by the prtvtoc(1M) command. For example, disk configuration files enable you to test profiles for all the different systems on your network from one system.
pfinstall is available only on a system running the Solaris 2.x environment.
OPTIONS
−D pfinstall uses the system’s disk configuration to test the profile. You must be root to execute the pfinstall command with the −D option.
−d disk_config pfinstall uses a disk configuration file, disk_config, to test the profile. A disk configuration file can be created by using the prtvtoc(1M) command.
−c path The path to the Solaris 2.x installation image. This is required if the image is not mounted on /cdrom. (For example, use this option if you copied the installation image to disk or mounted the CD-ROM on a directory other than /cdrom.)
profile The file name of the profile to test.
rootdisk A disk’s device name that specifies where to install the root (/) file system. Must be in the form cXtXdX.
You should run pfinstall from the directory where the profile and disk_config files reside (such as the profile directory). If the profile or disk_config file is not in the directory where pfinstall is run, you must specify the path to the particular file.
EXAMPLES
The following examples use pfinstall to test the marketing profile:
example% /usr/sbin/install.d/pfinstall −D marketing
example% /usr/sbin/install.d/pfinstall −d 104_test marketing
example% /usr/sbin/install.d/pfinstall −D −c /export/install marketing
SEE ALSO
WARNINGS
If the −d or −D option is not specified, pfinstall will perform an actual installation on the system by using the specified profile, and the data on the system will be overwritten.
NOTES
To create a disk configuration file:
1. Locate a system with the disk size needed for testing a particular profile.
2. Determine the device name for the system’s disk.
3. Redirect the output of prtvtoc(1M) to create the disk configuration file:
example% prtvtoc /dev/rdsk/device_name > disk_config
Where
/dev/rdsk/device_name is the device name of the system’s disk (in the form cXtXdX s2 )
disk_config is the disk configuration file name.
The following example creates a disk configuration file, 104_test, on a system with a 104-Mbyte disk, whose device name is c0t3d0:
example% prtvtoc /dev/rdsk/c0t3d0s2 > 104_test
You can also create a disk configuration file that includes multiple disks. In the following example, a disk configuration file is created that includes two, 104-Mbyte disks. When creating disk configuration files with multiple disks, it is important to make sure that each disk in the file is specified with a different target.
example% cat 104_test 104_test > dual104_test
To test a profile with a specific system memory size, set SYS_MEMSIZE to the specific memory size (in Mbytes) before running pfinstall:
# SYS_MEMSIZE=memory_size
# export SYS_MEMSIZE
SunOS 5.5/SPARC — Last change: 27 July 1993