update(4)

NAME

update − update-media format

DESCRIPTION

Tape update media consist of a simple tar archive (see tar(1)) with a few leading information files used by update (see update(1M)) plus specially-crafted file paths that allow files to be grouped into filesets. The following is intended as an aid in interpreting tape update media; not as a design guide for building your own. Update script format is also documented here.

On a netdist server system and on a CD-ROM, the update “media” is a collection of files in a directory hierarchy (exact format varies according to media type), plus various information files.

Information Files

The information files contain ASCII text and include:

system/INDEX
This file describes the filesets on the media. It consists of a header line followed by a series of blocks (paragraphs) of data (text), one for each fileset on the media. Each block is bounded by “begin:” and “end:” and contains labeled attributes for the fileset. The file contains lines of the form:

INDEX: media_number media_version_number checksum_algorithm_number

begin: fileset_name

mn: medium_number

fd: fileset_description

pn: partition_name

pd: partition_description

ff: fileset_flags (see Fileset Flags below)

is: instruction_sets (A.B8.05 media only; see Fileset Types below)

sys: system_types (A.B8.05 media only; see Fileset Types below)

fs: fileset_size (in bytes; normally computed by update)

fv: fileset_version_number

dep: dependee_fileset_1 dependee_version_number (minimum needed)

dep: dependee_fileset_2 dependee_version_number

...

ffile: INFO_file_information

...

frule: CDFinfo_file_information

...

end: fileset_name

begin: fileset_name

... (similar information about next fileset)

end: fileset_name

ENDINDEX: checksum

Dependency lines include both direct and indirect dependencies. The update and updist commands do not recursively apply dependencies.

On multiple-tape update media, the INDEX file on each tape is identical to that on all other tapes except for the media unit number in the header line.

system/INFO
This file describes the files on the media. For each fileset on the media, it contains a list of all the files in the fileset along with their sizes and special attributes. The file contains lines of the form:

INFO: media_version_number checksum_algorithm_number

#Fileset	Bytes	File
#==============	========	===================
fileset_name
+type[,attr]	size (bytes)	file_name [link_target]
+type[,attr]	size	file_name [link_target]
...
fileset_name
+type[,attr]	size	file_name [link_target]
+type[,attr]	size	file_name [link_target]
...

ENDINFO: checksum

Some HP-UX file attributes cannot be contained in a CD-ROM file system. They are included in the INFO file instead, in the type and attr fields. The value of the type field is one of the following. These are the only file types supported on any update media.

RF regular file

SL symbolic link (requires link_target)

HL hard link (requires link_target)

DR directory

The attr field is an octal value representing the file’s mode bits. The value from the source media is used, and the INFO file value is ignored, except when loading from CD-ROM media. File mode bits (from the source media or the attr field) are ignored for symbolic and hard links ( SL and HL entries), and left unchanged for directories ( DR entries) except when a new directory is created.

The size field is the string length of link_target for SL entries, and zero for HL and DR entries.

On multiple-tape update media, the INFO file on each tape is identical to that on all other tapes.

system/CDFinfo
This file contains a list of stand-alone file path names and one or more rules concerning each path name. The rules describe changes associated with each file when turning a standalone system into a cluster server, updating a cluster server, or adding a cnode to a clustered system. The sam and update commands (see sam(1M) and update(1M)) apply these rules during such operations. Only files whose paths require changes during cluster operations appear in the CDFinfo file.

If update media lacks CDFinfo files, update issues a warning, but updist refuses to load from the media because the result might be a netdist server on which some filesets have CDF information and others do not. (The workaround is to put empty CDFinfo files on the media for each fileset.)

Fileset Flags

Any of five flags can be associated with each fileset. Their meanings are:

B Rebuild the kernel and reboot the system.

C Change of destination is not allowed for this fileset. The fileset must be loaded under /.

M or H
Fileset contains HP-MC68020 (Series 300/400) files or HP-PA (Series 700 or Series 800) files, respectively. Beginning with release 8.05, the M flag is equivalent to:

is: MC68020
sys: S300

