A product kit is the standard mechanism by which layered products are delivered to and maintained on a Compaq Tru64TM UNIX® (formerly DIGITAL UNIX) operating system. This manual describes the procedures for creating, installing, and managing the collections of files and directories that make up a layered product kit that will be installed on a customer's system. Kits can be distributed on CD-ROM, diskette, or magnetic tape. A hardware product kit can only be distributed on CD-ROM in Direct CD format.
This book is intended for software developers who are responsible for creating product kits. They are expected to be moderately experienced with UNIX based operating systems and should have experience performing system administration tasks.
The following list describes the major changes made to this book:
The definition of a kit at the beginning of Chapter 1 has been expanded and clarified.
Notes have been added to Section 1.3 and Section 3.1.6 to explain subset control program requirements for DMS compliance.
The definition of the
DEPS
subset control
file field has been changed in
Section 4.4.3.
The sections referring to foreign device kits have been removed. This information has been superseded by Chapter 5 which describes how to create, test, and deliver hardware product kits.
Appendix A has been added to provide instructions on how to create and build a consolidated CD-ROM. A consolidated CD-ROM lets you upgrade your processor firmware at the same time that you install the operating system.
This manual is organized as follows:
| Chapter 1 | Introduction |
| Presents an introduction to the kit-building process. | |
| Chapter 2 | Creating the Kit Directory Structure |
| Describes how to create kit directories and build product kits. | |
| Chapter 3 | Creating Subset Control Programs |
| Describes how to write subset control programs (SCPs) to install and manage software subsets. | |
| Chapter 4 | Building Subsets and Control Files |
Describes how to create subsets
and subset control files with the
newinv
and
kits
utilities. |
|
| Chapter 5 | Hardware Product Kits |
| Describes how to create, test, and deliver hardware product kits for new or existing hardware. | |
| Chapter 6 | Producing Distribution Media for User and Kernel Product Kits |
| Describes how to produce a user or kernel product kit on the distribution media. | |
| Chapter 7 | Testing a User or Kernel Product Kit |
| Describes how to test user and kernel product kits on the target system. | |
| Appendix A | Creating a Consolidated CD-ROM |
| Dscribes how to create a consolidated CD-ROM. | |
| Appendix B | Standard Directory Structure |
| Describes the standard directory hierarchy. | |
| Glossary | Defines terms used in this manual. |
The printed version of the Tru64 UNIX documentation set is color coded to help specific audiences quickly find the books that meet their needs. (You can order the printed documentation from Compaq.) This color coding is reinforced with the use of an icon on the spines of books. The following list describes this convention:
| Audience | Icon | Color Code |
| General users | G | Blue |
| System and network administrators | S | Red |
| Programmers | P | Purple |
| Device driver writers | D | Orange |
| Reference page users | R | Green |
Some books in the documentation set help meet the needs of several audiences. For example, the information in some system books is also used by programmers. Keep this in mind when searching for information on specific topics.
The Documentation Overview provides information on all of the books in the Tru64 UNIX documentation set.
You may find the following documents helpful when preparing product kits:
Sharing Software on a Local Area Network
This manual describes Remote Installation Services (RIS) and Dataless
Management Services (DMS).
RIS is used to install software across a network
instead of using locally mounted media.
DMS allows a server system to maintain
the root,
/usr, and
/var
file systems
for client systems.
Each client system has its own root file system on the
server, but shares the
/usr
and
/var
file systems.
This manual can be helpful if you are preparing a hardware product kit that will be installed in a RIS environment.
Writing Device Drivers: Tutorial
This manual provides information for systems engineers who write device drivers for hardware that runs the operating system. Systems engineers can find information on driver concepts, device driver interfaces, kernel interfaces used by device drivers, kernel data structures, configuration of device drivers, and header files related to device drivers.
This manual can be helpful if you are preparing product kits for a device driver.
This manual describes the procedures to perform an Update Installation or Full Installation of the operating system on all supported processors and single-board computers. It explains how to prepare your system for installation, boot the processor, and perform the installation procedures.
This manual describes how to configure, use, and maintain the operating system. It includes information on general day-to-day activities and tasks, changing your system configuration, and locating and eliminating sources of trouble. This manual is intended for the system administrators responsible for managing the operating system. It assumes a knowledge of operating system concepts, commands, and configurations.
Reference Pages Sections 8 and 1m
This section describes commands for system operation and maintenance. It is intended for system administrators. In printed format, this section is divided into two volumes.
The Release Notes describe known problems you might encounter when working with the operating system and provides possible solutions for those problems. The printed format also contains information about new and changed features of the operating system, as well as plans to retire obsolete features of the operating system. Obsolete features are features that have been replaced by new technology or otherwise outdated and are no longer needed. The Release Notes are intended for anyone installing the operating system or for anyone using the operating system after it is installed.
Compaq welcomes any comments and suggestions you have on this and other Tru64 UNIX manuals.
You can send your comments in the following ways:
Fax: 603-884-0120 Attn: UBPG Publications, ZKO3-3/Y32
Internet electronic mail:
readers_comment@zk3.dec.com
A Reader's Comment form is located on your system in the following location:
/usr/doc/readers_comment.txt
Mail:
Compaq Computer Corporation
UBPG Publications Manager
ZKO3-3/Y32
110 Spit Brook Road
Nashua, NH 03062-9987
A Reader's Comment form is located in the back of each printed manual. The form is postage paid if you mail it in the United States.
Please include the following information along with your comments:
The full title of the book and the order number. (The order number is printed on the title page of this book and on its back cover.)
The section numbers and page numbers of the information on which you are commenting.
The version of Tru64 UNIX that you are using.
If known, the type of processor that is running the Tru64 UNIX software.
The Tru64 UNIX Publications group cannot respond to system problems or technical support inquiries. Please address technical questions to your local system vendor or to the appropriate Compaq technical support office. Information provided with the software media explains how to send problem reports to Compaq.
The following conventions are used in this manual:
%$A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells.
#A number sign represents the superuser prompt.
% catBoldface type in interactive examples indicates typed user input.
Italic (slanted) type indicates variable values, placeholders, and function argument names.
In syntax definitions, brackets indicate items that are optional and braces indicate items that are required. Vertical bars separating items inside brackets or braces indicate that you choose one item from among those listed.
coloredtext
In syntax definitions, literal elements are colored green. Variable values, placeholders, and function argument names are colored red. No special colored text is used outside of syntax descriptions.
In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times.
cat(1)A cross-reference to a reference page includes the appropriate section
number in parentheses.
For example,
cat(1)
indicates that you can find information on the
cat
command in Section 1 of the reference pages.
In an example, a key name enclosed in a box indicates that you press that key.
This symbol indicates that you hold down the first named key while pressing the key or mouse button that follows the slash. In examples, this key combination is enclosed in a box (for example, [Ctrl/C] ).