Ignite-UX Reference (March 2010, B3921-90005)

make_sys_image(1M) make_sys_image(1M)
y Yes, run the tests along with make_sys_image (this is the default).
n No, do not run the tests. This may be used on clients that the user knows
contain the patch.
o Run the tests only; that is, do not make a system image. It always exits and
returns a 4 if a patch exists that fixes a pax defect; a 3 if it is an enable-
ment patch (for example PAX-Enh on B.11.23); a 1 if the requested format
is not allowed on this system and a 0 if there are no pax patch(es) that the
system requires or could use.
p Run the tests only; prompt for cancel if a pax patch is required or could be
applied to the system. It always exits after the prompt, and returns the same
values as the o option exception if the patch(es) listed are non-enablement
patches it will return a 3 if the user answered [yY] to cancel.
−i Remove the bundle definition for the English language. This is useful only for
creating archives for use in multi-language or non-English installations where
the language specific parts of the core operating system are coming from
another source.
−p Preview mode; performs all of the checks and creates the command line, but
does not modify any files other than the make_sys_image.log.
−u Check the archive destination for sufficient storage capacity. The capacity of
raw devices is not easily checked, so this option has no effect in the case where
a raw device is the archive destination. The archive size is an approximation
and is generally 5% larger than the final archive. The default is to not check
capacity.
−v Verbose mode; writes all of the files that are being modified or removed and the
command line that will create the system archive to stdout.
−w log_file Write to the specified log file.
−x Print the list of files that will be set to the newconfig state and the files that
will be explicitly excluded using level 2 to both stdout and
/tmp/excluded_files. This doesn’t include files excluded because they
are sockets, named pipes, the local archive destination or on remote file sys-
tems. If the -f option is used, the output will reflect the effects of that file.
With this option selected, no archiving action is taken.
−L Create a copy of any non-standard LIF files (as defined for both whole and
LVM disks) found on the boot disk. The boot disk that is used is taken from the
first non-commented line in the /stand/bootconf file. The LIF volume
for storing these LIF files is /usr/lib/ignite_bootlif, and is created
only if non-standard LIF files are present. This option creates only the backup
file. Without this option, the backup, if needed, is created and the recovery
media is created with this information stored for later recovery. For more infor-
mation on the disks, LIF files, and LIF volume creation, see bootconf (4), lif (4),
mkboot(1M), and lifinit(1). The main purpose of this option is to allow LIF
diagnostics and any changes to the AUTO LIF file to be saved by the Ignite-UX
recovery commands (see make_net_recovery(1M)).
-? Display the help screen.
NOTE: If all of the defaults are used, a gzip compressed tar archive of the system with all of the host
and network information removed will be placed on the Ignite-UX server in /var/tmp/myhost.gz.
Environment Variables
Environment variables are to be on separate lines following the env_vars+=
keyword in the Ignite-UX
configuration file, *INSTALLFS.
3