(see Fileset Types below). The H flag is equivalent to:

is: PA_RISC_1_0
sys: S700, S800

Note that the M and H flags and the is and sys fields are mutually exclusive. Each fileset’s type must be specified with a flag or the is and sys fields, but not both. Beginning with A.B8.05-format media, the latter form is preferred.

S Fileset is secured (protected) against direct access from a CD-ROM.

Y Use rmfn to remove the files in the fileset before loading new ones (see rmfn(1M)). Use of this flag is discouraged because processing it is time consuming. The removal is better done for specific cases by customize scripts.

The B, C, and Y flags are used by update and ignored by updist.

Fileset Types on A.B8.05 Format Media

Beginning with the 8.05 release (media format A.B8.05), the is field specifies the instruction set(s) types of the system CPU on which the fileset can be loaded. The field value is one of:

MC68020 Motorola 68020, 68030, or 68040

PA_RISC_1_0 HP-PA RISC 1.0 or 1.1

PA_RISC_1_1 HP-PA RISC 1.1

* Indicates no particular instruction set is required. For example, this typically marks a fileset conatining only shell scripts and simple text.

The sys field specifies the system type(s) on which the fileset can be loaded. The field value is one or more comma-separated values from this list.

S300 Series 300 or 400

S700 Series 700

S800 Series 800

* Indicates the fileset is intended for all supported systems.

For example, consider a program compiled to use HP-PA RISC 1.0 instructions that does not distinguish Series 700 and Series 800 system types, or which handles the distinctions at run time. A fileset containing this program might be marked:

is: PA_RISC_1_0
sys: S700, S800

Path Names

On tape update media, path names of files other than the information files consist of their official path names with a concatenated prefix:

fileset/..

For example:

UX-CORE/../bin/sh

These path names indicate each file’s fileset and still allow unpacking with tar relative to any directory. Unpacking a tape update media unit with tar rather than update is discouraged, partly because it creates empty directories on the system, one for each fileset on the update media. The empty directories can be removed.

Each fileset’s files appear on the media grouped together (in a contiguous sequence).

Update Scripts

Update script files written and read by update (see update(1M)) have the following format:

• Blank and comment lines are ignored. Comment lines have # as the first non-whitespace character.

• All other lines are data lines and must end in \. Any whitespace at the start of the line or before the backslash is ignored.

• Each data line consists of one of the following forms.

name=’value’ \
command_name \
-option_letter \
-option_letter ’option_argument’ \
fileset_name \

• Any variable declarations (name=’value’) must appear before any other line types. The only supported environment variable in this context is UPDATENOSKIP.

• The first data line after variable declarations (if any) must be the full path name of the command as invoked from the command line, and it must match the current invocation name.

• Next are command options, one per line, each starting with -, with option arguments where required. Update scripts support any of the -msSPCdrb options only; options -Ffic cannot appear in them. For a netdist server source, the -P option must be present. For a CD-ROM source, the -C option must be present. (In this context the presence of these options also specifies the source type as other than tape.)

• Options are followed by zero or more fileset names, one per line, to cause pre-selection of filesets. Either fileset names or the -m option can be present, but not both, and neither is required. Note that -m causes matching on the system where the update script is run or read, possibly with different results than on the system where the script was written.

Here is an example of an update script.

UPDATENOSKIP=’0’ \
/etc/update \
-s ’hpfclc.fc.hp.com’ \
-S ’300’ \
-P ’8080’ \
-d ’/’ \
-r \
KERN-BLD \
LAN \
LSSERVER-ADMIN \
TOOL \

EXAMPLES

List the files on a tape update media unit accessed through special file /dev/rmt:

tar -tvf /dev/rmt

Display the leading information files on a given tape update media unit:

cd /tmp
tar -xvf /dev/rmt system
more system/*

DEPENDENCIES

Series 700

For HP-UX release 8.01, unlike release 8.05, update and updist do not distinguish Series 700 and Series 800 update media. Media for both Series are version A.B8.00 and bear the fileset flag H.

Museum

Related Articles