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

make_boot_tape(1M) make_boot_tape(1M)
NAME
make_boot_tape − make a bootable tape to connect to an Ignite-UX server
SYNOPSIS
/opt/ignite/bin/make_boot_tape [ -d device_file_for_tape]
[ -f configuration_file][-t tmp_directory][-v ][-? ]
/opt/ignite/bin/make_boot_tape [ -d device_file_for_tape][-g gateway ][-m netmask ]
[ -t tmp_directory][-v ][-? ]
DESCRIPTION
The tape created by make_boot_tape is a bootable tape that contains just enough information to boot a
PA-RISC system and connect to the Ignite-UX server where the tape was created. Once the target system
has connected with the Ignite-UX server, it may be installed or recovered using Ignite-UX. The tape is not
a fully self-contained install tape; an Ignite-UX server must also be present. The configuration information
and software to be installed on the target machine reside on the Ignite-UX server, not on the tape. If you
need to build a fully, self-contained recovery tape, see make_tape_recovery(1M) or make_medialif (1M).
make_boot_tape is used in situations when you have target machines that cannot boot via the network
from the Ignite-UX server. This happens either because the machine does not support booting from the net-
work or because it is not on the same subnet as the Ignite-UX server. In this case, booting from a tape gen-
erated by make_boot_tape means you do not need to set up a boot helper system. A tape created by
make_boot_tape may be used to kick off a normal Ignite-UX installation. It may also be used to
recover from recovery configurations saved on the Ignite-UX server. There is no "target-specific" informa-
tion on the boot tape. Only information about the Ignite-UX server is placed on the tape. Thus, it is possi-
ble to initiate an installation of any target machine from the same boot tape provided that the same Ignite-
UX server is used. Likewise, the target machine may be installed with any operating system configuration
that is available on the Ignite-UX server.
Typically, the make_boot_tape command is run from the Ignite-UX server that you wish to connect
with when booting from the tape later.
A key file that contains configuration information is called *INSTALLFS. This file exists on the Ignite-
UX server at /opt/ignite/boot/Rel_release/*INSTALLFS and is also present on the tape created
by make_boot_tape. See instl_adm(4) for details on the configuration file syntax. Unless the -f
option is used, the configuration information already present in the *INSTALLFS file is used on the tape
as well. The make_boot_tape command will never alter the *INSTALLFS file on the Ignite-UX
server; it will only change the copy that is placed on the tape.
Options
make_boot_tape recognizes the following options:
−d device_file_for_tape
Specifies the device file of the tape device where the boot tape will be created.
For the widest usage of the tape, choose a device file that will create a tape that
will work in any drive. For example, a tape created with a DDS-1/no compres-
sion device file will work in any DDS drive. One of the examples shows how to
create this device file. Also, see mksf (1M) for information on how to create a
DDS-1 device file. On certain systems, it is also possible to boot from a DLT
tape drive. By default, the /dev/rmt/0m device will be used.
-f configuration_file
Specifies that the contents of configuration_file will be treated as the configura-
tion information in the *INSTALLFS file that is written to the tape. The con-
tents of configuration_file will replace any configuration information already
present in the *INSTALLFS file that will written to the tape. The syntax of
configuration_file is always checked before it is applied.
See the examples section for a method to use the configuration information
already present in /opt/ignite/boot/Rel_release/*INSTALLFS as a
1