make_boot_tape.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

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_ﬁle_for_tape ]

[

-f conﬁguration_ﬁle][

-t tmp_directory][-v

][-? ]

/opt/ignite/bin/make_boot_tape

[ -d device_ﬁle_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 sys-

tem 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 conﬁguration

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 can-

not boot via the network from the Ignite-UX server. This happens either because the machine does not

support booting from the network or because it is not on the same subnet as the Ignite-UX server. In this

case, booting from a tape generated 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 instal-

lation. It may also be used to recover from recovery conﬁgurations saved on the Ignite-UX server. There

is no "target-speciﬁc" information on the boot tape. Only information about the Ignite-UX server is placed

on the tape. Thus, it is possible 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 conﬁguration 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 ﬁle that contains conﬁguration information is called

*INSTALLFS. This ﬁle exists on the Ignite-

UX server at /opt/ignite/boot/Rel_

release /*INSTALLFS and is also present on the tape created

make_boot_tape. See instl_adm (4) for details on the conﬁguration ﬁle syntax. Unless the

-f

option is used, the conﬁguration information already present in the *INSTALLFS ﬁle is used on the tape

as well. The make_boot_tape

command will never alter the *INSTALLFS ﬁle 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

Speciﬁes the device ﬁle of the tape device where the boot tape will be created. For

the widest usage of the tape, choose a device ﬁle that will create a tape that will

work in any drive. For example, a tape created with a DDS-1/no compression device

ﬁle will work in any DDS drive. One of the examples shows how to create this dev-

ice ﬁle. Also, see mksf (1M) for information on how to create a DDS-1 device ﬁle.

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

Speciﬁes that the contents of conﬁguration_ﬁle will be treated as the conﬁguration

information in the *INSTALLFS ﬁle that is written to the tape. The contents of

conﬁguration_ﬁle will replace any conﬁguration information already present in the

*INSTALLFS ﬁle that will written to the tape. The syntax of conﬁguration_ﬁle is

always checked before it is applied.

See the examples section for a method to use the conﬁguration information already

present in /opt/ignite/boot/Rel_release /*INSTALLFS as a starting point

for what is written to the tape.

-g gateway Speciﬁes the default Internet address for the gateway system through which the

target system may reach the Ignite-UX server. This is useful when the target sys-

tems are not on the same subnet as the Ignite-UX server.

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (4 pages)

PAGE 1
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
PAGE 2
make_boot_tape(1M) make_boot_tape(1M) The configuration already in /opt/ignite/boot/Rel_release /*INSTALLFS is used as a starting point in this case. The gateway specified is added to this data. If your situation requires a netmask to be set (see -m below), you will need to specify a netmask with the -m option. By default, when a gateway is specified with -g, any existing netmask in /opt/ignite/boot/Rel_release /*INSTALLFS will be ignored.
PAGE 3
make_boot_tape(1M) make_boot_tape(1M) SEE ALSO instl_adm(1M), make_medialif(1M), make_net_recovery(1M), make_tape_recovery(1M), instl_adm(4), ignite(5).
PAGE 4
(Notes) A (Notes) mA 4 Hewlett-Packard Company −1− HP-UX 11i Version 3: March 2012