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

make_sys_image(1M) make_sys_image(1M)
NAME
make_sys_image − create compressed file archive of a running system
SYNOPSIS
/opt/ignite/data/scripts/make_sys_image -s IP | hostname | local
[ -d directory | device ][-f file][-l 1 | 2][-n filename ][-r remsh_user ][-m c | t | p]
[ -c z | g | n ][-a archive_size ][-R ][-g file_list ][-t y|n|o|p][-i ][-p ][-u ][-v ]
[ -w log_file ][-x ][-L ][-? ]
DESCRIPTION
make_sys_image is used to create a system archive of a running single-user or multi-user system. This
archive may be in cpio, pax, or tar format, and may be compressed with either compress or
gzip. make_sys_image may be called as a post_config_script by Ignite-UX as part of the
installation process, or invoked at the command line on a running system. The archive may be written to a
file, a tape, or a raw disk device on a remote or the local system. If the archive destination is a remote sys-
tem, that system must have a .rhosts entry for the local system, or an NFS mount available. The
options for this command may be a combination of command line arguments and environment variables
passed in with the Ignite-UX configuration file via the env_vars keyword.
The archives created by make_sys_image are designed for use with Ignite-UX as part of an archive-
based ignition process. Before the archive is used for installing systems, the file system impacts of the
archive must be obtained. See archive_impact(1M). make_sys_image does not capture file system or
disk layout information. Use save_config to capture this information. For details on integrating the
script into the GUI, see manage_index(1M) for /var/opt/ignite/data/INDEX. For details on
using the script non-interactively, see instl_adm(4) for information on the post_config_script and
env_vars keywords.
Options
The make_sys_image command recognizes the following options:
−s IP|hostname|local
IP address or resolvable hostname of the server to send the archive to or local if
the destination is a local file system, NFS mount, disk or tape. If the destina-
tion is not local, permission to remotely access the server is required. If a host-
name is used in this case, it must be resolvable through whatever means the
name service switch is set to use (see switch(4) for more information).
−d directory|device
Destination directory (for example, /var/tmp/foo) or device file name (for exam-
ple, /dev/rmt/0m). The default is /var/tmp/.
Note: Archives written to tape or raw disk cannot be used directly; they must
first be extracted using dd onto a file system where they may be accessed by
an Ignite-UX server. To use a directory that is an NFS mount point on the
local system, use -s local to specify the server destination.
−f file File contains a user-defined list of files to be reset to the newconfig state or
ignored altogether. This list may be in addition to the default level 2 behav-
iors, or it may replace the default level 2 reset and/or ignore behaviors.
The file may have one or two sections headed by the keywords RESET or
NO_ARCHIVE. Following each keyword are the paths of files or directories
(one per line), or regular expressions that describe the files or directories. Each
keyword may be combined with the ONLY keyword. If the ONLY keyword is
used, the files in that section replace the default level 2 behavior. The keyword
lines must begin with a ’+’, and each keyword (except ONLY) must occur only
once in the file. The keywords are case sensitive and must be in all uppercase
letters. This option overrides the −l option and sets the level to 2.
1