Installation guide

(boot primary partition)
P##>>> boot
(boot secondary partitions)
Improper operation results if the lpinit command is omitted. The console
firmware prevents this by automatically executing the lpinit command if
the lp_count is nonzero and a boot command is issued on the primary
partition’s console terminal.
On startup, each secondary partition displays configuration information
(similar to the message in Section E.4.3.1). It is possible for this message to
be proceeded by a series of Y characters. This is not an error and can be
ignored.
7.2.7 Section E.4.5 (Installing the Operating System)
The operating system can be installed from a CD–ROM or over the network
from a Remote Installation Server (RIS). It may not always be practical to
configure a CD–ROM drive on all partitions and/or a RIS server may not be
available. One alternative (assuming a local network is available) is to install
the operating system to one partition from a CD–ROM, then configure that
partition as a RIS server for the other partitions. Refer to Sharing Software
on a Local Area Network for instructions on setting up a Remote Installation
Server.
7.3 Assembly Language Programmer’s Guide
The Assembly Language Programmer’s Guide (Chapter 5) should include a
description of the .rconst directive. This directive instructs the assembler
to add subsequent data into the .rconst section. This behavior is similar
to the .rdata directive, except that the entries cannot be relocatable.
7.4 Programming with ONC RPC
Sections 2.1.5 and 2.1.6 of the Programming with ONC RPC guide are
correct only for a system running Tru64 UNIX or earlier version of the
operating system. The code may not be portable to other UNIX systems.
If the client machine is not running Tru64 UNIX or earlier version of the
operating system, copy the source code to the client. Check that the header
calls are appropriate for the programming conventions on the client operating
system and then compile the code locally.
7–4 Documentation Notes