Digital PDFs

AA-PBL0E-TE

August 1992

153 pages

Original

5.3MB

Document:	ULTRIX Guide to Installing ULTRIX
Order Number:	AA-PBL0E-TE
Revision:	0
Pages:	153
Original Filename:

OCR Text

ULTRIX

Guide to Installing ULTRIX

Part Number: AA-PBLOE-TE

ULTRIX
Guide to Installing ULTRIX
Order Number: AA-PBLOE-TE

August 1992
Product Version:

ULTRIX and ULTRIX Worksystem Software, Version

4.3

This guide describes the basic and advanced installation procedures for ULTRIX and
ULTRIX Worksystem Software on all supported processors. This guide also describes
how to upgrade a system without having to perform an installation.

digital equipment corporation
Maynard, Massachusetts

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as
set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.227-7013.
© Digital Equipment Corporation 1987, 1988, 1989, 1990, 1992

The information in this document is subject to change without notice and should not be construed as a
commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no
responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or copied only in
accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by
Digital or its affiliated companies.

The following are trademarks of Digital Equipment Corporation:
ALL-IN-I, Bookreader, CDA, DDIF, DDIS, DEC, DEC FUSE, DEC net, DEC station, DEC system,
DECUS, DECwindows, DTIF, MASSBUS, MicroVAX, Q-bus, ULTRIX, ULTRIX Mail Connection,
ULTRIX Worksystem Software, UNIBUS, VAX, VAXstation, VMS, VT, XUI, and the DIGITAL logo.
Ethernet is a registered trademark of Xerox Corporation. IBM is a registered trademark of International
Business Machines Corporation. INGRES is a trademark of Ingres Corporation. Prestoserve is a
trademark of Legato Systems, Inc.; the trademark and software are licensed to Digital Equipment
Corporation by Legato Systems, Inc. Modula-2 is a trademark of Interface Technologies Corporation.
PostScript and Display PostScript are registered trademarks of Adobe Systems, Inc. UNIX is a
registered trademark of UNIX System Laboratories, Inc.

Contents

About This Manual
ix

Audience
Organization

. .. . . . . .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .

Related Documentation

............. .........................................................................

Conventions

x
x

Preparing for the Installation

1.1

Deciding on the Type of Installation
1.1.1
1.1.2
1.1.3
1.1.4

...........................................................

1-1

The Upgrade Installation .................................................................
The Basic Installation .....................................................................
The Advanced Installation ...............................................................
The System Management Option .....................................................

1-2
1-2
1-3
1-4

1.2

Checking the Hardware Needed for Installation

1-4

1.3

Checking the Software Distribution Kit

.......................................................

1-5

1.4

Backing Up the System

.............................................................................

1-6

Backups Before Upgrades ...............................................................
Backups Before Basic and Advanced Installations ................ ..............
The Next Step ...............................................................................

1-6
1-6
1-7

1.4.1
1.4.2
1.4.3

Planning Your Disk Space

2.1

Identifying Supported System Disks

2-2

2.2

Planning the Swap Space

2-4

2.3

Planning the Crash Dump Space

2-5

2.4

Planning the var Area

.............................................................................. .

2-6

Size of the var/adm/crash Directory ................................................. .
Error Logger ................................................................................ .
System Accounting ....................................................................... .

2-7
2-7
2-7

2.4.1
2.4.2
2.4.3

2.4.4
2.4.5
2.5

Size of the var/admlris Directory .................................................... .
Completing the var Worksheet ........................................................ .

Planning the lusr File System
2.5.1
2.5.2
2.5.3
2.5.4

2-8
2-8
2-9

Software Subsets Within the lusr File System .................................. ..
User Area .................................................................................... .
var Area ...................................................................................... .
Completing the lusr Worksheet ....................................................... .

2-9
2-9
2-10
2-10

2.6

Determining the Disk Partition Layout

2-10

2.7

Planning the Configuration File Entries

2-11

Booting the System

3.1

DEC station 2100/3100/3100S or DECsystem 3100 Processor

.........................

3-4

Booting from the TK50 Tape Cartridge Kit .......................................
Booting from the CDROM Optical Disc Kit ......................................
Booting from the Network ..............................................................

3-4
3-4
3-5

DEC station 5000 Series, DEC system 5000 Series, Personal DEC station 5000
Series, and the DECsystem 5900 Processor .............................................

3-6

3.2.1

3-6

3.1.1
3.1.2
3.1.3
3.2

Determining the Slot and Device Numbers of Your Boot Device
Determining the Slot Number (Default) ................................ ..
Determining the Boot Device Number ................................... .

3--6

Booting from the TK50 Tape Cartridge Kit ..................................... ..
Booting from the CDROM Optical Disc Kit ..................................... .
Booting from the Network ............................................................. .

3-7
3-7

3.2.1.1
3.2.1.2
3.2.2
3.2.3
3.2.4
3.3

DECsystem 5100 Processor
3.3.1
3.3.2
3.3.3

3-7

3-8

.......................................................................

3-9

3-9
3-9
3-10

3.4

DEC system 5400 Processor

3-11

3.5

DEC system 5500 Processor

3-12

3.5.1
3.5.2
3.5.3
3.5.4

Booting from the SCSI Tape Device ............................................... .
Booting from the Q-bus Tape Device ............................................. ..
Booting from the CDROM Optical Disc Kit ..................................... .
Booting from the Network ............................................................. .

3.6

DEC system 5810/5820/5830/5840 Processor

3.7

MicroVAX 2000, VAXserver 2000, or VAXstation 2000 Processor
3.7.1

ivContents

Booting from the TK50 Tape Cartridge Kit

3-12
3-13
3-13
3-13
3-15

................

3-17

.......................................

3-17

3.7.2
3.8

3.10

................

3-19

Booting from the TK50 Tape Cartridge Kit ...................................... .
Booting from the CDROM Optical Disc Kit ..................................... .
Booting from the Network ............................................................. .

3-19
3-20
3-21

MicroV AX 3300/3400 or V AXserver 3300/3400 Processor

3-22

3.9.1
3.9.2

Booting from the TK50 Tape Cartridge Kit ...................................... .
Booting from the Network ............................................................ ..

3-22
3-22

MicroV AX II, MicroV AX 3500/3600/3800/3900, V AXserver
100/3500/3600/3800/3900, VAXstation 3200/3500, VAXstation II, or
VAX station IIIGPX Processor .............................................................. .

3-24

3.10.1
3.10.2
3.11

3-18

MicroVAX 3100, VAX server 3100, or VAX station 3100 Processor
3.8.1
3.8.2
3.8.3

3.9

Booting from the Network

Booting from the TK50 Tape Cartridge Kit ................................... ..
Booting from the Network ........................................................... .

V AXstation 3520 or V AXstation 3540 Processor
3.11.1
3.11.2
3.11.3

3-24
3-25

....................................... .

3-26

Booting from the TK50 Tape Cartridge Kit .................................... .
Booting from the CDROM Optical Disc Kit .................................. ..
Booting from the Network ........................................................... .

3-26
3-27
3-27

3.12

VAX-ll/750 Processor

3.13

V AX-11/780 or V AX-11/785 Processor

3-30

3.14

VAX 6000-nnn Series or VAX server 6000-nnn Series Processor

3-32

3.14.1
3.14.2
3.14.3

...........................................................................

Booting from the TK50 Tape Cartridge Kit .................................... .
Booting from a System with a CIBCA-AA Controller ...................... .
Booting from a System with a CIBCA-AB Controller ...................... .

3.15

V AX 8200/8250 or V AX 8300/8350 Processor

3.16

VAX 8500/8530/8550, VAX 8700, or VAX 8800/8810 Processor

3.17

V AX 8600/8650 Processor

3.18

V AX 8820/8830/8840 Processor
3.18.1
3.18.2

3.19

......................................... .
............... .

3-28

3-32
3-32
3-33
3-34
3-36
3-37

.............................................................. .

3-38

Booting Sequence for a System Disk Connected to a Local Controller.
Booting Sequence for a System Disk Connected to an HSC ...............

3-38
3-39

V AX 9000 Processor

3-40

Performing the Installation

4.1

Choosing the Type of Installation

4-1

4.2

Selecting the Software Distribution Device

4-2

Contents v

4.3

Selecting the Disk for the root Partition

4.4

Rebooting the System

4.5

Specifying System Information

4.6

Allocating File Systems
4.6.1
4.6.2
4.6.3
4.6.4
4.6.5

......................................................

4-3

...............................................................................

4-5

..................................................................

4-5

............................................................................

4-6

Allocating the lusr File System ....................................................... .
Allocating the swap 1 Space ............................................................ .
Allocating the swap2 Space ............................................................ .
Allocating the Crash Dump Space ................................................... .
Allocating the var Area .................................................................. .

4-7
4-8
4-9
4-10
4-11

4.7

Installing ULTRIX Worksystem Software

4-12

4.8

Loading the Software Subsets

....................................................................

4-13

Installing from TK50 or MT9 Tape ..................................................
Installing from a CDROM ..............................................................
Loading Software Subsets for the Basic Installation ...........................
Loading Software Subsets for the Advanced Installation .....................

4-13
4-14
4-14
4-14

4.8.1
4.8.2
4.8.3
4.8.4
4.9

Loading the Software Subset Upgrades

4-16

4.9.1
4.9.2

4-16
4-17

Loading Upgrades from TK50 or MT9 Tape .................................... .
Loading Upgrades from CDROM ................................................... .

4.10

Specifying Kernel Options for the Configuration File

4-18

4.11

Console Boot Defaults and Console Media

4-20

4.11.1
4.11.2

Updating the Console Boot Default ............................................... .
Updating the Console Media ........................................................ .

4-21
4-21

4.12 _Completing the Installation and Rebooting the System

4-22

4.13

Post-Installation Procedures

4-23

Performing an Upgrade

5.1

Upgrading A Local System
5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6

....... .................................................................

5-2

Starting the Upgrade ..... .................................................................
Upgrading from a TK50 or MT9 ......................................................
Upgrading from a CDROM .............................................................
Upgrading from the Network .... ..... .... ........ ............ ...... .... ................
Loading the Software Subsets ..........................................................
Loading the Software Subset Updates ...............................................

5-2
5-3
5-3
5-3
5-3
5-4

5.1.6.1
5.1.6.2
5.1.6.3
5.1.7

vi Contents

Updating from a TK50 or MT9 .............................................
Updating from CDROM .......................................................
Updating from the Network ..................................................

Rebuilding a Kernel when the Required Kernel Is Available

................

5-4
5-5
5-5
5-6

5.1.8
5.2

Upgrading a Remote Installation Services Area

5.3

Upgrading a Diskless Management System Area

Adding and Deleting Software Subsets

6.1

Listing Software Subsets

6.2

Adding Subsets
6.2.1
6.2.2

5-7

Rebuilding a Kernel when the Required Kernel Is Not Available

5-9
5-9

...........................................................................

6-1

........................................................................................

6-1

Adding Subsets from Tape ..............................................................
Adding Subsets from a File Server ...................................................

6-2
6-2

6.3

Deleting Subsets

Working in the Standalone ULTRIX Environment

7.1
7.2

Invoking the Standalone ULTRIX Environment

7.3

Extending the Standalone ULTRIX Environment

RiSe Supported Software Subsets

VAX Supported Software Subsets

Unsupported Software Subsets

Sample Advanced Installation Procedure

D.1

Sample Advanced Installation Procedure.

6-2

7-1
7-2
7-2

Standalone ULTRIX Environment Capabilities

D-1

Index
Tables
1-1: Names of Directories and Files to Back Up
2-1: Supported System Disks

.................................................. .

............................................................................ .

2-2: Disk Configuration Worksheet

................................................................... .

1-7
2-2
2-3

2-3: Partial Crash Dump Space Requirements

2-6

2-4: var Worksheet

2-8

.......................................................................................... .

Contents vii

2-5: lusr Worksheet

2-10

2-6: File System Worksheet

2-11

2-7: Configuration File Entries

..... , ., ....... , . . . . .. . . . . . . . .. . ... . . . .. . . . .. . .. . . .. . . . . . . .. . . . . .. . .. . . . . ..

3-1: Location of Processor-Specific Boot Instructions
4-1: Post-Installation Tasks

...........................................

3-1

............................................... ................................

4-23

A-I: RISC Supported Subset Descriptions and Dependencies

.................................

B-1 : VAX Supported Software Subset Descriptions and Dependencies
C-l: Unsupported Software Subset Descriptions and Dependencies

viii Contents

2-12

....................

A-I
B-1
C-l

About This Manual

This guide describes the basic and advanced installation procedures for ULTRIX and
ULTRIX Worksystem Software (UWS) on all supported processors. It describes how
to prepare your system for installation, boot the processor, and perform the
installation procedure.
In addition, this guide discusses:
•

An upgrade procedure for certain systems, which you use instead of the basic or
advanced installation procedures to produce the new version of the product.
The upgrade procedure can be run on all ULTRIX and UWS Version 4.2 or
higher systems.

•

Standalone system management procedures, which operate in a memory-resident
environment to support limited system management activities.

Audience
The audience for this guide is anyone installing an ULTRIX system. The guide
assumes that:
•

You or a Digital Field Service representative has checked the hardware to ensure
that it is working properly.

•

You have read the documentation supplied with your hardware.

•

You have read the current version of the Release Noles.

•

You know the location and function of the controls and indicators on your
hardware.

•

You understand how to load and unload the installation media and know which
disks are needed during the installation.

•

You have a basic understanding of the ULTRIX file system and commands.

Organization
This guide has seven chapters, four appendixes, and an index:
Chapter 1

Describes the basic and advanced installation procedures and outlines
the tasks you must complete before beginning an installation.

Chapter 2

Describes the tasks you should complete before beginning an advanced
installation. This chapter contains a set of worksheets to help you plan
your system.

Chapter 3

Describes how to boot each processor that can support the ULTRIX
software.

Chapter 4

Describes how to complete the basic and advanced installations.

Chapter 5

Describes how to perform an upgrade procedure.

Chapter 6

Describes how to use the set 1 d utility to add or delete subsets after
the installation is complete.

Chapter 7

Describes a memory-resident environment that supports the initial
phases of an installation and limited system management activities.

Appendix A

Describes each supported subset for RISC processors and lists any
related subsets and system configuration file options.

Appendix B

Describes each supported subset for VAX processors and lists any
related subsets and system configuration file options.

Appendix C

Describes each unsupported subset for RISC and VAX processors.

Appendix D

Provides a complete example of an advanced installation.

Related Documentation
The following list suggests the order in which you should read the related
documentation:
1. Hardware documentation

This documentation shows you how to set up the processor and its additional
devices, and supplies valuable troubleshooting guidelines.
2. Release Notes

This document contains media labelling, subset sizes, and other installationrelated notes. Please read the release notes before beginning the installation or
update procedures.
3. Guide to System and Network Setup

You should refer to this guide to help you determine what to do after you
complete the advanced installation.
4. Guide to Sharing Software on a Local Area Network

This documentation describes how to install software products over the network.

Conventions
#

A number sign represents the superuser prompt.

% cat

Boldface type in interactive examples indicates typed user input.

file

Italic (slanted) type indicates variable values, placeholders, and function
argument names.
In syntax definitions, a horizontal ellipsis indicates that the preceding item
can be repeated one or more times.

cat(l)

x About This Manual

A cross-reference to a reference page includes the appropriate section
number in parentheses. For example, cat(l) indicates that you can find
information on the cat command in Section 1 of the reference pages.

Ctrl/x

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, ICtri/C I).

About This Manual xi

Preparing for the Installation

This chapter describes the basic and advanced installation procedures and discusses
the tasks you must complete before beginning the installation.
Before you begin the installation, do the following:
•

Read the Release Notes
The Release Notes contain information about installing and upgrading the
software, including hardware, boot, and general installation notes, such as
outstanding problems and their workarounds. The Release Notes also contain the
subset sizes for the RISC, VAX, and unsupported software. You will use these
subset sizes to help determine the characteristics of the system(s) you will install.

•

Decide whether you must use the upgrade procedure for your installation
Chapter 5 contains a procedure that allows you to upgrade to the current version
of ULTRIX and UWS without performing a basic or advanced installation. The
upgrade procedure is only for systems running ULTRIX and UWS Version 4.2 or
higher.

•

Decide whether to perform a basic or advanced installation
For new installations and for systems running ULTRIX and UWS versions earlier
than Version 4.2, Chapter 2 contains a set of worksheets designed to help you
plan your system. Working through Chapter 2 before beginning the advanced
installation will help you determine if you have enough disk space on your
system.

1.1

•

Check to be sure you have the hardware needed for installation

•

Check the contents of the software distribution kit against the Bill of Materials

•

Back up the system if you need to retain any information from your previous
system

Deciding on the Type of Installation
ULTRIX software can be installed on your system in the following ways:
•

If your system comes with Factory Installed Software (FIS), all of the ULTRIX
supported software subsets are installed at the factory. If you have PIS, you do
not need this guide. Refer to the PIS documentation included with your
processor.

•

From TK50 tape cartridges.

•

From an RRD40 or RRD42 CDROM optical disc cartridge.

•

From MT9 magnetic tapes.

•

From the network. A Remote Installation Services (RIS) client uses the network
to install software from a server that has been established with RIS.

The installation procedure provides four paths for you to follow: the upgrade
installation, the basic installation, the advanced installation, or the system managment
option. In addition, the installation procedure provides the system management
option.

1.1.1

The Upgrade Installation
The upgrade installation allows you to preserve your current ULTRIX and UWS
environment while upgrading to the new system. You do not have to perform a basic
or advanced installation and you do not have to save and restore your customizable
system files.
The upgrade procedure saves all your customizable system files before it copies and
verifies the subsets from the distribution medium. Then, the upgrade is applied to
your current system. Finally, you rebuild your system's kernel to effect the upgrade
to the new system version.
There is one restriction: any customizable files which you have modified and are
from the unsupported subsets will be replaced when the unsupported subsets are
installed. The procedure does not save the customizable files in any unsupported
subset. See Chapter 5 for more information.

1.1.2 The Basic Installation
The basic installation installs a default system with a minimum of prompts. The
basic installation procedure creates file systems on default partitions on your system
disk and loads the required software subsets. You should choose this path if you are
new to the ULTRIX operating system or if you want to install a basic system.
There are some post-installation procedures that you will not perform if you choose
the basic installation. For example, printer services are not available with the basic
installation. See Table 4-1 for further information.
The basic installation creates the following areas on default partitions on the system
disk:
•

The root file system

•

The /usr file system

•

The crash dump space and the swap space

The var area is created as a directory under the /usr file system.
The basic installation loads the following required supported software subsets:
•

Base System

•

Kernel Configuration Files

•

TCPIIP Networking Utilities

•

Network File System Utilities

•

Extended (Berkeley) Mailer

If your system is licensed to install ULTRIX Worksystem Software, the following
supported software subsets are also loaded during the basic installation:

1-2 Preparing for the Installation

•

XIIIDECwindows Servers

•

XIl1DECwindows User Environment

•

XIl1DECwindows 75dpi Fonts

The basic installation performs the following tasks:
•

Builds the kernel

•

Reboots the ULTRIX operating system

If after completing the installation you decide that you want additional subsets, you
can install these subsets using the setld utility. See the setld(8) reference page
for further information.

1.1.3 The Advanced Installation
If you choose the advanced installation you can select the default disk partitions and
the default file system layout, or you can decide on which disks you want the file
systems to reside. The advanced installation also lets you select and install some or
all of the optional subsets. You should choose this path only if you are experienced
with ULTRIX file systems or if you require the ability to perform tasks such as the
following:

•

Preserving customized partitions

•

Selecting file system layouts other than the default layouts

•

Allocating the /usr file system to any disk partition on your system

•

Allocating up to two swap areas to any disk partition on your system

•

Allocating the crash dump space to the same disk partition as one of the swap
areas or allocating it to a different disk partition

•

Allocating the var area to the same disk partition as /usr or allocating it to a
different disk partition

•

Selecting optional subsets

•

Adding options to the kernel configuration file

Performing these tasks during the advanced installation has the following advantages:
•

It allows for greater flexibility in allocating the file systems to the most
appropriate disk partition.

•

It lets you tailor the ULTRIX operating system to suit the needs of your site. For
example, if your system has multiple disks, you may want to place some of the
mandatory file systems on disks other than the system disk. This may improve
your system's performance.

Before you begin an advanced installation, you must know the size and location of
the areas you are going to allocate and which subsets you are going to select.
Chapter 2 contains a set of worksheets to help you plan your system. Fill out these
worksheets before you begin an advanced installation.

Preparing for the Installation 1-3

Note

Advanced installations are required for VAXstation 3520 and 3540
systems.

1.1.4 The System Management Option
The system management option creates a standalone ULTRIX environment. The
standalone environment supports the initial phases of an installation as well as
limited system management activities.
The standalone ULTRIX environment includes commands that assist in recovering
from root file system corruption and help perform general file system and disk
maintenance tasks. You should perform system management tasks in the standalone
ULTRIX environment only if you have extensive ULTRIX or UNIX operating
system experience.

1.2 Checking the Hardware Needed for Installation
To perform the installation you need to understand how to operate your system. The
documentation provided with your processor provides operating and troubleshooting
instructions.
You may also need some or all of the following hardware:
•

Software distribution device
You need a distribution device that corresponds with the software distribution
media. For example, if you have a TK50 software kit, you need a TK50 or TK70
tape drive. Load the media supplied with the software distribution kit on the
appropriate drive. See your hardware documentation for instructions on how to
load media. If you are installing from a RIS area, see your server administrator
for instructions.

•

System disk
The system disk is the disk from which you will boot your system. You should
know how to load a disk pack (if it is removable) on your disk drive. You should
also know how to get the disk ready for read/write operations. See your hardware
documentation for information.

•

Data disks
A data disk is a device on which you can store data files. In most cases, you do
not need any data disks to install the ULTRIX system. However, if you perform
an advanced installation, you can allocate certain file systems to a disk other than
the system disk. If you are going to perform an advanced installation and are
going to use data disks, back up any data on the disks before you begin.

•

Console terminal
You use the console terminal to communicate with your system during the
installation. Depending on your system and its configuration, you can perform the
installation at either a hardcopy or a video terminal.

The rest of this section does not apply to the following processors:
•

DEC station 2100/3100/3100S

1-4 Preparing for the Installation

•

.DECstation 5000, Model 100 and 200 series

•

Personal DEC station 5000, Model 20 and 25

•

DECsystem 3100

•

DECsystem 5000, Model 25

•

DECsystem 5000, Model 200 series

•

DECsystem 5810/5820

•

DECsystem 5900

•

Micro VAX 2000, VAX server 2000, VAXstation 2000

•

MicroVAX 3100, VAXserver 3100, VAXstation 3100

Check with a Digital Field Service representative to ensure that your hardware is
installed at the default control status register (CSR) addresses. If you have hardware
installed in the floating address space and it does not adhere to the standard algorithm
for address assignments, you should perform an advanced installation. The advanced
installation lets you modify these address assignments in the system configuration
file. After you modify these address assignments, the installation software should
successfully build the kernel.
To perform an advanced installation, you should understand the format of the system
configuration file and know how to use the ed editor. If you do not, then you should
have a Digital Field Service representative install your hardware at the standard CSR
addresses before you start the installation. See the Guide to Configuration File
Maintenance for information about the configuration file.
Note

For UNIBUS and Q-bus controllers, the ULTRIX operating system must
be installed on a system disk connected to a disk controller set at the
primary CSR address. If you have a disk controller at a secondary CSR
address, have a Digital Field Service representative switch the CSR
address so that the system disk is connected to the primary CSR.

1.3 Checking the Software Distribution Kit
Use the Bill of Materials to check your software distribution kit. The software
distribution kit includes this installation guide and one of the following:
•

A TK50 for systems with TK50 or TK70 tape cartridge drives

•

A CDROM optical disc kit for systems with RRD40 or RRD42 optical disc
drives

•

A MT9 magnetic tape kit for systems with magnetic tape drives

Systems that use a software distribution kit supplied by a remote server require the
use of the network. If you plan to install software over the local area network, find
out from your system administrator whether the network kit is set up and ready for
use.

Preparing for the Installation 1-5

1.4 Backing Up the System
Whether you perform an upgrade or an installation, you should back up your system
before starting the procedure.

1.4.1

Backups Before Upgrades
Before you begin an upgrade procedure, you should back up your system disk so you
can restore your system to known state should any errors occur during the upgrade
procedure.

1.4.2

Backups Before Basic and Advanced Installations
When you perform a basic or an advanced installation, the installation software
initializes the system disk, overwrites all files and data residing on the system disk,
and may overwrite any changes to disk partition sizes you made using the chpt
command. The installation software does not overwrite partition size changes you
have made on data disks.
If you are currently running an operating system, back up your system disk before

beginning the installation. The backup procedure is described in the Guide to Backup
and Restore. If you plan to perform the advanced installation, you should also back
up any data disks you plan to use.
Before you begin the installation, you may want to save certain files to retain
information specific to your site. Some files are not meant to be restored after the
installation, for example the get tytab file. Other files, for example your existing
hosts file, can be restored so that you do not need to retype them.
Table 1-1 lists the directory name and the file name for the files that you may want to
back up.

1-6 Preparing for the Installation

Table 1-1: Names of Directories and Files to Back Up
Directory

File

.cshrc
.profile

.login
.rhosts

.mailrc

/etc

acucap
aliases.pag
dumpdates
gettytab
hosts.equiv
phones
remote
sendmail.fc
services
termcap

aliases
automount.master
exports
group
passwd
printcap
resolv.conf
sendmail.hf
svc.conf
ttys

aliases.dir
crontab
fstab
hosts

/usr/var/adrn

aculog

lastlog

lpd-errs

/usr/var/uucp

L.cmds
LIST.NIGHT
uucp.longhall
uucp.week

LIST.DAY
LIST.NOON
uucp.night
USERFILE

LIST.HOUR
uucp.hour
uucp.noon

rc.local
sendrnail.cf
sendrnail.st
svcorder

You may also want to save the syslog file from the /usr/var/spool/mqueue
directory.
In addition to your site-specific files, you need to save the following:
•

If your system runs as a master or a slave Yellow Pages (YP) server, save the
/usr /var /yp/ domain-name directory for your domain.

•

If your system runs as the master YP server and the master copies of the files
used to create the YP maps are located in a separate directory, such as
/usr /var /yp/ src, save this directory as well.

•

If your system runs as a BINDlHesiod primary server, save the named. boot
file in the /usr /var / dss /narnedb default directory, all database files named
in the named. boot file, and the /usr /var / dss /narnedb/ src directory,
where the source files are located. Database files have . db extensions, source
files have . rev extensions.

1.4.3 The Next Step
If you are performing an upgrade, continue the procedure with Chapter 5. If you are
performing a basic installation, continue the installation procedure with Chapter 3. If
you are performing an advanced installation, continue the installation procedure with
Chapter 2. If you are performing system management tasks, continue with Chapter 7.

Preparing for the Installation 1-7

Planning Your Disk Space

You need to complete the following tasks before starting the advanced installation:
•

Identify available disks

•

Plan the swap space

•

Plan the crash dump space

•

Plan the var area

•

Plan the / u s r file system

•

Plan the kernel configuration file items

•

Decide whether to use the default disk partition layout or the existing disk
partition layout if you have modified the default disk partitions, and change the
partition layout if necessary

This chapter provides a summary of what you need to consider before determining
which disk partition is suitable for the file systems, swap space, and crash dump
space. It assumes that you know the contents of the file systems and understand the
concepts associated with allocating a file system to a disk partition. If you are unsure
of these concepts, see the following guides for more detailed conceptual information:
•

Guide to Disk Maintenance

•

Guide to System Crash Recovery

•

Guide to Configuration File Maintenance

In several sections of this chapter, you will need to complete worksheets that pertain
to the size of the file system being discussed. Many of the ULTRIX commands that
you may use before and after the installation give disk space size in different units.
For example, the chpt command gives the size of partitions in blocks or sectors.
However, the df command measures the space in kilobytes. The subset sizes are also
given in kilobytes. To aid you in determining disk space requirements, keep in mind
the following equations:
•

One kilobyte (KB) equals 1024 bytes.

•

One block equals 1/2 KB (512 bytes); a sector is the same as a block.

•

One megabyte (MB) equals 1024 KB (1,048,576 bytes), or 2048 blocks.

For example, to determine the size in MB of the default disk partitions for an RA70
disk, divide the length in blocks (as shown in ra(4)) or the size in blocks (as
displayed by the chpt command) by 2048:

Partition

Size in Blocks

Size in MB

32768

131072

547041

267

163840

471041

230

76001

383201

187

When you examine disk partitions with the chpt command or look in the ULTRIX
Reference Pages you are looking at the partitions as if they were unformatted. To
account for the ULTRIX file system when determining the size your disk partitions
need to be, subtract 16 percent of the size of the partition to give you the total
available space.
The information presented in Section 2.1 through Section 2.5 will enable you to
complete the summary worksheet in Section 2.6. When complete, this worksheet
will give you the complete layout of the file systems that you will be asked about
during the advanced installation.

2.1

Identifying Supported System Disks
Your system disk must be a supported bootable device. Table 2-1 lists possible
system disks and their associated ULTRIX mnemonics. If you are installing a system
for the first time, you will need to refer to the reference page for your system disk in
Section 4 of the ULTRIX Reference Pages for information on the default disk
partition layout.

Table 2-1: Supported System Disks
ULTRIX Mnemonic

Device Name

RM05

RA60, RA70, RA80, RA81, RA82, RA90,
RA92, RD53, RD54, RF30, RF31, RF71

RD53 (MicroV AX 2000 and VAXstation 2000
only), RD54 (MicroVAX 2000 and VAXstation
2000 only)

RZ23, RZ23L, RZ24, RZ25, RZ55, RZ56, RZ57

Note
RD53, RZ23, and RZ23L disks are not supported as single-system disks.
You will need a second suitably sized disk to perform the installation.

2-2 Planning Your Disk Space

The system disk contains the root file system and the swap 1 space. The unit number
for the system disk must be in the range 0 to 254 for ra-type devices or in the range 0
to 31 for the other types of devices.
Complete the worksheet in Table 2-2 to identify what disks are in your system's
configuration. Though the worksheet shows only four devices, you can configure a
maximum of 96 ra-type devices and 32 devices of other types into your system.
U sing the hardware documentation that came with your system and the associated
reference page for your disks, write in the disk type, the mnemonic for that disk, and
the size of each partition in MB. You will need to refer back to this worksheet when
completing the worksheets in the following sections.
If you are upgrading from an existing ULTRIX system or installing a new system on
a disk currently being used, use the chpt command with the -q option to look at
the existing disk partition layout on the disk or disks you intend to use. For example,
if the disk on which you want to install the system is an RA70 on unit 0, issue the
following command:
# chpt -q /dev/rraOa

The existing disk partition layout is displayed.

Table 2-2: Disk Configuration Worksheet

Disk Number

Device Name

ULTRIX Name

Partition

Partition
Size in MB

a
b

c
d

e
f
g

a
b

c
d

e
f
g

a
b

c
d

Planning Your Disk Space 2-3

Table 2-2:

(continued)

Disk Number

Device Name

ULTRIX Name

Partition

Partition
Size in MB

f
g

a
b

c
d

e
f

2.2 Planning the Swap Space
The swap space is the area on a disk used by the kernel to transfer processes into and
out of physical memory. The advanced installation lets you allocate two swap areas:
swapl and swap2. (You can allocate additional swap space during day-to-day system
management. See the Guide to Configuration File Maintenance for instructions on
how to do this.)
Allocate the swap I space either by accepting the default or by specifying another
partition. If you choose the default allocation, the installation software allocates the
swap 1 space to the b partition of the system disk. There is no default allocation for
swap2 space.

Note
If you choose a partition that overlaps the a partition, where customized

partition information resides, you will overwrite any customized partition
table that describes the disk you selected and overwrite the superblock.
For this reason the installation software does not include the a partition
in the list of partitions available for the swap area.
The size of the swap space should be at least two to three times the processor's
physical memory size. If your system is devoted to users that might be running
numerous large programs, your swap space will need to be more than three times the
size of physical memory.
If you plan to allocate a second swap space, you can divide the required size between

the two. For example, if you need lOO MB of swap space, you could allocate 50 MB
to the swap 1 space and 50 MB to the swap2 space. Dividing the swap space will
improve swapping performance.

2-4 Planning Your Disk Space

Note
If you plan to allocate the crash dump space (see Section 2.3) to the

same disk partition as the swap space, the swap space must be on a disk
connected to the same controller as the system disk.
To determine the size and record the location of the swap space areas, fill in the
following blanks:
1. The memory in MB for your processor is _ _ _ __
2. Therefore, you need
MB (two or three times main memory,
depending on the number and size of processes running) to accommodate your
swap space.
3. Refer to the worksheet in Table 2-2 to identify partitions that are large enough for
your swap spaces.
4. Record the location of the swap space as follows:
Swap Space

Size in MB

ULTRIX Name

Disk Number

Partition

swap!
swap2

2.3 Planning the Crash Dump Space
The crash dump space is the area on the disk where the kernel writes the memory
contents in the event of a system crash.
Allocate the crash dump space by accepting the default or by specifying another
partition. You can allocate the crash dump space either to the same partition as swap 1
or swap2, or to another partition. If you choose the default allocation, the installation
software allocates the crash dump space to the b partition of the system disk.
The ULTRIX operating system provides two types of crash dumps: partial and full.
You can use either partial or full crash dumps, but not both.
Partial crash dumps, the default, write only part of the memory's contents to the
crash dump space. This minimizes the amount of disk space needed to hold crash
dumps. Use Table 2-3 to help determine the space needed for partial crash dumps
based on physical memory size of your system and its maximum number of users.
Full crash dumps write the entire contents of memory to the crash dump space. For
full crash dumps, the size of crash dump space needed must be at least equal to the
size of memory plus the size of the kernel, vmunix. The size of the kernel can be
up to approximately 4.1 MB. See the Guide to System Crash Recovery for more
information about calculating crash dump space.
Note

The crash dump space must be on a disk connected to the same
controller as the system disk.

Planning Your Disk Space 2-5

Table 2-3: Partial Crash Dump Space Requirements
Physical Memory
inMB

Maximum Number
of Users

Space Needed
for RiSe (MB)

Space Needed
for VAX (MB)

6
8
16
32
64
128
256
512

2
2
16
32
64
128
128
256

not applicable
8
14
20
28
40
40
48

6
8
10
12
16
26
26
34

To determine the size and record the location of the crash dump space, fill in the
following blanks:
1. The memory in MB for your system is _ _ __
2. The maximum number of users allowed on your system is _ _ __
3. You need
MB to accommodate your crash dump space. For partial
dumps, select a value from Table 2-3. For full dumps, this value must be at least
equal to the amount of memory.
4. Refer to the worksheet in Table 2-2 to identify partitions that are large enough for
your crash dump space.
5. Record the ULTRIX name, disk number, and partition where you plan to allocate
the crash dump space. See Table 2-2 to identify partitions that are large enough
to allocate the crash dump space.
ULTRIX Name

Disk Number

Partition

2.4 Planning the var Area
The var area contains volatile, machine-specific directories and files, like tmp,
spool, and adm.
You can allocate the var area either as a file system on its own partition, or as a
directory in the / u s r file system. If you choose the default allocation, the
installation software allocates the var area as the directory /usr /var.
In determining the size of the var area, you need to consider the following:
•

The crash dump space

•

The error logger

•

System accounting

•

The size of the var / adm/ r is directory, if appropriate for your system

The following sections briefly describe how these items affect the size of var.
Complete the worksheet in Section 2.4.5 as you work through the sections.

2-6 Planning Your Disk Space

2.4.1

Size of the var/adm/crash Directory
The file system requires room to accommodate the crash dump space. When the
system crashes, the savecore utility writes a partial copy (for partial dumps) or a
complete copy (for full dumps) of main memory (vrncore) and the vrnunix image
located in the root file system into the swap space. When the system comes back up,
savecore writes these copies of vrncore and vrnunix to files located in the
var / adm/ crash directory.
The var / adm/ crash directory should have at least the amount of space you
recorded in Section 2.3. This should give you enough space for one crash dump. See
the Guide to System Crash Recovery for more information about calculating crash
dump space.
Fill in the first item of the worksheet in Table 2-4 with the size of the crash dump
space.

2.4.2

Error Logger
The var file system requires room to accommodate the error log. The error log is a
record of system- and hardware-related errors in a binary file. If you are creating a
new system and have never had an error log file, then estimate your requirements
using the following guidelines:
•

The error logger records about 1 MB per week on a processor that has 25 MB of
memory and is connected to two tape drives, 10 disk drives, 1 DMB serial port,
and 1 Ethernet interface. If you back up or remove the error log file once a
month, then you need to plan for an error log file that is about 4 MB.

•

Increase this recommended number if you have a processor with more memory, a
greater number of peripheral devices, or peripheral devices that experience
numerous errors. You should also increase the recommended number to
accommodate any remote processors that log in to the local processor.

•

Increase this recommended number if your system is connected to a Computer
Interconnect (CI) network. The error logger records errors for all systems and
devices attached to the CI. Applying the first guideline in this list for each system
attached to the CI, you can estimate the amount of error logging each system
generates. Then add together the total for each system to give you the total error
logging space your system needs.

•

Decrease this recommended number if you have a processor with less memory or
a smaller number of peripheral devices.

The Guide to the Error Logger provides more information on the error logger.
Fill in the second item of the worksheet in Table 2-4 with the amount of space
needed for the error logger.

2.4.3

System Accounting
The adm directory in the var area contains data files generated by administrative
programs such as acct, aculog, and wtrnp. The data that these programs generate
can vary widely from system to system and over time. For example, the file
adm/ acct in the var area can easily grow by 50 KB a day for a large system and
by 5 KB for a workstation. As a general guideline for system accounting, you should
allot 10 KB per day for workstations and 100 KB per day for larger systems. If you
back up or remove the system accounting file once a month, then you need to plan

Planning Your Disk Space 2-7

for accounting files that occupy about 300 KB for workstations and 3 MB for large
systems. See the Guide to Disk Maintenance for more information on the space
requirements for system accounting.
Fill in the third item of the worksheet in Table 2-4 with the amount of space needed
for system accounting.

2.4.4

Size of the var/adm/ris Directory
If you are going to set up a network kit on your system, you can choose to transfer
software subsets from distribution media to the adm/ r is directory in the var area.
Anyone with a processor from the VAXstation, MicroVAX, DEC station, or certain
DECsystem series of processors can then install the software subsets residing in this
directory using the Ethernet. See the Guide to Sharing Software on a Local Area
Network for more information on setting up the network kit.
You must reserve enough space in the adm/ris directory in the var area for the
software you want to install. See Appendix A (for RISC processors) or Appendix B
(for VAX processors) for a brief description of each software subset and the names of
any other subsets or kernel configuration file options related to its operation and the
Release Notes for the subset sizes.
Fill in the fourth item of the worksheet in Table 2-4 with the amount of space needed
for the adm/ris directory in the var area.

2.4.5

Completing the var Worksheet
Complete the worksheet in Table 2-4 to determine the space requirements for the
var area.

Table 2-4: var Worksheet
Item

Obtain number from ...

Crash dump space

Section 2.4.1

Error logger

Section 2.4.2

System accounting

Section 2.4.3

Size of the
var/adm/ris
directory

Section 2.4.4

Total for var

TOTAL

If you plan on using a separate partition for the var area, record the ULTRIX name,
disk number, and partition where you plan to allocate the var file system:
ULTRIX Name

2-8 Planning Your Disk Space

Disk Number

Partition

2.5 Planning the lusr File System
The lusr file system is the directory structure that contains such directories as
lusr I sys, lusr I adm, and lusr Ibin.
You must allocate the lusr file system, either by accepting the default or by
specifying another partition. If you choose the default allocation, the installation
software allocates the g partition of the system disk.
In determining the size of the lusr file system, you need to consider the following:
•

The software subsets you plan to install on lusr

•

The amount of user space needed

•

The size of the var area if it is on the same partition as lusr

The following sections briefly describe how these items affect the size of lusr.
Table 2-5 contains a worksheet that you will complete by working through the
sections.

2.5.1

Software Subsets Within the lusr File System
The lusr file system requires room to accommodate the software subsets that will
reside within it. A software subset is a collection of executable files and data files
needed to perform a specific function or provide a particular class of services. For
example, the Document Preparation Extensions provide tools for the online reference
pages, such as nroff and catman.
Use the tables in the Release Notes that list RIse and VAX subset sizes to determine
the amount of space to allocate for the subsets you plan to install. The mandatory
subsets are always installed. The optional subsets are not needed for your system to
function; you can choose none, some, or all of the optional subsets depending on
your system requirements and available space. Select the subsets that you want to
install and add their sizes together. Record the totals in the spaces provided.
See Table A-I (for RISe processors), or Table B-1 (for VAX processors) for
descriptions of the software subsets and a list of other subsets and kernel
configuration file options related to each subset.
Fill in the first item of the worksheet in Table 2-5 with the amount of space needed
for all the subsets you plan to install.

2.5.2

User Area
The advanced installation does not provide an area for user files. You need to set up
this area after the installation. However, you should still take this amount of space
into consideration when planning your system. As a guideline, you should reserve at
least 10MB of disk space for each user on your system. For example, if there are 10
users, you should reserve a minimum of 100 MB of disk space.
If you intend to set quotas on the user area, multiply the quota for each user by the
number of users to determine the amount user space. See the Guide to Disk
Maintenance for information on disk quotas.

Fill in the second item of the worksheet in Table 2-5 with the amount of space
needed for the users directory.

Planning Your Disk Space 2-9

2.5.3

var Area
If you plan to place the var area on the same partition as /usr, you must add the
size of the var area that you determined with the worksheet in Table 2-4 to the total
of /usr.
If appropriate for your system, fill in the third item of the worksheet in Table 2-5
with the amount of space needed for var.

2.5.4

Completing the lusr Worksheet
Complete the worksheet in Table 2-5 to determine the space requirements for the
/usr area.

Table 2-5: lusr Worksheet
Item

Obtain Number From ...

Software subsets

The Release Notes

Size of the user area

Section 2.5.2

Size of the var area

Table 2-4 for the var total

Total for lusr

TOTAL

Refer to Table 2-2 to identify partitions that are large enough for the /usr file
system.
Record the ULTRIX name, disk number, and partition where you plan to allocate the
/usr file system:
ULTRIX Name

Disk Number

Partition

2.6 Determining the Disk Partition Layout
After you determine how much space your system requires for each file system, you
need to determine whether you can accept the default disk partition layouts or
whether you want to modify the disks with the chpt command to use a customized
partition layout.
If you modify the partition tables for the system disk, the partitions for root and

swap 1 must meet the following minimum space requirements:
•

The root or a partition must be at least 32,768 blocks (16 MB).

•

The swap or b partition must be at least 12,288 blocks (6 MB). This assumes that
you plan to add a second swap device.

If the modified partitions do not meet these requirements, then the advanced

installation imposes the default partition table for the system disk. No other disks on
the system are affected.
Complete the worksheet in Table 2-6 by entering the values that you determined in
the previous sections. This table will give you the complete file system layout and
2-10 Planning Your Disk Space

space requirements for your system.

Table 2-6: File System Worksheet
Items

Approximate Size

Disk

Partition

(--)

Root (from Table 2-2)
swap 1 (from Section 2.2)
swap2 (from Section 2.2)
Crash dump space (from Section 2.3)
/var (from Table 2-4; fill in disk
and partition lines if applicable)
/usr Total:

After completing the worksheet, you need to ensure that the disk partitions are laid
out the way you want them. If you are installing a system for the first time, refer to
Table 2-2 and to Section 4 of the ULTRIX Reference Pages for the default partition
layout for your disk or disks.
Compare the disk partition layout with the total values in Table 2-6. If a file system
(excluding swap) is immediately going to consume more than 75 percent of its
intended disk partition not including the 16 percent of the partition that the ULTRIX
file system consumes, you may want to expand the disk partition, if possible.
Assuming that you have a valid backup of your current system (if appropriate) and
that you are experienced with ULTRIX file systems, you can modify disk partitions
by choosing the System Management option of the installation procedure to enter the
standalone ULTRIX environment. This environment loads a memory-resident
ULTRIX kernel on your system and gives you access to the commands you need to
change the partitions. See Chapter 7 for information on the standalone ULTRIX
environment.

2.7 Planning the Configuration File Entries
Certain layered products require that an entry be added to your system's
configuration file for that product to work. For example, DEC net requires an entry in
the configuration file.
When you choose the kernel option corresponding to each configuration file entry,
the advanced installation procedure updates the configuration file before it builds the
kernel, vmunix.
If you plan to use any of the features listed in Table 2-7 now or in the future, add the
relevant entry during the advanced installation. If you include them during the

installation, the products that use these features will function immediately after they
are installed. Otherwise, when you are ready to install a product, you will need to add
the necessary entry in the configuration file and then rebuild the kernel.
Note that including the entry in the configuration file does not mean that the product
is installed.

Planning Your Disk Space 2-11

Table 2-7: Configuration File Entries
Kernel Option

Description

Local Area Transport
(LAT)

Gives you the kernel options and
devices required to facilitate
communications with Digital's Ethernet
local area terminal server.

Bisynchronous
Communication
protocol (VAX only)

Gives you access to the 2780 and 3780
remote job entry terminals.

Computer Interconnect
(CI) network

Gives you kernel options and devices
required to use the internet protocols
on the CI wires.

DiagnosticlUtilities
Protocol (DUP)

Provides a method of communication
between a host class driver and a server
in the controller. DUP defines the
communications between a host control
program and a remote program in the
controller.
DUP requires one of the following
devices to be configured on the system:
bvpssp, ci, msi, or uq.

IS09660 File System
Support (CDFS)

Allows you to access an IS09660
formatted CDROM as a local, readonly file system.

Ethernet packet filter

Allows you to implement networking
protocols without modifying the kernel,
and allows you to monitor the network
by receiving packets destined for
machines other than your own.

Enhanced security
features

Give you audit, additional identification
and authentication mechanisms, and
trusted path. Note that adding the audit
and the additional identification and
authentication mechanisms at
installation time will not activate these
options. See the Security Guide for
Administrators for further information.

DECnet

Gives you the kernel options required
to facilitate the use of the DECnet
networking protocols.

Add?

All of the configuration
options listed
None of the
configuration options
listed

Depending on your hardware configuration, you may need to edit your system's
configuration file even if you choose to add kernel options during the advanced

2-12 Planning Your Disk Space

installation. You will need to edit the configuration file in the following situations:
•

Your system's configuration does not conform to control status register (CSR)
address assignment rules.

•

You have disk controllers in floating address space.

•

You have both KDA50 and RQDX controllers on the Q-bus.

For more information on editing your system's configuration file, see the Guide to
Configuration File Maintenance.
Now you are ready to begin the installation.

Planning Your Disk Space 2-13

Booting the System

Before you can install the ULTRIX software, you must prepare the hardware for the
installation and then boot the system from the installation media. How you do this
depends on which processor you have.
If you are using a TK50 tape kit or a MT9 tape kit to boot your system, or are
booting the standalone kernel for system management tasks, follow the instructions
included with the kit. If you are using a CDROM optical disc to boot your system,
follow the instructions in the hardware manual included with the CDROM.

Another way to boot your system is over the network. You boot your system from
the network when you are:
•

Initiating an installation from a remote server

•

Booting a diskless system

•

Booting a standalone kernel from a remote server in order to perform system
management tasks

To boot over the network, you must be registered as a client on a DMS or RIS
server. See the Guide to Sharing Software on a Local Area Network for information
on registering your system.
Look for your processor in Table 3-1 and find the section in this chapter that gives
booting instructions for your processor. Follow the instructions in that section and
then continue the installation procedure with Chapter 4 if you are performing a basic
or an advanced installation, or Chapter 5 if you are performing an upgrade
installation.
Table 3-1: Location of Processor-Specific Boot Instructions
Processor

Section

DEC station 2100

Section 3.1

DEC station 3100

Section 3.1

DEC station 3100S

Section 3.1

DEC station 5000, Model 100 series

Section 3.2

DEC station 5000, Model 200 series

Section 3.2

Personal DEC station 5000, Model 20 & 25

Section 3.2

DECsystem 3100

Section 3.1

DEC system 5000, Model 25

Section 3.2

DEC system 5000, Model 200 series

Section 3.2

DECsystem 5100

Section 3.3

DECsystem 5400

Section 3.4

DECsystem 5500

Section 3.5

Table 3-1:

(continued)

Processor

Section

DEC system 5810

Section 3.6

DECsystem 5820

Section 3.6

DEC system 5830

Section 3.6

DECsystem 5840

Section 3.6

DECsystem 5900

Section 3.2

MicroVAX II

Section 3.10

MicroVAX 2000

Section 3.7

MicroVAX 3100

Section 3.8

MicroVAX 3300

Section 3.9

MicroVAX 3400

Section 3.9

MicroVAX 3500

Section 3.10

MicroVAX 3600

Section 3.10

MicroVAX 3800

Section 3.10

MicroVAX 3900

Section 3.10

V AXserver 100

Section 3.10

V AXserver 2000

Section 3.7

VAX server 3100

Section 3.8

VAXserver 3300

Section 3.9

VAXserver 3400

Section 3.9

V AXserver 3500

Section 3.10

VAXserver 3600

Section 3.10

VAXserver 3800

Section 3.10

V AXserver 3900

Section 3.10

V AXserver 6000-nnn series

Section 3.14

VAXstation II

Section 3.10

V AXstation IIIGPX

Section 3.10

V AXstation 2000

Section 3.7

VAXstation 3100

Section 3.8

VAXstation 3200

Section 3.10

V AXstation 3500

Section 3.10

V AXstation 3520

Section 3.11

VAXstation 3540

Section 3.11

VAX-11/750

Section 3.12

VAX-11/780

Section 3.13

VAX-11/785

Section 3.13

VAX 6000-nnn series

Section 3.14

VAX 6210

Section 3.14

VAX 6220

Section 3.14

VAX 6230

Section 3.14

3-2 Booting the System

Table 3-1:

(continued)

Processor

Section

VAX 6240

Section 3.14

VAX 6310

Section 3.14

VAX 6320

Section 3.14

VAX 6330

Section 3.14

VAX 6340

Section 3.14

VAX 6350

Section 3.14

VAX 6360

Section 3.14

VAX 6410

Section 3.14

VAX 6420

Section 3.14

VAX 6430

Section 3.14

VAX 6440

Section 3.14

VAX 6450

Section 3.14

VAX 6460

Section 3.14

VAX 6510

Section 3.14

VAX 6520

Section 3.14

VAX 6530

Section 3.14

VAX 6540

Section 3.14

VAX 6550

Section 3.14

VAX 6560

Section 3.14

VAX 8200

Section 3.15

VAX 8250

Section 3.15

VAX 8300

Section 3.15

VAX 8350

Section 3.15

VAX 8500

Section 3.16

VAX 8530

Section 3.16

VAX 8550

Section 3.16

VAX 8600

Section 3.17

VAX 8650

Section 3.17

VAX 8700

Section 3.16

VAX 8800

Section 3.16

VAX 8810

Section 3.16

VAX 8820

Section 3.18

VAX 8830

Section 3.18

VAX 8840

Section 3.18

VAX 9000

Section 3.19

Booting the System 3-3

3.1

DECstation 2100/3100/31 OOS or DECsystem 3100 Processor
To prepare the DEC station 2100/3100/3100S or DECsystem 3100 hardware:
1. Turn on power to the console terminal and all additional peripheral devices.
2. Turn on power to the processor.
3. Remove any TKSO tape cartridges and CDROM optical discs from their
associated drives.
The console subsystem now prints an initial display and ends with the console mode
prompt:
»

The boot command you type depends on the software distribution kit: TKSO,
CDROM, or network. The boot command for each distribution kit is described in
this section.

3.1.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TKSO tape kit for inserting the tape into
the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 BOOTIUPGRADE
into the tape drive. Ensure the tape is online and ready to use.
3. Use the following command to determine the unit number of the drive for your
device:
»

test -c

A display appears that shows what is assigned to each unit number on your
system.
4. Use a command with the following syntax to boot your system:
boot -f tz(O, unit-number)

Replace unit-number with the unit number of your tape drive.
The following example shows the command to boot the system from tape drive
number S.
»

boot -f tz(O,S)

Next, the installation software displays some system information, followed by the
memory and hardware configurations.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.1.2

Booting from the CDROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the
hardware manual for inserting the optical disc into the caddy.

3-4 Booting the System

Follow this procedure to boot the system:
1. Load the CDROM optical disc with the label appropriate for your machine
architecture, either ULTRIXlUWS V4.3 (RISC) SUPPORTED or ULTRIXlUWS
V4.3 (VAX) SUPPORTED, into the drive. Wait for the drive to be on line and
ready.
2. Use the following command to determine the unit number of the drive for your
device:
»

test -c

A display appears that shows what is assigned to each unit number on your
system.
3. Use a command with the following syntax to boot your system:
boot -f rz(O, unit-number,O)vmunix

Replace unit-number with the unit number of your optical disc drive.
The following example shows the command to boot the system from optical disc
drive number 4:
»

boot -f rz(O,4,O)vmunix

3.1.3

Booting from the Network
To boot the system over the network, type a command with the following syntax at
the console mode prompt:
boot -f mop(net-inteiface)

If you have more than one network interface, replace net-inteiface with the number
of the interface you want to use. If you have only one network interface, replace
net-inteiface with zero (0).

Booting the System 3-5

3.2 DECstation 5000 Series, DECsystem 5000 Series, Personal
DECstation 5000 Series, and the DECsystem 5900
Processor
To prepare these processors:
1. Tum on power to the console tenninal and all additional peripheral devices.
2. Tum on power to the processor.
3. Remove any TK50 tape cartridges and CDROM optical discs from their
associated drives.
The console subsystem now prints an initial display and ends with the console mode
prompt:
»

The boot command you type depends on the software distribution kit: TK50,
CDROM, or network. Before beginning, you must detennine the slot and device
numbers of your boot device.

3.2.1

Determining the Slot and Device Numbers of Your Boot Device
The instructions in this section assume that if you have multiple disk drives,
CDROM drives, or tape drives, you know which drive is your boot device.
If you are booting from a Small Computer System Interconnect (SCSI) device, check
the cabling of your hardware to determine which controller you are booting from.

3.2.1.1

Determining the Slot Number (Default)
To detennine which controllers and devices are configured on your system, type the
following command at the console prompt:
»

cnfg

This command displays the options present on the system. Your system will display
output similar to the following (the output will differ depending on your system
configuration):
7:KN02-AA
6: PMAD-AA
S:PMAZ-AA
2:PMAZ-AA
1 :PMAG-AA

DEC
DEC
DEC
DEC
DEC

VS.3a
VS.3a
vS.3a
vS.3a
T3.0a

TCFO
TCFO
TCFO
TCFO
TCFO

(16 MB)
(enet:08-00-2b-16-8S-7e)
(SCSI=7)
(SCSI=7)
(PXG--D=24)

The first column displays the slot numbers of the device controllers. The last column
displays the devices in each slot. If your system has more than one device in a
particular slot, a display similar to the following appears:
3: KN02-BA

DEC

XS.4g

TCFO

1: PMAG-CA

DEC

VS.3a

TCFO

3-6 Booting the System

(32 MB)
(enet: 08-00-2b-16-S8-d6)
(SCSI = 7)
(PX -- D=8)

3.2.1.2

Determining the Boot Device Number
To determine the device number of your boot device, type a command with the
following syntax:
cnfg sloCnumber

For example, to determine the device number of a SCSI disk drive with a controller
in slot 5, type the following command:
»

cnfg 5

The system displays a table similar to the following:
5:

PMAZ-AA

DEC

DEV

PID

rz3
tz5

RZ56

V5.3a

TCFO

(SCSI

= 7)

VID

REV

SCSI DEV

DEC

0200

DIR
SEQ

In the previous example, the disk drive is identified by the letters "rz". The device
number for the disk drive is 3 (rz3). The tape drive is identified by the letters "tz".
The device number for the tape drive is 5 (tz5).
Now that you know the slot number and the device number, you can boot your
system or set your system's environmental boot variable. Follow the directions given
in the appropriate booting sections.
If the command shows that you have multiple devices configured on the same
controller, you will have to know which device is the boot device. If you do not
know which device is the boot device, consult your system administrator.

3.2.2

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TK50 tape kit for inserting the TK50 into
the tape drive.
Follow this procedure to boot the system:
1. Make sure that your TK50 tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (RISC) BOOT
UPGRADE into the tape drive. Ensure the tape is online and ready to use.
3. To determine the device number of the SCSI tape, use the same slot number and
device number that were determined by the cnfg command in Section 3.2.1.2.
For example to boot a SCSI tape (tz) at slot 5, drive 5, type the following
command:
»

boot 5/tz5

You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.2.3

Booting from the CDROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the
hardware manual for inserting the optical disc into the caddy.

Booting the System 3-7

Follow this procedure to boot the system:
1. Load the CDROM optical disc with the label appropriate for your machine
architecture, either ULTRIXlUWS V4.3 (RISC) SUPPORTED or ULTRIXlUWS
V4.3 (VAX) SUPPORTED, into the drive. Wait for the drive to be on line and
ready.
2. Use a command with the following syntax to boot your system:
boot slocnumberlrzdevice_numberlvmunix

Replace slot-number with the slot number of the CDROM controller. Replace
device-number with the device number of your optical disc drive.
For example, to boot the system from optical disc drive number 4 on slot number
1, type the following command:
»

boot l/rz4/vmunix

You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.2.4

Booting from the Network
To boot the system from the network, use a command with the following syntax:
boot sloCnumberimop

Replace slot_number with the slot number of the network controller.
For example, to boot from the network on slot number 6, type the following
command:
»

boot 6/mop

3-8 Booting the System

3.3 DECsystem 5100 Processor
To prepare the DECsystem 5100 hardware:
1. Turn on power to the console terminal and all additional peripheral devices.
2. Turn on power to the processor.
3. Remove any TK50 tape cartridges and CDROM optical discs from their
associated drives.
The console subsystem now prints an initial display and ends with the console mode
prompt:
»

The boot command you type depends on the software distribution kit: TK50,
CDROM, or network. The boot command for each distribution kit is described in
this section.

3.3.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TK50 tape kit for inserting the tape into
the tape drive.
Follow this procedure to boot the system:
1. Make sure that your TK50 tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (RISC)
BOOTIUPGRADE into the tape drive. Ensure the tape is online and ready to
use.
3. Use the following command to determine the unit number of the drive for your
device:
»

conf

A display appears that shows what is assigned to each unit number on your
system.
4. Use a command with the following syntax to boot your system:
boot -f tz(O, unit-number}

Replace unit-number with the unit number of your tape drive.
The following example shows the command to boot the system from tape drive
number 5:
»

boot -f tz(O,5)

3.3.2

Booting from the CDROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the

hardware manual for inserting the optical disc into the caddy.

Booting the System 3-9

conf

A display appears that shows what is assigned to each unit number on your
system.
3. Use a command with the following syntax to boot your system:
boot -f rz{O,unit-number,O)vmunix

Replace unit-number with the unit number of your optical disc drive.
The following example shows the command to boot the system from optical disc
drive number 4:
»

boot -f rz(O,4,O)vmunix

Next, the installation software displays some system information, followed by the
memory and hardware c<?nfigurations.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.3.3

Booting from the Network
To boot the system over the network, type a command with the following syntax at
the console mode prompt:
boot -f mop{net-inte1jace)

If you have more than one network interface, replace net-inteiface with the number
of the interface you want to use. If you have only one network interface, replace
net-inteiface with zero (0).

3-10 Booting the System

3.4 DECsystem 5400 Processor
To prepare the DECsystem 5400 hardware:
1. Tum on power to the console terminal and all additional peripheral devices.
2. Tum on power to the DECsystem 5400 processor.
3. Remove any TK50 or TK70 tape cartridges from their associated drives.
The console subsystem prints an initial display, ending with the console mode
prompt:
»

Follow the instructions included with your TK50 tape kit for inserting the tape into
the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (RISC)
BOOTIUPGRADE into the tape drive. Ensure the tape is online and ready to
use.
3. To determine the unit number of the drive for your device, first enter the
following command to invoke the VAX console:
»

maint

When the VAX console prompt appears, enter the following command:
»> show device

A display appears that shows what is assigned to each unit number on your
system. Record the unit number of your tape drive, then enter the following
command to return to the RISC console:
»> exit

4. Use a command with the following syntax to boot your system:
boot -f tm(O, unit-number)

Replace unit-number with the unit number of your tape drive.
The following example shows the command to boot the system from tape drive
number 0:
»

boot -f tm(O,O)

Booting the System 3-11

3.5 DECsystem 5500 Processor
To prepare the DECsystem 5500 series processor hardware:
1. Turn on power to the console terminal and all additional peripheral devices.
2. Turn on power to the processor.
3. Remove any TK50 tape cartridges and CDROM optical discs from their
associated drives.
The console subsystem now prints an initial display and ends with the console mode
prompt:
»

The boot command you type depends on the software distribution kit: TK50,
CDROM, or network. Before beginning, you must determine the slot and device
numbers of your boot device.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.

2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (RISC)
BOOTIUPGRADE into the tape drive. Ensure the tape is online and ready to
use.
3. To determine the unit number of the drive for your device, first enter this
command to invoke the VAX console:
»

maint

When the V AX console prompt appears, enter the following command:
»> show device

A display appears that shows what is assigned to each unit number on your
system. Record the unit number of your tape drive, then enter the following
command to return to the RISC console:
»> exit

3.5.1

Booting from the SCSI Tape Device
Use a command with the following syntax to boot your system:
boot -f tz(O, unit-number)

Replace unit-number with the unit number of your tape drive.
The following example shows the command to boot the system from tape drive
number 0:
»

boot -f tz(O,O)

You have completed booting your system. Continue the installation procedure with
Chapter 4.

3-12 Booting the System

3.5.2

Booting from the Q-bus Tape Device
Use a command with the following syntax to boot your DECsystem 5500 from a
Q-bus tape:
boot -f tm(O, unit-number)

Replace unit-number with the unit number of your tape drive.
The following example shows the command to boot your DECsystem 5500 from tape
drive number 0:
»

boot -f tm(O,O)

You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.5.3

Booting from the CDROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the
hardware manual for inserting the optical disc into the caddy.

show devices

A display appears that shows what is assigned to each unit number on your
system.
3. Use a command with the following syntax to boot your system:
boot -f rz(controller-number, unit-number,O)vmunix

Replace controller-number with the controller number. Replace unit-number with
the unit number of your optical disc drive.
The following example shows the command to boot the system from optical disc
drive number 4:
»

boot -f rz(O,4,O)vmunix

3.5.4

Booting from the Network
To boot the system over the network, type a command with the following syntax at
the console mode prompt:
boot -f mop(net-inteiface)

Booting the System 3-13

If you have more than one network interface, replace net-inteiface with the number
of the interface you want to use. If you have only one network interface, replace
net-inteiface with zero (0).

3-14 Booting the System

3.6 DECsystem 5810/5820/5830/5840 Processor
To prepare the DECsystem 5810/5820/5830/5840 hardware:
1. Tum on power to the console terminal and all additional peripheral devices.
2. Tum on power to the processor.

3. Remove any TK50 or TK70 tape cartridges from their associated drives.
The console subsystem now prints an initial display and ends with the console mode
prompt:
»

2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (RISC) BOOT
UPGRADE into the tape drive. Ensure the tape is on line and ready to use.
3. To determine the node number of the drive for your device, use the following
command:
»

show config

A display, similar to the following, appears on your screen. It shows shows what
is assigned to each slot number on your system:
1+
2
9+
E+
XBI
1+
2+
4+
6+
C+

Type
KN58A/A
KN58A/B
MS62A
DWMBA/A
E
DWMBA/B
KDB50
CIBCA
TBK70
DEBNI

(8081)

Rev
0000

(4001)
(2001)

0002
0002

(2107 )
(010E)
(0108)
(410B)
(0118)

OOOA
131C
41C2
0307
0100

Record the slot number of your XMI-to-BI bus adapter (XBI), which is
hexadecimal E in the example. Also record the node number of your TBK70
controller, which is 6 in the example. (Do not include the plus sign (+) that
appears in the output.)
4. Use a command with the following syntax to boot your system:
boot -f tms(/xOxslot-numberlbnode-number, unit-number)
Replace slot-number with the slot number of your XBI adapter. Replace nodenumber with the node number on the XBI where your TBK70 controller is
located. Replace unit-number with the unit number of your TBK70 controller.
The unit number is always the same as the node number on the XBI where your
TBK70 controller is located.
The following example shows the command to boot the system from XBI slot E

Booting the System 3-15

for a TBK70 controller located on XBI node 6:
»

boot -f tms(/xOxe/b6,6)

3-16 Booting the System

3.7 MicroVAX 2000, VAXserver 2000, or VAXstation 2000
Processor
The following instructions assume you have no bootable software on any device in
your system. To prepare the Micro VAX 2000, VAXserver 2000, or VAXstation 2000
hardware:
1. Set the system unit on/off switch to 1 (on).
2. Turn on power to the disk expansion box (if present).
3. Tum on power to the TZKSO expansion box (if present).
4. Turn on power to peripheral devices, such as printers or modems.
S. Remove any TKSO tape cartridges and RXSO or RX33 diskettes from their
associated drives.
After about 20 seconds, the monitor displays a power-up test sequence similar to:
KA410 Vl. 0
F ... E ... D ... C ... B ... A ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ...

The first line is hardware revision information.
The second line is a countdown of the system self-test diagnostics. The
countdown may be followed by some status or error messages. The owner's
manual explains these status and error messages and also how you can tell
whether the self-test passed.
6. After the system finishes the self-test countdown, press the halt button on the rear
of the system unit. The console mode prompt appears:
»>

You are now ready to boot the system. The boot command you type depends on the
software distribution kit: TKSO or network. The boot command for each distribution
kit is described in this section.

3.7.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TKSO tape kit for inserting the TKSO tape
into the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to
use.
3. Type the following at the console mode prompt:
»> b muaO

Booting the System 3-17

3.7.2

Booting from the Network
To boot the system over the network, type the following command at the console
mode prompt:
»> b esaO

3-18 Booting the System

3.8 MicroVAX 3100, VAXserver 3100, or VAXstation 3100
Processor
The following instructions assume you have no bootable software on any device in
your system. To prepare the MicroVAX 3100, VAX server 3100, or VAXstation 3100
hardware:
1. Set the monitor on/off switch to 1 (on).
2. Tum on power to all disk expansion boxes (if present).
3. Tum on power to all TZK50 and CDROM optical disc expansion boxes (if
present).
4. Set the system unit on/off switch to 1 (on).
5. Tum on power to peripheral devices, such as printers and modems.
6. Remove any TK50 tape cartridges and CDROM optical discs from their
associated drives.
After about 20 seconds, the monitor displays a power-up test sequence similar to
this:
KA42-B Vl. 0

F ... E ... D ... c ... B ... A ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ...

The first line is hardware revision information.
The second line is a countdown of the system self-test diagnostics. The
countdown may be followed by some status or error messages. The owner's
manual explains these status and error messages and also how you can tell
whether the self-test passed.
7. Press the halt button on the rear of the system unit after the system finishes the
self-test countdown. The console mode prompt appears:
»>

You are now ready to type the boot command. The boot command you type depends
on the software distribution kit: TK50, CDROM, or network. The boot command for
each distribution kit is described in this section.

3.8.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TK50 tape kit for inserting the TK50 tape
into the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOTIUPGRADE into the tape drive. Ensure the tape is on line and ready to
use.

Booting the System 3-19

3. Type the following command to determine the drive from which to boot:
»> show device

After several seconds, a nine-column table is displayed. You need the following
information from this table:
-

The logical device name, which is shown in column 1.

The physical device name, which is shown in column 8.

4. Type the boot command at the console mode prompt, using the logical device
name determined by the show device output.
For example, a TZ30 or TZK50 device connected to SCSI controller A with SCSI
bus ID number 5 would require a boot command like the following:
»> b mkaSOO

3.8.2

Booting from the COROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the
hardware manual for inserting the optical disc into the caddy.

Follow this procedure to boot the system:
1. Load the CDROM optical disc with the label appropriate for your machine
architecture, either ULTRIXlUWS V4.3 (RISC) SUPPORTED or ULTRIXlUWS
V4.3 (VAX) SUPPORTED, into the drive. Wait for the drive to be on line and
ready.
2. Type the following command to determine the drive from which to boot:
»> show device

After several seconds, a nine-column table is displayed. You need the following
information from this table:
-

The logical device name, which is shown in column 1.

The physical device name, which is shown in column 8.

3. Type the boot command at the console mode prompt, using the logical device
name determined by the show device output.
For example, an RRD40 device connected to SCSI controller B with SCSI bus ID
number 4 would require a boot command like the following:
»> b dkb400

3-20 Booting the System

3.8.3

Booting from the Network
To boot the system over the network, type the following command at the console
mode prompt:
»> b esaO

Booting the System 3-21

3.9 MicroVAX 3300/3400 or VAXserver 3300/3400 Processor
To prepare the MicroVAX 3300/3400 or VAXserver 3300/3400 hardware:
1. Tum on power to the console terminal and all additional peripheral devices.
2. Set the front panel HALT ENABLEIDISABLE switch to the halt enabled
position.
3. Tum on power to the processor.
4. Remove any TK50 tape cartridges from their associated drives.
The console subsystem now prints an initial display similar to the following on the
console terminal:
KA640-A

T3.0-10, VMB 2.2

Performing normal system tests.
41. .40 .. 39 .. 38 .. 37 .. 36 .. 35 .. 34 .. 33 .. 32 .. 31. .30 .. 29 .. 28 .. 27 .. 26 ..
25 .. 24 .. 23 .. 22 .. 21. .20 .. 19 .. 18 .. 17 .. 16 .. 15 .. 14 .. 13 .. 12 .. 11. .10 ..
09 .. 08 .. 07 .. 06 .. 05 .. 04 .. 03 ..

Tests completed.

Then the console mode prompt appears:
»>

You are now ready to type the boot command. The boot command you type depends
on the software distribution kit: TK50 or network. The boot command for each
distribution kit is described in this section.

3.9.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TK50 tape kit for inserting the TK50 tape
into the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are wri~e-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOT/UPGRADE into the tape drive. Ensure the tape is online and ready to
use.
3. Type the following command at the console mode prompt:
»> b muaO

3.9.2

Booting from the Network
To boot the system over the network, type the following command at the console

3-22 Booting the System

mode prompt:
»> b esaO

Booting the System 3-23

3.10 MicroVAX II, MicroVAX 3500/3600/3800/3900, VAXserver
100/3500/3600/3800/3900, VAXstation 3200/3500,
VAXstation II, or VAXstation II/GPX Processor
This section describes how to boot the following processors:
•

Micro VAX II

•

MicroV AX 3500/3600/3800/3900

•

VAXserver 100/35001360013800/3900

•

VAXstation 3200/3500

•

VAXstation II

•

VAXstation IIIGPX

To prepare the hardware:
1. Turn on power to the console terminal and all additional peripheral devices.
2. Make sure the HALT, write-protect, and READY switches (located on the
processor's front panel) are set to their out positions.
3. Set the back panel HALT ENABLEIDISABLE switch to the halt enabled
position.
4. Turn on power to the processor.
5. Remove any TK50 tape cartridges from their associated drives.
The console subsystem now prints an initial display similar to the following on the
console terminal:
KA630-A.Vl.3
Performing normal system tests.
7 .. 6 .. 5 .. 4 .. 3 ..
Tests completed.

Then the console mode prompt appears:
»>

3.10.1

2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (V AX)
BOOTIUPGRADE into the tape drive. Ensure the tape is online and ready to
use.

3-24 Booting the System

3. Type the following command at the console mode prompt:
»> b muaO

3.10.2

Booting from the Network
To boot the system over the network, type the following at the console mode prompt:
»> b xqaO

Booting the System 3-25

3.11

V AXstation 3520 or VAXstation 3540 Processor
The following instructions assume you have no bootable software on any device in
your system. To prepare the VAXstation 3520 or V AXstation 3540 hardware:
1. Set the monitor on/off switch to 1 (on).
2. Set the system unit on/off switch to 1 (on).
3. Tum on power to the CDROM box (if present).
4. Tum on power to peripheral devices, such as printers and modems.
5. Remove any TK50 tape cartridges and CDROM optical discs from their
associated drives.
After about 20 seconds, the monitor displays a power-up test sequence similar to
this:
KA60 Vl.O
F .. E .. D .. c .. B .. A .. 9 .. 8 .. 7 .. 6 .. 5 .. 4 .. 3 .. 2 .. 1. .0

Tests complete.

The first line is hardware revision information.
The second line is a countdown of the system self-test diagnostics. The
countdown may be followed by some status or error messages. The owner's
manual explains these status and error messages and also how you can tell
whether the self-test passed.
6. Press the halt button on the front of the system unit after the system finishes the
self-test count down. The console mode prompt appears:
CPUlc»>

3.11.1

Booting from the TK50 Tape Cartridge Kit
Follow the instructions included with your TK50 tape kit for inserting the TK50 tape
into the tape drive.
Follow this procedure to boot the system:
1. Make sure that your tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOT/UPGRADE the tape drive. Ensure the tape is online and ready to use.
3. Type the following command at the console mode prompt:
»> b muaO

3-26 Booting the System

3.11.2

Booting from the CDROM Optical Disc Kit
If your CDROM optical disc is not already in its caddy, follow the instructions in the

hardware manual for inserting the optical disc into the caddy.
Follow this procedure to boot the system:
1. Load the CDROM optical disc with the label appropriate for your machine
architecture, either ULTRIXlUWS V4.3 (RISC) SUPPORTED or ULTRIXlUWS
V4.3 (VAX) SUPPORTED, into the drive. Wait for the drive to be on line and
ready.
2. Type the following command to determine the drive from which to boot:
»> show scsi

A seven-column table is displayed. This table contains the commands for
possible devices from which to boot.
3. Look at column 4, labeled DEVNAM, which contains device names. Find the
RRD40 or RRD42 device name in the list.
4. Find the corresponding boot command in column 2, labeled VMB, which contains
the virtual memory boot command for each device.
5. Type the appropriate boot command from the list in column 2, for example:
»> b dka600

3.11.3

Booting from the Network
To boot the system over the network, type the following command at the console
mode prompt:
»> b esaO

Booting the System 3-27

3.12 VAX-11nSO Processor
To prepare the VAX-111750 hardware:
1. Tum on power to the processor.
2. Set the processor power-on action switch to HALT and the rotary key switch to
LOCAL. It makes no difference how the boot device switch is set during the
installation.
3. Make sure power is on for the console terminal and all additional peripheral
devices.
4. Halt the processor so that the console terminal displays the console mode prompt:
»>

Follow this procedure to boot the system:
1. Insert the TU58 tape cassette labeled ULTRIX V4.2 (VAX) TU58 BOOT 111 into
the console TU58 drive on the front of the processor.

2. Type the following command at the console mode prompt:
»> b ddaO

After the boot media has been read, a message similar to the following displays:
Please remove the volume "ULTRIX" from the console drive.
Insert the first standalone system volume and enter "YES" when ready:

3. Remove the TU58 tape cassette labeled ULTRIX V4.2 (VAX) TU58 BOOT Ill.
4. Insert the first standalone system volume, labeled ULTRIX V4.3 (VAX)
STANDALONE ULTRIX TU58 #1. Type YES at the prompt.
More system information appears, followed by a display similar the following:
Resuming load operation on volume "", please stand by . . .

Load the TU58 labeled 'STANDALONE ULTRIX TU58 #2'.
Press the Return key when ready.

5. Remove the TU58 tape cassette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX TU58 #1, replace it with the TU58 tape cassette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX TU58 #2, and press Return.
More system information appears, followed by a display similar the following:

Load the TU58 labeled 'STANDALONE ULTRIX TU58 #3'.
Press they Return key when ready.

6. Remove the TU58 tape cassette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX TU58 #2, replace it with the TU58 tape cassette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX TU58 #3, and press Return.

3-28 Booting the System

More system information appears, followed by a display similar the following:

Load the TU58 labeled 'STANDALONE ULTRIX TU58 #4'.
Press the Return key when ready.

7. Remove the TU58 tape cassette labeled ULTRIX V4.3 (V AX) STANDALONE
ULTRIX TU58 #3, replace it with the TU58 tape cassette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX TU58 #4, and press Return. The installation
software displays the memory and hardware configurations.
8. Remove the TU58 tape cassette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX TU58 #4.
9. Reload the TU58 tape cassette labeled ULTRIX V4.2 (VAX) TU58 BOOT 111.
This media is necessary for booting your system if your configuration requires
access to hardware microcode.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-29

3.13 VAX-11nSO or VAX-11nS5 Processor
To prepare the VAX-111780 or VAX-111785 hardware:
1. Tum on power to the processor.
2. Set the restart switch to OFF and the rotary key switch to LOCAL.
3. Make sure power is on for the console terminal and all additional peripheral
devices.
4. Halt the processor so that the console terminal displays the console mode prompt:
»>

Follow this procedure to boot the system:
1. Remove the RXOI console diskette that is in the drive inside the processor.
2. Insert the RXOI diskette labeled ULTRIX V4.2 RXOI BOOT 111. The diskette
label should point toward the handle of the diskette drive.
3. Type the following at the console mode prompt:
»> b

4. Remove the RXOI diskette labeled ULTRIX V4.2 RXOI BOOT 111.
5. Insert the first standalone system volume, labeled ULTRIX V4.3 (VAX)
STANDALONE ULTRIX RXOI #1. Type YES to the prompt.
More system information appears, followed by a display similar to the following:
Resuming load operation on volume "", please stand by . . .

Load the RXOl labeled 'STANDALONE ULTRIX RXOl #2'.
Press the Return key when ready.

6. Remove the RXOI diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RXOI #1, replace it with the RXOI diskette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX RXOI #2, and press Return.
A display similar to this appears:

Load the RXOl labeled 'STANDALONE ULTRIX RXOl #3'.
Press the Return key when ready.

7. Remove the RXOI diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RXOI #2, replace it with the RXOI diskette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX RXOI #3, and press Return. The installation
software displays the memory and hardware configurations.

3-30 Booting the System

A display similar to this appears:

Load the RXOl labeled 'STANDALONE ULTRIX RXOl #4'.
Press the Return key when ready.

8. Remove the RXOI diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RXOI #3, replace it with the RXOI diskette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX RXOI #4, and press Return.
9. Remove the RXOI diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RXOI #4.
10. Reload the RXOI diskette labeled ULTRIX V4.2 RXOI BOOT 111.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-31

3.14 VAX 6000-nnn Series or VAXserver 6000-nnn Series
Processor
This section describes how to boot the following processors:
•

VAX 6000-210/220/230/240

•

VAX 6000-310/320/330/340/350/360

•

VAX 6000-410142014301440/450/460

•

VAX 6000-510/520/530/540/550/560

Note that VAX server 6000-nnn processors were fonnerly known as VAX server
6210/6220 or VAX server 6310/6320/6330/634016350/6360 processors.
To prepare the hardware:
1. Turn on power to the processor.
2. Turn on power for the console terminal and all additional peripheral devices.
3. Halt the processor so that the console terminal displays the console mode prompt:
»>

The boot command you type depends on whether or not your system has a CIBCAAA or a CIBCA-AB controller. If your system has a CIBCA-AA controller,
continue with Section 3.14.2. If your system has a CIBCA-AB controller, continue
with Section 3.14.3. Otherwise, continue with Section 3.14.1.

3.14.1

~ooting from the TK50 Tape Cartridge Kit

Follow the instructions included with your TK50 tape kit for inserting the tape into
the tape drive. Then, follow this procedure to boot your system.
1. Make sure that your TK50 tape cartridges are write-protected.
2. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOTIUPGRADE into the tape drive. Ensure the tape is online and ready to
use.
3. Type the following ,command at the console mode prompt to begin the
installation:
»> b /r5:10008 csal

Next, the installation software displays some system infonnation, followed by the
memory and hardware configurations.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.14.2

Booting from a System with a CIBCA-AA Controller
Follow the instructions included with your TK50 tape kit for inserting the tape into
the tape drive. Then, follow this procedure to boot a system with a console tape:
1. Make sure that your TK50 tape cartridges are write-protected.
2. Load the console tape supplied with your system into your console drive.

3-32 Booting the System

3. Type the following command at the console mode prompt:
»> b /r5:10008 csal

After the boot media has been read, a message similar to the following is
displayed:
Please remove the volume " CONSOL " from the console drive.
Load the first standalone system volume into the console drive
and enter "YES" when ready:

4. Remove the console tape cartridge supplied with your processor.
5. Load the tape cartridge labeled ULTRIX AND UWS V4.3 (VAX)
BOOTIUPGRADE into the console drive. Ensure the tape is online and ready to
use. Type YES to the prompt.
More system information appears, followed by a display similar to the following:
Resuming load operation on volume "", please stand by . . .

The installation software displays the memory and hardware configurations.
6. Remove the TK50 tape cartridge kit.
7. Reload the console tape cartridge supplied with your processor. This media is
necessary for booting your system.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3.14.3

Booting from a System with a CISCA-AB Controller
Follow the instructions included with your TK50 tape kit for inserting the tape into
the tape drive. Then, follow this procedure to boot a system:
1. Make sure that your TK50 tape cartridges are write-protected.
2. Load the tape cartidge labeled ULTRIX AND UWS V4.3 (VAX)
BOOTIUPGRADE into the console drive. Ensure the tape is online and ready to
use.
3. Type the following command at the console mode prompt:
»> b /r5:10008 csal

You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-33

3.15 VAX 8200/8250 or VAX 8300/8350 Processor
To prepare the VAX 8200/8250 or VAX 8300/8350 hardware:
1. Tum on power to the processor.
2. Set the processor key switch 1 to ENABLE. Set the processor key switch 2 to
HALT.
3. Make sure power is on for the console terminal and all additional peripheral
devices.
4. Halt the processor.
5. Press the front panel Reset button and wait for the console mode prompt:
»>

Follow this procedure to boot the system:
1. Load the RX50 diskette labeled ULTRIX V4.2 (VAX) RX50 BOOT 111 in the
processor's removable drive. Use the left-hand drive if your unit is vertically
positioned; use the uppermost drive if your unit is horizontally positioned. Make
sure the orange arrow on the diskette lines up with the orange bar on the drive;
otherwise, the boot procedure will fail.
2. Type the following at the console mode prompt:
»> b csal

3. Remove the RX50 diskette labeled ULTRIX V4.2 (VAX) RX50 BOOT 111.
4. Insert the first standalone system volume, labeled ULTRIX V4.3 (VAX)
STANDALONE ULTRIX RX50 #1. Type YES to the prompt.
More system information appears, followed by a display similar to the following:
Resuming load operation on volume "", please stand by . . .

Load the RX50 labeled 'STANDALONE ULTRIX RX50 #2'.
Press the Return key when ready.

5. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RX50 #1, replace it with the RX50 diskette labeled ULTRIX V4.3
(VAX) STANDALONE ULTRIX RX50 #2, and press Return.
More system information appears, followed by a display similar to the following:

Load the RX50 labeled 'STANDALONE ULTRIX RX50 #3'.
Press the Return key when ready.

6. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RX50 #2, replace it with the RX50 diskette labeled ULTRIX V4.3

3-34 Booting the System

(VAX) STANDALONE ULTRIX RX50 #3, and press Return. The installation
software displays the memory and hardware configurations.
7. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RX50 #3.
8. Reload the RX50 diskette labeled ULTRIX V4.2 (VAX) RX50 BOOT Ill. This
media is necessary for booting your system if your configuration requires access
to hardware microcode.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-35

3.16 VAX 8500/8530/8550, VAX 8700, or VAX 8800/8810
Processor
To prepare the VAX 8500/8530/8550, VAX 8700, or VAX 8800/8810 hardware:
1. Tum on power to the processor.
2. Tum on power to the console subsystem.
3. Initialize the system with the @sys in i t command procedure.
4. Tum on power to all additional peripheral devices.
5. Halt the processor so that the console terminal displays the console mode prompt:
»>

Follow this procedure to boot the system:
1. Load the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX
RX50 #1 into the console subsystem's diskette drive unit O. Use the left-hand
drive if your unit is vertically positioned; use the uppermost drive if your unit is
horizontally positioned. Make sure the orange arrow on the diskette lines up with
the orange bar on the drive; otherwise, the boot procedure will fail.
2. Type the following command at the console mode prompt:
»> @cnsl.com

The installation software displays some system information, followed by this
message:

Load the RX50 labeled 'STANDALONE ULTRIX RX50 #2'.
Press the Return key when ready.

3. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RX50 #1, replace it with the RX50 diskette labeled ULTRIX V4.3
(V AX) STANDALONE ULTRIX RX50 #2, and press Return. The installation
software displays the memory and hardware configurations.
4. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE
ULTRIX RX50 #2, replace it with the RX50 diskette labeled ULTRIX V4.3
(V AX) STANDALONE ULTRIX RX50 #3, and press Return. The installation
software displays the memory and hardware configurations.
5. Remove the #3 RX50 diskette.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3-36 Booting the System

3.17 VAX 8600/8650 Processor
To prepare the VAX 8600/8650 hardware:
1. Tum on power to the processor.
2. Set the processor power-on action switch to HALT and the rotary key switch to
LOCAL.
3. Turn on power to the console terminal and all additional peripheral devices.
4. Halt the processor so that the console terminal displays the console mode prompt:
»>

Follow this procedure to boot the system:
1. Type the following command at the console mode prompt:
»> @cnsl.com

After the boot media has been read, a message similar to the following is
displayed:
Please remove the volume "VMS Exchange" from the console drive.
Insert the first standalone system volume and enter "YES" when ready:

2. Remove the RL02 console disk currently located in the disk drive inside the
processor.
Mount the RL02 disk labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX
RL02 #1 onto the disk drive located inside the processor. Make sure the drive is
online and ready for operation. Type YES to the prompt.
A display similar to the following is displayed:
Resuming load operation on volume "", please stand by . . .

The installation software displays the memory and hardware configurations.
3. Remove the RL02 disk labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX
RL02 #1.
4. Mount the RL02 console disk that you removed in step 2. Make sure the drive is
online and ready for operation.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-37

3.18 VAX 8820/8830/8840 Processor
Look in the configuration section of your site management guide for the following
numbers for the RA60 installation device:
•

VAX Bus Interconnect (VAXBI) number, which is the VAXBI bus to which the
controller is connected

•

VAXBI node number, which is the node on the VAXBI bus to which the
controller is connected

•

Disk (dn) number, which is the unit number of the RA60 disk to which the
controller is connected

•

For an RA60 disk connected to a Hierarchical Storage Controller (HSC), the HSC
Computer Interconnect (CI) node number

To prepare the VAX 8820/8830/8840 hardware:
1. Tum on power to the processor.
2. Initialize the system with the @sysini t command procedure.
3. Tum on power for the console terminal and all additional peripheral devices.
4. Halt the processor so that the console terminal displays the console mode prompt:
»>

5. Load the media labeled ULTRIX AND UWS V4.3 (VAX) into the software
distribution device.
6. Enter the device information you obtained from the configuration section of your
site management guide.
7. Enter the boot sequence described in the section that applies to your system.

3.18.1

Booting Sequence for a System Disk Connected to a Local
Controller
Enter the numbers and the boot command specified in the following order:
d r1 BI-number BI-node
d r3 disk-number
@bdara

The following example shows the sequence for BI number 2, BI node I, and RA60
disk 0:
»> d r1 21
»> d r3 0
»> @bdara

The system then displays the boot command for you to type.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

3-38 Booting the System

3.18.2

Booting Sequence for a System Disk Connected to an HSC
Enter the numbers and the boot command specified in the following order:
d r1 BI-number BI-node
d r2 HSC-node-number
d r3 disk-number
@bcara

The following example shows the sequence for BI number 3, BI node 4, HSC node
8, and RA60 disk 2:
»> d rl 34
»> d r2 8
»> d r3 2
»> @bcara

The system then displays the boot command for you to type.
You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-39

3.19 VAX 9000 Processor
To prepare the VAX 9000 hardware, follow these steps:
1. Tum on power to the console terminal.
2. Set the Startup switch to Halt.
3. Set the Power switch to the On position.
4. Set the Service Processor Access switch to Local/SPU.
Note that to boot the system, you will be using an editor similar to EDT to edit a file.
Online editing help is available.
Follow the instructions included with your TKSO tape kit for inserting the tape into
the tape drive.
To boot the system, follow these steps:
1. Make sure that your tape cartridge is write-protected.
2. Load the tape cartridge labeled ULTRIX V4.3 (VAX) VAX 9000 INSTL TKSO
into the tape drive located inside the processor. Ensure the tape is online and
ready to use.
3. Type the following command at the console mode prompt to inform the operating
system that the tape labeled ULTRIX is in tape drive mua7:
»> mount mua7: ultrix

4. Next, copy the following command to the userfiles directory. This
command takes approximately 7-10 minutes to complete.
»> copy mua7: []ultrix.ima [userfiles]

S. Type the following command before removing the TKSO tape:
»> dismount mua7:

6. Remove the TKSO tape from the tape drive.
7. Copy the standalone boot command procedure located in the userfiles
directory to the ULTRIX boot command procedure by typing the following
command:
»> copy [userfiles]sabkupboo.cmd [userfiles]ultrixboo.cmd

8. Next, define ul trix. ima as the root image and then identify the disk unit
information for your system. To do this, you need to edit the ul trixboo. cmd
file.
To invoke the editor, type the following command:
»> edit [userfiles]ultrixboo.cmd

The screen displays an end-of-buffer message:
[EOB]

If you have a video display terminal, the edi t command invokes a full-screen
editor similar to EDT. If you have a hardcopy terminal, it invokes a line editor.

3-40 Booting the System

Note

Online help for full-screen or line editing is available at any time
during the editing session. Press the PF2 key or type help at the
asterisk (*) or the command prompt (:).
After the last line in the comment section (noted by exclamation points (!», open
up a line for editing and add the following command:
DEFINE/SYSTEM SYS$ROOTIMAGE [USERFILES]ULTRIX.IMA

Your file should look similar to the following:
!Inputs:
PI - "TRUE" for /START "FALSE" otherwise

All other GRPs are clear
DEFINE/SYS SYS$ROOTIMAGE [USERFILESJULTRIX.IMA

Move the cursor to the last line in the section containing the DEPOSIT
commands. Open up a line for editing and add the following command:
DEPOSIT R5 %X8

This entry tells the system that the DEPOSIT command for register 5 is %X8.
Your file should look similar to the following:
EXAMINE/SYMBOL=START_ADDRESS PC

DEPOSIT RO %X40
DEPOSIT R3 1
DEPOSIT R5 %X8

!Get the start address

Set device type (CONSOLE)
Set the disk unit number
required mode for ULTRIX

To end the editing session, press CtrllZ. The system will display an asterisk (*).
Type ex it. The installation procedure returns you to the system prompt.
9. To initialize the hardware, type the following command:
»> ilk

1O. To boot the ULTRIX software, type the following command. This will take
several minutes to complete.
»> b ultrix

You have completed booting your system. Continue the installation procedure with
Chapter 4.

Booting the System 3-41

Performing the Installation

This chapter describes how to perform the basic and advanced installations. You
must perform an installation in these situations:
•

When you have never installed ULTRIX or ULTRIX W orksystem Software
systems.

•

When you have the ULTRIX or ULTRIX Worksystem Software installed, but the
product version is not Version 4.2 or higher.
Note
If your system is ULTRIX or ULTRIX Worksystem Software Version
4.2 or higher, you can perform an upgrade instead of an installation.
Continue with Chapter 5 to perform an upgrade.

Whether you decide to do a basic or an advanced installation, you need to complete
the tasks described in Section 4.1 through Section 4.5.
Through Section 4.5, the basic and advanced installation follow similar paths by
requiring you to specify a system disk, reboot the system, and specify system
information. However, the information you provide for the system disk in the
advanced installation may differ from that in the basic installation.
After Section 4.5, the two installation procedures diverge. The basic installation uses
the default file system layout and installs the mandatory subsets. The advanced
installation can take one of two paths:
•

You can select the default disk partitions, the default file system layout, and a
choice of optional subsets.

•

You can select customized disk partitions, a customized file system layout, and a
choice of optional subsets.

There are some post-installation procedures that you cannot perform if you choose
the basic installation. For example, printer services are not available with the basic
installation. See Table 4-1 for further information.
If you plan to perform the advanced installation, before proceeding you should
review Chapter 2 to ensure that you have enough disk space and that the disks'
partitions are as you want them. Refer to Table 2-2 and Table 2-6 for this
information. Appendix D contains an example of an advanced installation.

4.1

Choosing the Type of Installation
Throughout the installation procedure, you will be prompted for information about
the installation. Some prompts have a default response which is shown by brackets
surrounding a letter, for example [b]. Press Return to accept the default response or
enter the letter that corresponds to the option you want to choose.

The first step in installing the software is choosing whether to perform a basic or
advanced installation. The system displays a brief message describing the basic
installation and a menu like the following:
Select one of the following options:
1) BASIC Installation
2) ADVANCED Installation
3) System management
Enter your choice:

Type the number corresponding to the type of installation you want to perform. See
Chapter 7 for further information on the system management option. After you make
your selection, the prompt for the next task is displayed.
Note

Advanced installations are required for V AX station 3520 and 3540
systems.

4.2 Selecting the Software Distribution Device
This section applies only if your system uses console boot media. The following
processors use console boot media:

•
•
•
•
•
•
•

VAX-I 1/750

•
•

VAX 87XX

VAX-I 1/780
VAX-I 1/785
VAX 8200/8250
VAX 8300/8350
VAX 86XX
VAX 85XX
VAX 8800 series

If your system does not use console boot media, continue the installation procedure
with Section 4.3.

Because your system uses console boot media, you must select the device on which
you will load the distribution media supplied with your kit. The system displays a
table listing the possible software distribution devices for your system.
The table lists the following information:
Selection

The selection number associated with each possible distribution
device.

Device Name

The Digital name for each device.

ULTRIXName

The ULTRIX identifier for each device.

Device Number

The device number of each device.

Controller Name

The name of the peripheral controller to which the device is
connected.

4-2 Performing the Installation

Controller Number

The controller number associated with each device. You need
the controller number only if the table shows two devices of
the same type with the same device number.

For example, a VAX-111785 processor displays a table similar to the following:
*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***
The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:
SOFTWARE DISTRIBUTION DEVICE TABLE
Selection

1
2

Device
Name

ULTRIX
Name

Device
Number

RA60
TU81

ra2
tmsO

Controller
Name
KDB50
TU81

Controller
Number
4

To select the software distribution device, follow these steps:
1. Type the selection number corresponding to the device you want.
2. Load the BootlUpgrade media into the software distribution device you selected
from the table. Make sure the device is on line.
3. After the message displays the Digital name for the device, the ULTRIX name,
and the device number of your selection, the procedure asks you to confirm your
choice. To confirm your choice, enter y. After you press Return, the table of
system disk drives is displayed.

4.3 Selecting the Disk for the root Partition
The next step in installing the software is specifying your system disk. The system
disk, also referred to as the a or root partition, will contain the root file system and
the swap 1 space.
The procedure displays a table listing the following information:
Selection

The selection number associated with each possible system
disk.

Device Name

The Digital name for each disk.

ULTRIX Name

The ULTRIX identifier for each disk.

Device Number

The device number of each disk.

Controller Name

The controller name associated with each disk. You need the
controller number only if the table shows two disks of the
same type with the same device number.

Controller Number

The unit number for the system disk must be in the range 0 to
254 for r a -type disks and in the range 0 to 31 for other types
of disks. This disk will contain the root file system and the
swap 1 space.

The system displays a table similar to the one shown in the following example of a
DEC station 5000 processor. This table lists the devices available for your processor.
Select the device you want to contain the root file system by typing the selection

Performing the Installation 4-3

number at the prompt and pressing Return.

*** SYSTEM DISK SELECTION ***
The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:
SYSTEM DISK TABLE
Selection

Device
Name

ULTRIX
Name

Device
Number

1
2
3

RZ55
RZ56
RZ56

rzO
rz1
rz13

o
5

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

Enter your choice: 3

After you enter your selection number, a message is displayed indicating the device
name and the device number. You are asked to make sure the disk drive is on line
and write-enabled. Then, you are asked to confirm your choice. If you decide not to
use the device you selected, enter n at the prompt and choose another device from
the table.
You selected RZ56, device number 13. Make sure this disk drive is on line
and write-enabled (if applicable to your disk drive), then confirm
your choice.
Use RZ56, rz13, for your system disk? (yin)

[]: y

If you selected the advanced installation and you have nonstandard disk partitions on
the system disk, a prompt is displayed asking you to select either the default partition
table or the existing partition table. The default partition table refers to the standard
disk partitions for this release. The existing partition table refers to partitions that
have been customized.
Select one of the following partition tables to be displayed for the
system disk rz13 RZ56:
1
2

Default partition table
Existing partition table

Enter your choice: 2

Depending on your choice, the system displays either the default partition table or the
existing partition table. Then, the system asks if these are the disk partitions you
want. Type y at the prompt if you want to choose the partition table displayed.
Type n at the prompt if you decide you want to choose a different table. If you enter
n, the system will redisplay the prompt to select either the default or existing
partition table.

Note
If you select the existing partition table and the existing partition sizes
are below the minimum sizes established for this release, your selection
will be rejected.
After you enter and confirm your choice, the system allocates, makes, and restores
the root file system on partition a of the system disk. A message similar to the
following is displayed:

4-4 Performing the Installation

The installation procedure now allocates the root file system on
partition 'a' of the system disk, rz13 RZ56.
Making the root file system on rz13 RZ56.
The installation procedure is now restoring the root file system to
partition 'a' of the system disk, rz13 RZ56.
1351+0 records in
1351+0 records out

4.4 Rebooting the System
After the root file system is restored to the a partition, the installation procedure
prints messages telling you how to reboot your system. Follow these steps to reboot
the system:
1. If the system has not halted the processor for you, halt the processor, following
the instructions provided by the system.
After you halt the processor, the system displays the console mode prompt. Note
that on VAX workstations the console prompt may be displayed anywhere along
the left side of your screen, instead of at the end of the installation messages.
2. Type the boot command at the console mode prompt, using the boot sequence
provided by the system. For example, the boot command sequence provided by
the installation procedure for the DECsystem 5000 is as follows:
*** BOOTSTRAP COMMAND SEQUENCE ***
Issue the following console commands to set your default bootpath variable
and to boot your system disk:
»
»

setenv boot "2/rz5/vrnunix -a"
boot

For example, at the prompt for the DECsystem 5000, enter:
»

setenv boot 112/rz5/vmunix -all

boot

4.5 Specifying System Information
A series of prompts is displayed asking you to enter system information. Read these
prompts carefully. Each prompt tells you the correct format to use. If you enter an
inappropriate response, you continue to receive the prompt until you enter a valid
response.
The prompts ask you to provide the following information:
•

The system name
After you enter the system name, you are asked to confirm your choice. Network
installations do not ask you for a system name.

•

The date and time

•

Your time zone

•

Whether your area alternates between daylight savings and standard time

Performing the Installation 4-5

•

Your geographic area

•

A superuser password
Choose a superuser password that other people are unlikely to guess and keep it
secure. The password should be up to eight characters in length. A longer
password will be truncated to eight characters. After you enter your superuser
password, you are prompted to reenter it to confirm that it is correct. Note that as
a security measure the password you enter is not displayed on the terminal. After
you set up the superuser password, anyone who logs in with the superuser name
root, must use the password you choose here. Do not use the password given in
the following example:
*** SPECIFY THE SUPERUSER PASSWORD ***

Enter new password: faR!Kle
Verify: faR!Kle

At this point, the basic and advanced installation procedures diverge. If you selected
the basic installation, continue with Section 4.7. If you selected the advanced
installation, continue with Section 4.6.

4.6 Allocating File Systems
If you selected the advanced installation, the procedure continues as follows. The
system disk you selected contains the root file system on partition a.
If you chose to use the default partition table, the system displays a table showing the
default file system layout. The table shows the locations of the following areas on
your system disk:

•

The root file system

•

The / u s r file system

•

The swapl space

•

The crash dump space

The information displayed looks similar to the following:
*** FILE SYSTEM DEFAULT OPTION ***
The following table shows the default file system layout on RZ56, rz13:
partition
a
b
g

bottom
0
32768
163840

top
32767
163839
731505

size
32768
131072
567666

overlap
c
c
c,d,e

default
root
swap, dump
/usr

If you choose the defaults, the var area will be allocated to /usr/var.

A prompt is displayed asking if you want to choose the default file system layout.
Do you want to choose the default file system layout?

(y/n): y

If you want to accept the defaults, enter y. The system will display information

4-6 Performing the Installation

similar to the following.
Making the new file system for /usr on /dev/rrz13g RZ56
*** SUPPORTED SOFTWARE INSTALLATION ***

If you enter y at the prompt, continue with Section 4.7. If you enter n at the prompt,
continue with Section 4.6.1.

4.6.1

Allocating the lusr File System
If you chose not to use the default partition table, the system displays a table similar
to the one shown in the following example of a DEC station 5000. This table lists the
disks connected to your processor. Select the disk on which you want to allocate the
/usr file system by typing the disk's selection number at the prompt. Refer to the
file system worksheet in Table 2-6 for the disk name.
*** /usr FILE SYSTEM ALLOCATION ***
You can allocate the /usr file system to one of the disks listed in the
table below.
See the Guide to Installing ULTRIX for an explanation of
this table:
/usr FILE SYSTEM ALLOCATION TABLE
Selection

1
2

Device
Name

ULTRIX
Name

Device
Number

RZ55
RZ56
RZ56

rzO
rz1
rz13

o
5

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

o
o
1

Enter your choice: 3

You selected RZ56, device number 13. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RZ56, rz13 for /usr file system? (y In)

[]: y

After you enter your confirmation, a message is displayed indicating:
•

The partitions available on the disk you selected

•

The size in KB of each available partition

•

Other partitions over which each available partition extends

The system instructs you to enter the letter of the partition on which you want to
allocate the /usr file system. Refer to the /usr file system worksheet in Table 2-5
that you filled out for the partition.
A default partition is displayed in the square brackets only if the disk is the system

Performing the Installation 4-7

disk.
The disk rz13 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:
partition

size (KB)

d
e
f
g
h

overlap

146265
146265
275137
283833
283834

c,g
c,g,h
c,h
c,d,e
c,e,f

Type the letter of the partition on which you want to allocate the /usr
file system [no default]: 9
Making the new file system for /usr on /dev/rrz13g RZ56

4.6.2

Allocating the swap1 Space
The system displays a table similar to the one shown in the following example. This
table lists the disks connected to your processor. Select the disk on which you want
to allocate the swap 1 space.

*** ALLOCATE THE SWAP1 SPACE ***
You can allocate the swap1 space to one of the disks listed in the
table below.
See the Guide to Installing ULTRIX for an explanation of
this table:
SWAP1 SPACE ALLOCATION TABLE
Selection

Device
Name

ULTRIX
Name

Device
Number

RZ55
RZ56
RZ56

rzO
rz1
rz13

2
3

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

a
a
1

Enter your choice: 3

You selected RZ56, device number 13. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RZ56, rz13 for swap1 space?

(y In)

[]: y

After you enter your confirmation, a message is displayed indicating:
•

The partitions available on the disk you selected

•

The size in KB of each available partition

•

Other partitions over which each available partition extends

Refer to the file system worksheet in Table 2-6 for the disk name and partition.

4-8 Performing the Installation

Note
If you choose a partition that overlaps the a partition, where customized
partition information resides, you will overwrite any customized partition
table that describes the disk you selected and overwrite the superblock.
For this reason the system does not include the a partition in the list of
partitions available for the swap area.
The disk rz13 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:
partition

size (Kbytes)

overlap

b
f
h

65536
275137
283834

c,h
c,e,f

Type the letter of the partition on which you want to allocate the
swap1 space [b]: b

Note
If you want to upgrade the system in future releases, you must allocate
the swap 1 space on partition b of the system disk.

4.6.3

Allocating the swap2 Space
A prompt is displayed asking if you want to allocate a second swap space. If you do
not want to allocate a second swap space, enter il, and continue with Section 4.6.4.
Otherwise, enter y and complete this section.
*** ALLOCATE THE SWAP2 SPACE ***
Do you want to allocate a second swap space? (yin)

[n]: y

The system displays a table similar to the one shown in the following example. This
table lists the disks connected to your processor. Select the disk on which you want
to allocate the swap2 space.
You can allocate the swap2 space to one of the disks listed in the
table below.
See the Guide to Installing ULTRIX for an explanation of
this table:
SWAP2 SPACE ALLOCATION TABLE
Selection

1
2

Device
Name

ULTRIX
Name

Device
Number

RZ55
RZ56
RZ56

rzO
rzl
rz13

1
5

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

o
o
1

Performing the Installation 4-9

Enter your choice: 1

You seiected RZ55, device number O. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RZ55, rzO for swap2 space? (yin)

[]: y

After you enter your confirmation, a message is displayed indicating:
•

The partitions available on the disk you selected

•

The size in KB of each available partition

•

Other partitions over which each available partition extends

You are prompted to enter the letter of the partition on which you want to allocate
the swap2 space. Refer to the file system worksheet in Table 2-6 for the disk name
and partition.
The disk rzO you selected from the previous table has the following
partitions available, on which you can allocate the swap2 space:
partition

size (Kbytes)

b
c
d
e
f
g
h

73728
324520
40960
40960
122880
234408
29608

overlap
c
a,b,d,e,f,g,h
c,g
c,g
c,g
c,d,e,f,h
c,g

Type the letter of the partition on which you want to allocate the
swap2 space [no default]: b

4.6.4

Allocating the Crash Dump Space
The system displays a table similar to the one shown in the following example. This
table lists the disks connected to your processor. Select the disk on which you want
to allocate the crash dump space.

*** ALLOCATE THE CRASH DUMP SPACE ***
You can allocate the crash dump space to one of the disks listed in the
table below.
See the Guide to Installing ULTRIX for an explanation of
this table:
CRASH DUMP SPACE ALLOCATION TABLE
Selection

Device
Name

ULTRIX
Name

Device
Number

RZ55
RZ56
RZ56

rzO
rz1
rz13

1
5

2
3

4-10 Performing the Installation

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

o
o
1

Enter your choice: 3

You selected RZ56, device number 13. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RZ56, rz13 for crash dump space?

(yin)

[]:

After you enter your confinnation, a message is displayed indicating:
•

The partitions available on the disk you selected

•

The size in KB of each available partition

•

Other partitions over which each available partition extends

You are prompted to enter the letter of the partition on which you want to allocate
the crash dump space. You can allocate the crash dump space to the same partition as
either swap 1 or swap2. Refer to the file system worksheet in Table 2-6 for the disk
name.

Note
The crash dump space must be on a disk connected to the same
controller as the system disk.
The disk rz13 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:
partition

size (Kbtyes)

overlap

f
h
b

275137
283834
65536

c,h
c,e,f
c

Type the letter of the partition on which you want to allocate the
crash dump space [b]: b

4.6.5

Allocating the var Area
The system displays a table similar to the one shown in the following example. This
table lists the disks connected to your processor. Select the disk on which you want
to allocate the var area.
*** ALLOCATE THE var FILE SYSTEM ***
You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:
var FILE SYSTEM ALLOCATION TABLE
Selection

Device
Name

ULTRIX
Name

Device
Number

RZ55
RZ56
RZ56

rzO
rz1
rz13

1
5

2
3

Controller
Name
SCSI
SCSI
SCSI

Controller
Number

o
1

Performing the Installation 4-11

Enter your choice: 3

You selected RZ56, device number 13. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RZ56, rz13 for var file system? (yin)

[]: y

After you enter your confirmation, a message is displayed indicating:
•

The partitions available on the disk you selected

•

The size in KB of each available partition

•

Other partitions over which each available partition extends

You are prompted to enter the letter of the partition on which you want to allocate
the var area. You can allocate the var area either to a separate partition as a file
system, or as a directory under the /usr file system. If you want to allocate the
var area to the /usr file system, select the same disk and partition selected in
Section 4.6.1. Refer to the file system worksheet in Table 2-6.
The disk rz13 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:
partition

size (Kbytes)

overlap

f
h

275137
283834
283833

c,h
c,e,f
c,d,e

Type the letter of the partition on which you want to allocate the var
file system [g]: h

Making the new file system for var on Idev/rrz13h RZ56

Continue with Section 4.7.

4.7 Installing ULTRIX Worksystem Software
If you are installing on a machine other than a workstation, a message describing the
licenses required to load ULTRIX Worksystem Software is displayed, followed by a
prompt to choose whether or not to install the ULTRIX Worksystem Software. For
example:
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.
Do you want to install ULTRIX Worksystem Software? yin []:

After you respond to the prompt, continue with Section 4.8.
If you are installing to a workstation, you are asked to select the type of monitor
display being used. Refer to your system's hardware guide for this information.

4-12 Performing the Installation

Type the selection number at the prompt.
Select one of the options below that describes the enter of display
being used:
1) Black and White
2) Color
3) Gray Scale
Enter your choice:

After you enter your choice, continue with Section 4.8.

4.8 Loading the Software Subsets
Next, you can load the software subsets from the distribution media.
If you are installing from a TK50 or MT9 tape, continue with Section 4.8.1.
If you are installing from a CDROM, continue with Section 4.8.2.

If you are installing from the network and choose the basic installation, continue with
Section 4.8.3.
If you are installing from the network and choose the advanced installation, continue
with Section 4.8.4.

4.8.1

Installing from TK50 or MT9 Tape
If you are installing from a TK50 or an MT9 tape, you are now required to change
tape cartridges. The installation script prompts you with the following statement:
*** SUPPORTED SOFTWARE INSTALLATION ***
Remove the tape containing the BOOT/UPGRADE software and replace it with
the tape containing the SUPPORTED software subsets.

Remove the tape marked ULTRIX AND UWS V4.3 BOOTIUPGRADE and replace
it with the tape marked ULTRIX AND UWS V4.3 SUPPORTED Volume 1.
Note
The tape marked ULTRIX AND UWS V4.3 BOOTIUPGRADE contains
only the bootstrap sequence and the update subsets. Other tapes, marked
as SUPPORTED SOFTWARE, contain the supported subsets.
The installation software prompts you to make sure the distribution media containing
the supported software subsets for ULTRIX is mounted and on line. If it is not,
mount the media labeled SUPPORTED and prepare the device for read-only
operations. The installation software displays the following prompt and message:
Please make sure your installation tape is mounted and on-line.
Are you ready (y/n)?

After you enter y, the procedure displays the following message:
positioning Tape

If you are performing a basic installation, continue with Section 4.8.3. If you are
performing an advanced installation, continue with Section 4.8.4.

Performing the Installation 4-13

4.8.2

Installing from a COROM
If you are installing from a CDROM, the device is already prepared and loaded. If
you chose a basic installation continue with Section 4.8.3. If you chose an advanced
installation continue with Section 4.8.4.

4.8.3

Loading Software Subsets for the Basic Installation
When you choose the basic installation, the system loads the software subsets and
displays copying, working, and verifying messages. For example:
Base System (UDTBASE420)
Copying from /dev/nrmtOh (tape)
Working .... Thu May 09 17:38:02 EDT 1991

Verifying
Working .... Thu May 09 17:42:22 EDT 1991

If you are doing a tape installation, some of the subsets are on a second (or more,
with MT9 tapes) tape volume. When the procedure needs these subsets, the system
displays the following message:
Volume change.
Rewinding tape ...
17:01:00 GMT 1991

Working ... Thu Jul 25

When the tape has finished rewinding, you see the following:
Please remove tape volume 1 and replace it with volume 2

Remove the tape volume and replace it with the next tape volume. Continue this
procedure each time a tape is rewound until all the tapes have been read.
Next, the system asks if the tape is online and ready. If you enter y the installation
procedure continues installing the subsets. When the system finishes installing the
software subsets, it displays a message telling you that the software subsets have
been installed.
Continue with Section 4.9.

4.8.4

Loading Software Subsets for the Advanced Installation
When you choose the advanced installation, the system displays a menu of required
software subsets.
***

Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:

The system then displays a list of the optional subsets and asks you to enter the
numbers corresponding to the optional subsets you want to install. Separate multiple

4-14 Performing the Installation

selections with spaces.
The subsets listed below are optional:

Enter your choice(s): 1 2 3 4 5

The system pauses briefly while it determines that the selected subsets will fit on the
disk.
Next, the system displays a list of the subsets you chose to install and asks you to
verify your choice.
You are installing the following subsets:

Is this correct? (yin): y

If you want to change your choice of subsets, enter n at the prompt; the system will
again prompt you to select the optional subsets.
The system loads the software subsets and displays copying, working, and verifying
messages. For example:
Base System (UDTBASE420)
Copying from IdevlnrmtOh (tape)
Working .... Thu May 09 17:38:02 EDT 1991

Verifying
Working .... Thu May 09 17:42:22 EDT 1991

If you are installing from tape, some of the optional subsets are on a second (or
more, with MT9 tapes) tape volume. If you selected any of these optional subsets, the
system displays the following message:
Volume change. Rewinding tape ...
17:01:00 GMT 1991

Working ... Thu Jul 25

When the tape is rewound, the system displays the following message:
please remove tape volume 1 and replace it with volume 2

Remove the tape volume and replace it with the next tape volume. Continue this
procedure each time a tape is rewound until all the tapes have been read.
Next, the system asks if the tape is on line and ready. If you enter y, the installation
procedure continues installing the subsets and displays a message telling you when
the subsets have been installed.
Continue with Section 4.9

Performing the Installation 4-15

Note

For VAXstation 3520 and 3540 systems, you must choose the VS35XX
XIIIDECwindows Fonts optional subset.
If you are installing your software over the network and the upgrade subsets

are available for this release on your server, these will appear in the subset
selection menu. Be sure to select the corresponding upgrade subset for each
subset you select. For example, if you want to install the Software
Development Utilities subset and an upgrade exists for it, enter the selection
number for the option and the selection number for the Software Development
Utilities UPGRADE.

4.9 Loading the Software Subset Upgrades
This release of ULTRIX and UWS contains software subset upgrades. How you
install these subsets depends on your distribution media.

4.9.1

Loading Upgrades from TK50 or MT9 Tape
If you are installing from a TK50 tape, the system asks you to remove the tape

labeled ULTRIX AND UWS V4.3 SUPPORTED and replace it with the tape labeled
ULTRIX AND UWS V4.3 BOOTIUPGRADE.
The installation software has successfully installed the software
subsets. You can now remove the tape containing the software subsets
from the device.
Please mount the tape containing the BOOT/UPGRADE subsets.

Note

The tape labeled ULTRIX AND UWS V4.3 BOOTIUPGRADE is the
same tape that you used to boot your system. It contains both the
bootstrap sequence and the upgrade subsets.
Next, the system asks you to make sure your installation tape is mounted and on line
and asks if you are ready.
Please make sure your installation tape is mounted and on-line.
Are you ready (y/n)? y

After you enter y, the system displays the following message:
Positioning Tape

If you chose the basic installation, only the standard upgrades are installed.
If you chose the advanced installation, the system displays a menu of all upgrade

subsets. You are prompted to select the subsets you want to install. Select each
subset and separate multiple selections with spaces.

4-16 Performing the Installation

If you select the following option, only the subsets listed as mandatory are installed:
None of the Above

If you enter y at the prompt asking you to confirm your selection, the system loads
the subsets. If you enter n, the system redisplays the menu and asks you to enter and

confirm your choice of subsets. After you confirm your choice, the system installs
the subsets.
When the subset installation is complete, the system displays a message telling you
that the software subsets have been installed. If you chose the advanced installation,
continue with Section 4.10. If you chose the basic installation, continue with Section
4.11.
Note
If for some reason the system is unable to install the upgrade subsets, the

following error message is displayed:
The installation procedure was unable to install the Upgrade
subsets.

The system then attempts to install the upgrade subsets a second time.
*** Attempting again to install the Upgrade subsets ***
If the system is still unable to install the upgrade subsets, the following

error message is displayed:
The installation procedure failed to install the Upgrade
subsets. This causes the installation procedure to stop.
Contact your DIGITAL representative.

4.9.2

Loading Upgrades from COROM
If you are installing from CDROM disk and there are upgrade subsets on the media

that must be installed, the system displays the following message:
Installing Upgrade Subsets

If you chose the basic installation, only the standard upgrade subsets are installed.
If you chose the advanced installation, the system displays a menu of all upgrade

subsets. You are prompted to select the subsets you want to install. Select each
subset and separate mUltiple selections with spaces.
If you select the following option, only the subsets listed as mandatory are installed:
None of the Above

If you enter y at the prompt asking you to confirm your selection, the system loads

the subsets. If you enter n at the prompt, the system redisplays the menu and asks
you to enter and confirm your choice of subsets. Once you have confirmed your
choice, the system installs the subsets.

Performing the Installation 4-17

When the subset installation is complete, the system displays a message telling you
that the software subsets have been installed. If you chose the advanced installation,
continue with Section 4.10. If you chose the basic installation, continue with Section
4.11.

Note
If for some reason the system is unable to install the upgrade subsets,
you will receive the following error message:
The installation procedure was unable to install the Upgrade subsets

The system attempts to install the upgrade subsets a second time.
*** Attempting again to install the Upgrade subsets ***

If the system is still unable to install the upgrade subsets, the following
error message is displayed:
The installation procedure failed to install the Upgrade
subsets. This causes the installation procedure to stop.
Contact your DIGITAL representative.

4.10 Specifying Kernel Options for the Configuration File
This section applies only if you chose the advanced installation.
After you install the upgrade, the system displays a table listing the kernel options for
the configuration file and asks you to enter the selection number for each kernel
option you want. Separate multiple selection numbers with spaces.
After you enter your selection, the system displays a list of the kernel options you
selected and asks you to confirm your choice.
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection
1
2
3
4
5
6
7
8
9
10

4-18 Performing the Installation

Kernel Option
Local Area Transport (LAT)
Bisynchronous Communication protocol (VAX only)
Computer Interconnect (CI) network
Diagnostic/Utilities Protocol (DUP)
IS09660 File System Support (CDFS)
Ethernet Packet Filter
Enhanced Security Features
DECnet
All of the above
None of the above

Enter the selection number for each kernel option you want.
For example, 1 3 : 1 3 5 7 8
You specified the following kernel options:
Local Area Transport (LAT)
Computer Interconnect (CI) network
IS09660 File System Support (CDFS)
Enhanced Security Features
DECnet

If you do not want the kernel options you selected, enter n at the prompt. The

system redisplays the list of kernel options. Once you are satisfied with your choice,
enter y at the prompt.
Is this correct? (yin)

[n]: y

What is displayed next depends on whether you have hardware installed in the
floating address space. If the system does not find devices in the floating address
space, it issues a message like the following:
* * * SYSTEM CONFIGURATION PROCEDURE * * *
Configuration file complete.

If the system finds devices in the floating address space, it issues a message with a

list of devices similar to the following:
* * * SYSTEM CONFIGURATION PROCEDURE * * *
The system found these devices in the floating
address space:
uda2
dzO
dz1

on ubaO at 160354
on ubaO at 160100
on ubaO at 160110

Configuration file complete.

The system displays a prompt asking if you want to edit the configuration file. Enter
y at the prompt if you need to modify the configuration file. You are expected to

understand the format of the configuration file and how to use the ed editor. (For
more information on editing your system's configuration file, see the Guide to
Configuration File Maintenance.)
Do you want to edit the configuration file?

(yin)

[n]:

You will need to edit the configuration file in the following situations:
•

Your system's configuration does not conform to CSR address assignment rules.
When you install ULTRIX software, the UNIBUS and Q-bus devices that reside
in the floating address space are automatically sized. Therefore, the placement of
devices in this space is critical to the success of your installation.
If your configuration does not conform to CSR address assignment rules, you

must perform an advanced installation because it allows you to edit the system
configuration file built by the system. If you have questions about the accuracy
of your floating address space configuration, contact your Digital Field Service
representative.
•

You have disk controllers in the floating address space.
If your system contains any disk controllers with addresses assigned in the

floating address space (address space beginning with 016), the installation
assumes that the controller has no devices attached to it because the installation
Performing the Installation 4-19

software cannot correctly find the number of drives attached to a disk controller
in floating address space.
To include any drives attached to a disk controller in the floating address space,
you need to edit the configuration file and manually add these drives to the file.
The following example represents the relevant portion of a configuration file
before and after it was edited during the installation. The system in this example
has three KFQSA controllers: uqO, uq 17, and uq 18, of which uq 17 and uq 18 are
in the floating address space, and each controller has one drive attached to it, unit
numbers 0, 1, and 3, respectively. The software places the following information
in the configuration file:
controller
controller
disk
controller
controller
controller
controller

udaO
uqO
raO
udal
uq17
uda2
uq18

at
at
at
at
at
at
at

ubaO
udaO
uqO
ubaO
udal
ubaO
uda2

csr 0172150
drive 0

vector uqintr

csr 0160334

vector uqintr

csr 0160340

vector uqintr

The configuration file does not include drives 1 and 3. To include these drives,
edit the configuration file as follows:
controller
controller
disk
controller
controller
disk
controller
controller
disk

•

udaO
uqO
raO
udal
uq17
ra1
uda2
uq18
ra2

at
at
at
at
at
at
at
at
at

ubaO
udaO
uqO
ubaO
udal
uq17
ubaO
uda2
uq18

csr 0172150
drive 0

vector uqintr

csr 0160334
drive 1

vector uqintr

csr 0160340
drive 3

vector uqintr

You have both a KDA50 and an RQDX controller on the Q-bus.
If your system has both a KDA50 and an RQDX controller on a Q-bus, the

installation procedure assumes that the drive numbers on the second controller are
0, 1,2, and 3. This may not be true for your system. You need to edit the
configuration file to assign the correct drive numbers to the second controller.
Note

Your system's configuration file may contain lines representing
unsupported devices that are commented out with a number sign (#) as
the first character of the line. Do not remove the number signs at this
time because the modules required for these devices are on the
unsupported kit, which you have not yet installed.
Once the unsupported kit is installed, remove the number signs and use the
resulting configuration file to build a kernel containing the unsupported
modules.
The time required for system configuration varies according to processor.

4.11

Console Boot Defaults and Console Media
Section 4.11.1 and Section 4.11.2 contain processor-specific information for updating
console boot defaults and console media. If these sections do not apply to your
processor, continue with Section 4.12.

4-20 Performing the Installation

4.11.1

Updating the Console Boot Default
If you have one of the following processors, the next step in the installation
procedure is to update the console boot defaults:
•

MicroVAX 3100

•

Micro VAX 3500

•

MicroVAX 3300/3400

•

VAXserver 3300/3400

•

VAX 6000-nnn series or VAXserver 6000-nnn series

Once the system halts the processor, follow the instructions displayed on the screen.
Once you have completed these instructions, you can enter the b command whenever
you need to boot your system. See the Guide to System Shutdown and Startup for
more information. Continue the installation procedure with Section 4.12.

4.11.2

Updating the Console Media
If you have one of the following processors with the system disk connected to a
Hierarchical Storage Controller (HSC), the next step in installation procedure is to
update the console media:
•

VAX-l 11750

•

VAX-l 1/780

•

VAX-l 1/785

•

VAX 8600/8650

•

VAX 8200/8250

•

VAX 8300/8350

The following system prompt is displayed:
*** CONSOLE MEDIA UPDATE ***

You need a blank tape, disk, or diskette, depending on the type of console media.
The procedure instructs you to do the following:
1. Ensure the console media is in the drive.
2. Press Return to extract the files.
3. Remove· the console media from the drive.
4. Insert a blank piece of console media, first making sure that is write-enabled. For
a TU58 tape cassette, the RECORD tab should be in the leftmost position. For an
RX50 diskette, there should be no write-protect tab on the edge of the diskette.
5. Press Return. Messages similar to the following are displayed:
Building console for ULTRIX.
This takes several minutes

Directory listing of the new console follows.

Performing the Installation 4-21

6. What you do next depends on which processor you have.
-

For a VAX-111750, remove the TU58 tape cassette from the drive and writelock the cassette. Then, reinsert the TU58 cassette into the drive. Follow the
instructions that are displayed, telling you to set the front switch labeled
BOOT DEVICE to the position that boots the cassette.
If your system includes a Computer Interconnect (CI), the distributed console
tape labeled ULTRIX V4.2 BOOT 111, an equivalent tape, or a customized
tape built for a CIIHSC system disk should remain in its drive at all times.
This is necessary to load required CI microcode.

For a VAX-111780 or VAX-111785, leave the RX01 console diskette in the
drive. The files on this diskette let you automatically boot the system, using
the default boot commands.

For a V AX 8200/8250/8300/8350, if your system includes a Computer
Interconnect (CI), the distributed console diskette labeled ULTRIX V4.2
BOOT Ill, an equivalent diskette, or a customized diskette built for a CIIHSC
system disk should remain in its drive at all times. This is necessary to load
required CI microcode.
You must also update the Electrically Erasable Programmable Read-Only
Memory (EEPROM) to specify the default boot device. Refer to the hardware
guide for information.
You should also run the VAX diagnostic program EBUCA.

Continue the installation procedure with Section 4.12.

4.12 Completing the Installation and Rebooting the System
Depending on your processor type and system disk, the software either reboots the
system automatically or displays instructions on how to reboot your system.
Note

You can cause MicroVAX 2000 and VAXstation 2000 processors to boot
automatically from a disk other than device 0 by issuing the TEST 51
command at the console prompt. Refer to the hardware documentation
that comes with these processors for more information.
The system displays messages similar to the following:
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***
The following files were created during the installation procedure:
/vmunix
/genvmunix
/usr/adm/install.log
/usr/adm/install.FS.log
/usr/adm/install.DEV.log

customized kernel
generic kernel
installation log file
file systems log file
special device log file

If you are installing to a system without a graphics console, a login prompt is
displayed. The login prompt indicates that your installation was successful. For

4-22 Performing the Installation

example:

Ultrixboot - V4.3

Sat Jul 04

06:15:25 EDT 1992

ULTRIX V4.3 System #1: Sat Jul 04 06:18:28 EDT 1992

ULTRIX V4.3
login:

(mysystem)

If you are installing to a workstation, a Start Session dialog box is displayed

indicating that your ULTRIX W orksystem Software session manager is running. The
box contains a login prompt and a password prompt. You can now log in to the
superuser account by typing root at the login prompt and the superuser password
specified earlier in the installation at the password prompt.
See the DECwindows User's Guide for information about how to use ULTRIX
Worksystem Software, including how to log in and use the Session Manager.

4.13 Post-Installation Procedures
A message referring to the locations of /vmunix, / genvmunix, and the log files is
included in the message-of-the-day file, / etc /motd, and will appear each time you
log in to your system. If you want, you can delete these references from your
/etc/motd file. See the Guide to System and Network Setup for information about
the / etc /motd file.
Print out the log files generated in /usr / adm during your installation. You may
need information from these files for system maintenance. Each system has a twouser license as the default. If you want to increase your system's simultaneous login
capacity to more than two users, you must register your Product Authorization Keys
(PAKs). See the Guide to Software Licensing for information about registering
PAKs.
The following table lists some of the tasks you may want to perform, with the name
of the utility used to perform each task. See the Guide to System and Network Setup
for more information about the tasks you will need to complete after the installation
to establish your system's environment. See the Security Guide for Administrators for
instructions on how to set up your system for enhanced security.

Note
The installation procedure does not provide an area for users' files. You
must do this manually after the installation of the system is complete.
See the Guide to System and Network Setup for more information.

Table 4-1: Post-Installation Tasks
Task

Utility

Using the License Management Facility

lrnf(8)

Setting up the License Management Facility

lrnfsetup(8)

Performing the Installation 4-23

Table 4-1:

(continued)

Task

Utility

Adding users and setting up a users' file area

adduser(8)

Adding devices

MAKEDEV(8)

Setting up printers*

Iprsetup(8)

Setting up a local area network

netsetup(8)

Setting up a Network File System

nfssetup(8)

Setting up uucp*

uucpsetup(8)

Setting up the Yellow Pages service

ypsetup(8)

Setting up the BINDIHESIOD service

bindsetup(8)

Setting up the enhanced security features*

secsetup(8)

Setting up the Simple Network Management Protocol*

snmpsetup(8n)

Setting up the Services Order Configuration file

svcsetup(8)

Setting up for remote installation services*

ris(8)

Setting up for diskless management services*

dms(8)

The asterisk (*) denotes the tasks that can be performed only if you chose the
advanced installation. For example, if you chose the basic installation you will not
be able to set up your printer unless you install the optional subsets.
Use the set 1 d utility to load the unsupported software subsets and to add and delete
software subsets. Proper use of set ld will help you manage disk space. For further
information about the setld(8) utility see the ULTRIX Reference Pages.

4-24 Performing the Installation

Performing an Upgrade

You can upgrade an existing ULTRIX and ULTRIX Worksystem Software Version
4.2 or higher system to an ULTRIX and ULTRIX Worksystem Software Version 4.3
system by following the instructions in this chapter. When you upgrade an existing
system, you do not have to perform a complete installation.
Note
You cannot use this upgrade procedure on any system running ULTRIX
or ULTRIX W orksystem Software versions earlier than Version 4.2. For
these earlier versions of the product, you must perform a complete
installation, either a basic or advanced installation. Complete
installations are described in Chapter 4.
The upgrade procedure has three main functions:
1. The procedure selects, copies, and verifies new product software subsets from a
distribution media to your system.
2. The procedure selects, copies, and verifies update subsets to the new product
subsets from a distribution media to your system.
3. The procedure rebuilds the kernel on your system with the upgraded software to
produce a new version of the system.
You use the ULTRIX and UWS Supported and Boot/Upgrade distribution media to
upgrade the system.
There are three possible upgrade paths:
•

If you are upgrading a local system from TK50 or MT9 tapes, from CDROM, or
from the network as a client of a Remote Installation Services (RIS) server, go to
Section 5.1.

•

If you are upgrading a new or existing RIS area on a server, go to Section 5.2.

•

If you are upgrading a new or existing Diskless Management System (DMS) area
on a server, go to Section 5.3.

Note
When you use the upgrade procedure, you must rebuild the kernel for
your system. You must also edit your system configuration file when
you have made customizations to it. Please preview the upgrade
instructions in this chapter before you begin an upgrade.
The script(l) command is not available during the upgrade process. If you want a
script of the upgrade to use as a log, copy the /usr /ucb/ script utility to the
/ trnp directory. Then, before starting the upgrade procedure, run the script
command from / trnp. For example, to run the script on the upgrade into a file you

name upgrade. v43 . log, enter the following command:
# /tmp/seript upgrade.v43.1og

5.1

Upgrading A Local System
Depending on the load device of your processor, use one of the following distribution
devices to load the software:
•

TK50 cartridge tape

•

9-track magnetic tape

•

CDROM

•

Network (from a RIS server)

The upgrade procedure makes use of the setld utility and is essentially the same
for all distribution device types.
If you must abort the upgrade for any reason, press Ctrl/c to abort processing and
prevent changes. Then, restart the upgrade from the beginning.

5.1.1

Starting the Upgrade
To start the upgrade, follow these steps:
1. Log in to your system as root.

2. Bring your system down to single-user mode. Your system must be in singleuser mode to perform the upgrade procedure.
The following command brings the system down to single-user mode after a
delay of five minutes:
# fete/shutdown +5 "Upgrading to ULTRIX V4.3"

For more information on shutting down your system, see the Guide to System
Shutdown and Startup and the shutdown(8) reference page.
3. Unmount all file systems and remount all ULTRIX file systems by entering the
following commands:
# /ete/umount -a -f
# fete/mount -a -t ufs

4. Run the / etc/update program to start the daemon that will keep your file
system consistent. Enter the following command:
# fete/update

Refer to upda t e(8) for more information.
Continue with the section that describes the upgrade for the distribution media you
are using:
•

Section 5.1.2, for upgrading from a TK50 or MT9

•

Section 5.1.3, for upgrading from a CDROM

•

Section 5.1.4, for upgrading from the network

5-2 Performing an Upgrade

5.1.2

Upgrading from a TK50 or MT9
If you are upgrading from tape, make sure that the tape is write-protected. For both
TK50 and MT9 tapes, follow these steps:

1. Load the first volume of the media labeled Supported onto your system's
software distribution device.
2. Enter the following command; replace N with the logical unit number of the
device you are using:
# /ete/set1d -1 /dev/nr-mtNh

3. The system issues the following prompt to be sure that your distribution device is
on line:
Please make sure your installation tape is mounted and on-line.
Are you ready (yin) ?

When you have determined that the tape is mounted and on line, answer y to the
prompt.
Go to Section 5.1.5.

5.1.3

Upgrading from a COROM
If you are upgrading from a CDROM, follow these steps:

1. Load the CDROM onto your system's distribution device.
2. Enter the following command: replace N with the logical unit number of the
device you are using:
# fete/mount -r /dev/rzNe /ront

3. If your system is a RISC machine, enter the following command:
# /ete/set1d -1 front/RIse/BASE

If your system is a VAX machine, enter the following command:
# /ete/set1d -1 front/VAX/BASE

Go to Section 5.1.5.

5.1.4

Upgrading from the Network
If your system is a registered client and you are upgrading from the network, enter
the following command: replace server: with the name of your RIS server, followed
by a colon:
# /ete/set1d

-l~~e~

Refer to Section 5.2 for information about setting up a RIS server.
Continue with Section 5.1.5.

5.1.5

Loading the Software Subsets
If you are upgrading from tape, the procedure displays a Posi tioning Tape
message and begins to extract the subsets from the distribution media. If you are
upgrading from CDROM or the network, the procedure does not display a message

Performing an Upgrade 5-3

before it begins to extract the subsets from the server over the network.
The procedure determines which subsets are mandatory for your system and lists
them as mandatory subsets. The procedure then lists those subsets that are optional
for your system. If there are no optional subsets listed, the procedure asks you
whether you wish to continue.
Follow these steps to load the supported subsets from the distribution media:
1. If there are no optional subsets listed, the procedure asks you whether you wish to
continue. Enter y at the prompt and skip to Step 3, below. The procedure loads
the mandatory subsets specific to your system by copying and verifying each
subset.
2. If there are optional subsets listed, the procedure asks you to select from three
options: All of the Above, None of the Above, and Exit without installing
subsets. Enter the number that represents the None of the Above option. The
procedure loads the mandatory subsets specific to your system by copying and
verifying each subset.
3. After it loads the subsets, the procedure may display the following message:
Required kernel is not available.

When this message appears, you will eventually follow the instructions in Section
5.1.8 to complete the upgrade by rebuilding your system's kernel when there is
not a kernel available.
Otherwise, you will eventually follow the instructions in Section 5.1.7 to
complete the upgrade by rebuilding your system's kernel using an available
kernel.
Next, however, you must apply updates to any subsets just loaded.
Continue with Section 5.1.6.
Note
If at a later time you decide to install any of the optional subsets, be sure
to install the corresponding update subsets, if they exist, for the subsets
you install. For example, if you later install subset UDTACCT430, be
sure to also install the update subset UDTACCT431.

5.1.6

Loading the Software Subset Updates
Next, you must load the software subsets that update the subsets just loaded.
How you load the software subset updates depends on whether your distribution
media is tape, CDROM, or the network.

5.1.6.1

Updating from a TK50 or MT9
If your distribution media is tape, follow these instructions to load the software
subset updates.

1. Load the first volume of the media labeled ULTRIX and UWS
BOOTIUPGRADE onto your system's software distribution device.
2. Enter the following command, replacing N with the actual logical unit number of

5-4 Performing an Upgrade

the device you are using:
# /etc/set1d -1 /dev/nr.mtNh

3. The system prompts you to be sure that your distribution device is on line, as
follows:
Please make sure your installation tape is mounted and on-line.
Are you ready (yin) ?

When you have determined that the tape is mounted and on line, enter y to the
prompt.
You are done loading the update subsets when the procedure returns to the superuser
prompt. Then, you can continue with the instructions about rebuilding the kernel.
Go to Section 5.1.7 to complete the upgrade by rebuilding your system's kernel when
the required kernel is available.
Go to Section 5.1.8 to complete the upgrade by rebuilding your system's kernel when
the required kernel is not available.

5.1.6.2

Updating from COROM
If your distribution media is CDROM, follow these instructions to load the software

subset updates.
If your system is a RISC machine, enter the following command:
# /etc/set1d -1 /mnt/RISC/BASE_UPGRADE

If your system is a VAX machine, enter the following command:
# /etc/set1d -1 /mnt/VAX/BASE_UPGRADE

Unmount the disk by entering the following command:
# /etc/umount /mnt

Remove the distribution media. Then, continue with the instructions about rebuilding
the kernel.
Go to Section 5.1.7 to complete the upgrade by rebuilding your system's kernel when
the required kernel is available.
Go to Section 5.1.8 to complete the upgrade by rebuilding your system's kernel when
the required kernel is not available.

5.1.6.3

Updating from the Network
If your distribution media is the network, the updates were automatically loaded. The
procedure is done when it returns the superuser prompt.

Go to Section 5.1.7 to complete the upgrade by rebuilding your system's kernel when
the required kernel is available.
Go to Section 5.1.8 to complete the upgrade by rebuilding your system's kernel when
the required kernel is not available.

Performing an Upgrade 5-5

5.1.7

Rebuilding a Kernel when the Required Kernel Is Available
To rebuild a kernel on a system when the required kernel is available, take the
following steps:
1. Use the doconfig command with the -c option to rebuild your kernel.
Replace HOSTNAME in the following command with the name of your system

typed in all capital letters:
# /ete/doeonfig -e HOSTNAME

The - c option specifies that the new kernel be built using the configuration file
that already exists in the / sys / conf /vax directory for VAX processors or the
/ sys / conf /mips directory for RISe processors.
2. Note that the doconf ig command allows you to edit the configuration file.
The following prompt appears immediately after you invoke the doconfig
command with the - c option:
Do you want to edit the configuration file

(y/n)

[n]?

Only a few configurations require that you edit the configuration file at this point.
Thus, in most cases, you can enter no at this prompt.
The doconf ig program then displays the following message as it begins to
rebuild your kernel:
*** PERFORMING SYSTEM CONFIGURATION ***

When the doconf ig command finishes executing, it reports the location of a
newly built VAX kernel as follows:
The new kernel is /sys/VAx/HOSTNAME/vrnunix

It reports the location of a newly built RISe kernel as follows:
The new kernel is /sys/MIPS/HOSTNAME/vrnunix

When the doconf ig program completes, it returns you to the superuser prompt.
3. Move the new VAX kernel to root by entering the following command:
# mv /sys/VAX/HOSTNAME/vmunix /vmunix

Or, move the new RISe kernel to root by entering the following command:
# mv /sys/MIPS/HOSTNAME/vmunix /vmunix

4. The generic kernel, / genvrnunix was loaded from the software distribution
during the upgrade. Now, copy it to root by entering the following command:
# ep /usr/genvmunix /genvmunix

5. To complete the upgrade and activate the new kernel, reboot the system by
entering the following command:
# fete/reboot

When the reboot command returns you to the superuser prompt, the upgrade is
complete.

5-6 Performing an Upgrade

5.1.8

Rebuilding a Kernel when the Required Kernel Is Not Available
To rebuild a kernel on a system when the required kernel is not available, take the
following steps:
1. Copy genvrnunix to vrnunix by entering the following command:
# ep /usr/genvmunix /vmunix

2. Reboot your system by entering the following command:
# fete/shutdown -r now "reboot with V4.3 genvmunix"

3. When your system comes up to multiuser mode, log in as root and bring your
system to single-user mode by entering the following command:
# fete/shutdown now "switching to single-user"

4. Unmount all file systems and remount all UFS file systems by entering the
following command:
# /ete/umount -a -f

# fete/mount -a -t ufs

5. If you have customized your system's configuration file, enter the following
command to make a copy of your system's configuration file:
# ep /sys/eonf/mips/HOSTNANfE /sys/eonf/mips/HOSTNANfE.V4.2

Replace the HOSTNAME in the example with the name of your system.

Note
Customizations of the configuration file include local changes to its
global, options, and pseudodevice definitions. You can restore the
customizations in two ways:
-

During step 8, as the doconf ig program is running, enter yes when
you are asked if you want to edit the newly created configuration file.
The doconf ig program places you in the ed editor and you can add
the necessary customizations.

During step 8, as the doconfig program is running, enter no when
you are asked if you want to edit the newly created configuration file.
After the doconf ig program finishes, use the text editor of your
choice to enter the necessary customizations in the new configuration
file, and then rebuild your kernel using the doconf ig -c command.
For more information on using the doconf ig command with the -c
option, see the doconfig(8) reference page.

6. Invoke the doconfig command with no options, as follows:
# doeonfig

While the system is running with a generic kernel, the doconfig program
places the proper configuration entries in your system's configuration file and
makes any special device files that may be required, with the exception of local
configuration customizations.
7. The doconfig program is menu-driven and first asks you to supply your
system's name, then tells you that a system with that name exists, and asks you

Performing an Upgrade 5-7

whether you want to replace the existing system.
Enter y to indicate you do want to replace the system. For example:
A system with that name exists. Replace it (y/n)

[n]:

The program next asks you for the date and time and the time zone for your
system.
8. The doconfig program then asks you if you want to edit the configuration file.
Enter no at the prompt, unless you wish at this time to customize the new
configuration file. If you want to customize now, enter y at the prompt and the
doconf ig program will place you into an editing session. After you exit from
the editing session, the doconf ig program resumes.
9. When the doconf ig program finishes, it prints out informational messages like
the following, listing the path to the new kernel and to the log of device special
files that it created in the / dev directory. For example, building on a system
named SAMSA:
*** PERFORMING SYSTEM CONFIGURATION ***

working
working
working

Thu Aug
Thu Aug
Thu Aug

1 09:11:45 EDT 1991
1 09:13:45 EDT 1991
1 09:15:46 EDT 1991

*** DEVICE SPECIAL FILE CREATION ***

working ..... Thu Aug

1 09:16:35 EDT 1991

A log file listing Special Device Files is located in /dev/MAKEDEV.log
The new kernel is /sys/MIPS/SAMSA/vrnunix

10. Move /vrnunix to / genvrnunix by entering the following command:
# mv /vmunix /genvmunix

11. Move the new kernel created by the doconf ig program to the root partition.
For example:
# mv /sys/MIPS/SAMSA/vmunix

/vmunix

Note
If you are running BINDlHesiod, edit the / etc/rc .local file and
add the BIND extension to the hostname entry, because
doconfig overwrites the existing hostname entry with the name
of your system without its BIND extension.
12. You may now enable your windowing system by running the script that updates
the / et c / tty s file. Enter the following command:
# /ete/server_seps

13. Reboot your system to bring in the new kernel by entering the following

5-8 Performing an Upgrade

command:
# shutdown -r now" boot with V4.3"

The upgrade procedure is complete.

5.2 Upgrading a Remote Installation Services Area
The following sections describe the steps you must follow to upgrade a Remote
Installation Services (RIS) area on a server. To create a new RIS area on your RIS
server, refer to the Guide to Sharing Software on a Local Area Network.
You can upgrade an existing RIS area only on Version 4.3 servers.
To upgrade a RIS area, follow these steps:
1. Log in to the server system as root.
2. Run the / etc / r is utility. Select the Delete Software menu item.
3. Select the RIS area to be upgraded from the menu.
4. Select the appropriate client architecture (VAX or RISe) from the menu.
S. If your current system is Version 4.2A, delete the current ULTRIX Supported
Product and ULTRIX BOOTIUPGRADE products from the selected RIS area by
selecting their product numbers from the menu.
If your current system is Version 4.2, delete the current ULTRIX Supported

Product and MANDATORY UPGRADE products from the selected RIS area by
choosing their product numbers from the menu.
6. Install the Version 4.3 product into the RIS area. The instructions for this part of
the upgrade are the same as for installing products into an existing RIS area.
Refer to the Guide to Sharing Software on a Local Area Network for these
instructions.
You are required to repeat this step twice. First, to install the Supported volumes,
then to install the BootlUpgrade volume.
The procedure is complete when the the / etc/ris utility displays the following
message:
Finished Extracting Subsets from Distribution Media

7. Use the RIS Modify option to modify the product for each registered client. Be
sure to choose both the Supported Products and the Boot Upgrade options when
modifing each client.
8. When the RIS main menu reappears, choose the exit option to return to the
superuser prompt.

5.3 Upgrading a Diskless Management System Area
The following section describes how to perform the upgrade on a server's Diskless
Management System (DMS) area. The process consists of installing the product into
the server's DMS area.
Whether you can upgrade a DMS area currently serving clients depends on the
version number of the clients' operating system and the version number of the
server's operating system:
Performing an Upgrade 5-9

•

If your server is running ULTRIX and UWS Version 4.3, you can upgrade

Version 4.2 (VAX and RISC) and Version 4.2A (RISC) registered client areas to
Version 4.3.
•

If your server is running ULTRIX and UWS Version 4.2 (VAX or RISC) or

Version 4.2A (RISC), you can upgrade Version 4.2 (V AX) and Version 4.2A
(RISC) registered client areas to Version 4.3.
•

If your server is running ULTRIX and UWS Version 4.2 (VAX or RISC) or

Version 4.2A (RISC), you cannot upgrade Version 4.2 (RISC) registered client
areas to Version 4.3. Instead, you must first remove any Version 4.2 (RISC)
clients, perform the upgrade procedure, and then reregister the clients.
If your server supports multiple diskless areas, you must repeat the upgrade process

for each area.
Note

Use the correct media to upgrade the product in your diskless areas. The
upgrade will fail unless you use RISC media for an area serving RISC
clients and use VAX media for an area serving VAX clients.
Perform the following steps to upgrade an existing diskless area on a server:
1. Shut down all registered diskless clients.
2. Back up the diskless environments.
3. Load the first volume of the Supported media onto your software distribution
device, if you have not done so already. If you are installing the product from
CDROM, use the mount command as follows; replace N with the logical unit
number of the device you are using:
# /etc/mount -r /dev/rzNc /ront

4. Invoke the dms utility:
# /etc/dms

5. Choose the Install Software option from the Diskless Management Services
menu.
6. The system presents you with two software installation options. Choose the
option Add software to Existing Area from the Install Software menu.
7. The system asks you into which existing diskless environment you want to install
software, and lists your options. Select the appropriate environment.
8. The system prompts you to enter the device special file name or mount point of
the distribution media. Your responses depend on which distribution media you
use, tape or CDROM.
If you are installing from a TK50 tape or MT9 tape, the command is the same for
both VAX and RISC environments. Enter the following command, replacing N

5-10 Performing an Upgrade

with the logical unit number of the device you are using:
/dev/rmtNh

Make sure that the installed nledia is write-protected.
Note

When installing from tape, the procedure determines which tapes
must be loaded and prompts you to mount the appropriate volumes.
For example, you could receive a message like the following:
Please remove tape Vol 4 and replace it with Vol 2

Follow the instructions the procedure supplies.
If you are installing from CDROM to an area serving RISC clients, enter the

following command:
/mnt/RIse/BASE

If you are installing from CDROM to an area serving VAX clients, enter the
following command:
/mnt/VAX/BASE

9. If there are clients already registered, the procedure displays the following
question:
The product software will automatically be propagated to every
registered client.
Is that alright? (yin):

Enter y at the prompt to propagate the product to registered clients. If you enter
n at the prompt, you will have to upgrade clients later.
The system lists mandatory and optional subsets from the Supported media and
installs them.
The system copies and verifies each subset you selected.
10. If your installation media is TK50 or MT9, remove the Supported tape from the
drive and load the Boot/Upgrade tape in the drive.
11. Choose the Install Software option from the Diskless Management Services
menu.
12. The system presents you with two software installation options. Choose the
option, Add software to Existing Area from the Install Software menu.
13. The system asks you into which existing diskless environment you want to install
software, and lists your options. Select the appropriate environment.
14. The system prompts you to enter the device special file name or mount point of
the distribution media. Your responses depend on which distribution media you
use, tape or CDROM.
If you are installing from a TK50 tape or MT9 tape, the command is the same for
both VAX and RISC environments. Enter the following command, replacing N

Performing an Upgrade 5-11

with the actual logical unit number of the device you are using:
/dev/rmtNh

Make sure that the installed media is write-protected.
If you are installing from CDROM to an area serving RISC clients, enter the

following command:
/mnt/RISC/BASE_UPGRADE

If you are installing from CDROM to an area serving V AX clients, enter the

following command:
/mnt/VAX/BASE_UPGRADE

15. If there are clients already registered, the procedure displays the following
question:
The product software will automatically be propagated to every
registered client.
Is that alright? (yin):

If your installation media is TK50 or MT9 tape, remove it from the drive.

Your upgrade is complete. You may now reboot each new client, unless you have
modified the area of previously-registered clients. In that event, you must run the
DMS Rebuild Kernel option for each client. Then you can reboot the clients.

5-12 Performing an Upgrade

Adding and Deleting Software Subsets

The set1d utility is used to install and manage software. You can save disk space
with the set1d command by specifying and loading only the software subsets that
you need. This chapter describes how to use the set1d utility. You must have
superuser privileges to modify the system software using set 1d. The set 1d utility
has several command line syntaxes to list, add, and delete software subsets.
Although the command lines differ, the set1d command lines use certain command
arguments as follows:
•

The di r argument specifies the destination of the subset. Specify this argument
if you are loading the software to a file hierarchy that starts somewhere other than
at root (/).

•

The optional subs e t argument specifies the name of the subset.

•

The 1 oca t i on argument specifies the device special file or mount point
containing the media from which the subset or product is to be transferred.

If you specify a di r argument, it must precede the command function. If you

specify a subset or a location argument, it must follow the command function.
For detailed information on the set 1 d command, its functions, and the command
line syntax, see set1d(8) in the ULTRIX Reference Pages.

6.1

Listing Software Subsets
To display the status of all subsets known to the system, specify the set 1d
command with the -i (inventory) function. The format is as follows:
setld [-0 din -i [subset]

For example, to display a list of subsets, enter the following:
# setld -i

To display the files included in a particular subset, for example, UDTUUCP430,
enter the following:
# setld -i UDTUUCP430

6.2 Adding Subsets
To add a subset to your system, use the set 1d command with the -1 (load)
function, the location argument and the subset argument. The format is as follows:
setld [-0 dir] -I < location> subset [ subset. .. ]

The following examples show how to add subsets to your system from tape and from
a file server.

6.2.1

Adding Subsets from Tape
To add or reinstall a subset on the / mn t directory of your system from a kit residing
at tape drive / dev / rmt lh, enter a command like the following:
# set1d -D /mnt -1

6.2.2

/dev/rmtlh UDTUUCP430

Adding Subsets from a File Server
To add or reinstall subsets from a file server, enter a command like the following,
substituting the name of the file server for the server in the example:
# set1d -1 server:

6.3 Deleting Subsets
To delete a subset from your system, use the set ld command with the -d function
and the subset argument. The syntax is as follows:
setld [-0 dir] -d subset [ subset. .. ]

For example, to delete the UDTUUCP400 subset from your system, enter the
following:
# set1d

-d UDTUUCP400

6-2 Adding and Deleting Software Subsets

Working in the Standalone ULTRIX
Environment

The standalone ULTRIX environment is a memory-resident environment that is used
to initiate ULTRIX installations. The primary purpose of the standalone ULTRIX
environment is to support the initial phases of an installation, which include selecting
the distribution and system devices, as well as restoring the root file system image to
the target system disk. Throughout the installation process, full ULTRIX device
drivers are used.
The standalone ULTRIX environment also supports limited system management
activities. These activities include:
•

Restoring a damaged root file system

•

Checking the consistency of the root file system

•

Restoring the boot block image

•

Performing disk maintenance operations

The standalone ULTRIX environment provides commands that assist in recovering
from root file system corruption and help perform general file system and disk
maintenance tasks. It is a limited environment that does not perform like a full
ULTRIX operating system environment. You should perform system management
activities in the standalone ULTRIX environment only if you have extensive
ULTRIX or UNIX operating system experience.
This chapter explains how to invoke the standalone ULTRIX environment, identifies
some of its commonly used capabilities, and describes how to extend the standalone
ULTRIX environment so that additional commands can be used.

7.1

Invoking the Standalone ULTRIX Environment
The media and the commands that you use to invoke the standalone ULTRIX
environment are dependent on the type of processor that you are using. These media
and commands are identified and described in Chapter 3 of this manual.
As part of the installation, the system displays the following menu of options:
Select one of the following options:
1} BASIC Installation
2) ADVANCED Installation
3) System management
Enter your choice:

Choose the third item, System Management, to invoke the standalone ULTRIX
environment. The system responds by placing the system in single-user mode and by
displaying the superuser ( #) shell prompt.

7.2 Standalone ULTRIX Environment Capabilities
The standalone ULTRIX environment enables you to perform several system
management activities. In some cases, you have to use system primitives instead of
the more advanced system commands. For example, to make a new file system, you
would use the mkfs command instead of the newfs command.
Note
At boot time, the system does not configure controllers assigned floating
CSR addresses. Only peripheral devices connected to controllers that
have been assigned fixed CSR addresses are accessible.
If you want access to special device files, you have to create them using the
MAKEDEV command. You can use the standalone system to perform the following

tasks:
•

Edit a file using the ed editor

•

Repair corrupted file systems with the fsck command

•

Create new file systems with the mk f s command

•

Restore the boot block with the dd command

•

Restore file systems with the restore command

•

Modify partition tables with the cbpt command

•

Mount other disks and file systems with the mount command

The Guide to Backup and Restore gives an example of how to restore the root file
system using the standalone ULTRIX environment after a catastrophic event has
occurred.

7.3 Extending the Standalone ULTRIX Environment
If you find that the commands and utilities provided by the standalone ULTRIX
environment do not completely meet your needs, you can extend the environment to
include access to other commands. To extend the environment, perform the
following steps:

1. Make the device special files for the device that contains the target commands.
To do this, change directories as follows:
# cd Idev

After changing directories, use the following syntax to create the special device
files:
MAKEDEV device

The following example shows the command for making a device special file for
rzOa.
# MAKEDEV rzOa

2. Mount the device. For example, to mount the r z 0 a device on the / mn t file

7-2 Working in the Standalone ULTRIX Environment

system, use the following format:
# fete/mount /dev/rzOa /mnt

This enables you to access any of the commands or files on that device. To see
what commands and files are available, enter the following command:
# Is /mnt

The system responds by displaying the contents of I mn t .
If there are directories that you want to include in your search path, reset and export
the path environment variable. For example, to add Imnt Ibin to your path, enter
the following command:
# PATH

= "$PATH:/mnt/bin"; export PATH

To exit the standalone environment and halt the processor, enter the following
command:
# fete/halt

To exit the standalone environment and return to the menu, press CtrllD.

Working in the Standalone ULTRIX Environment 7-3

Rise Supported Software Subsets

Table A-I briefly describes each supported software subset for RISe processors and
lists the names of any other subsets or kernel configuration file options related to its
operation.

Table A-1: RiSe Supported Subset Descriptions and Dependencies
Subset Name

Contents

UDTACCT430

Accounting Software

Optional

Programs and data files needed to perform
system accounting. This subset contains log
files that grow automatically. It is intended
for users familiar with ULTRIX system
administration.

UDTAFM430

Adobe Font Metric Files

Optional

Font metrics (character bounding box,
width, name, ligature, kerning, and font
properties) for PostScript outline fonts used
by text formatting applications in PostScript
output devices.

Dependencies

UDTBASE430

Base System

Required

Fundamental utilities and data files for the
ULTRIX operating system. Base System
includes the C compiler and linker, the
editors, library and data files needed for
POSIX environment, and all of the
general-purpose programs. This subset
cannot be removed.

UDTBIN430

Kernel Configuration Files
Required to
Utility programs and binary files required to install layered
configure ULTRIX kernels. This subset can prod~cts that
be deleted after installation.
reqmre th~ kernel
to be rebmlt.

Required

UDTCDABASE430

CDA Base System

Optional

Runtime components for CDA.

Required for all
subsets

Required for:
UDWMAIL430

Subset Name

Contents

UDTCDAPGMR430

CDA Software Dev Libraries

Optional

Programming libraries for CDA

Dependencies

UDTCOMM430

Communications Utilities

Optional

Utilities for several types of serial
communications with other systems,
including tip, ftp, and telnet.

UDTDCMT430

Doc. Preparation for Ref. Pages
Required for:
Tools to format manage and display
UDTMAN430
reference pages: The n;o f f formatter and UDTMANPGRM430
required macros.
UDWMAN430
UDWMANPGMR430

Optional

UDTDCMTEXT430

Other Doc. Preparation Software

Optional

Additional nroff macro packages,
bibiography tools, and ro f f tools.

UDTDL430

Diskless Environment Support

Optional

Software for a diskless environment. This
subset is required only for diskless
management services.

UDTEXAMPLES430

Programming Examples

Optional

Programming examples for: dbx, dl i,
ncs, device drivers, and others.

UDTEXER430

System Exerciser Package

Optional

Programs that help in diagnosing problems
with your hardware and peripheral devices.

UDTINET430

TCPIIP Networking Utilities

Required

Programs and data used to implement
Internet networking on your ULTRIX
system.

Requires:
UDTINET430
Required for:
UDTUUCP430

Requires:
UDTDCMT430

Requires:
UDTPGMR430

Required for:
UDTCOMM430
UDTNFS430
UDTUMAIL430
Kernel
configuration:
options INET

A-2 RiSe Supported Software Subsets

Subset Name

Contents

Dependencies

UDTINTLPGMR430

Internationalization Dev. Env.

Optional

Source for internationalization languages.

UDTINTLRT430

Internationalization Runtime Env.

Optional

Internationalization languages for
set locale and internationalization tools.

UDTKERB430

Kerberos Network Authentication

Optional

Programs and data used to implement
Kerberos network authentication on your
ULTRIX system.

UDTMAN430

Ref. Pages for Sys. Admin. & Users

Optional

Online reference pages for Sections 1,4, 5,
6,7, and 8 of the ULTRIX Reference Pages.

UDTMANPGMR430

Reference Pages for Programmers

Optional

Online reference pages for Sections 2 and 3
of the ULTRIX Reference Pages.

UDTMH430

The RAND Mail Handler

Optional

Programs that constitute the RAND
Corporation MH mail reader interface.

UDTMOP430

Maintenance Operations Protocol

Optional

Software necessary to use your system as a
boot server for LAT, DMS, or RIS.

UDTNFS430

Network File System Utilities

Required

Programs and data files you need to share
file systems over the network. This subset
contains the files used to implement the
Yellow Pages facility.

UDTPGMR430

Software Development Utilities

Optional

Libraries and utilities useful for software
development. These include the libraries for
linking programs to be analyzed with the
dbx debugger, the 1 in t program verifier,
and the lex and yacc parser packages.

Requires:
UDTDCMT430

Required for:
UDWMAIL430
Requires:
UDTUMAIL430
Kernel configuration:
options DLI
pseudodevice dli

Requires:
UDTINET430
Kernel configuration:
options NFS
options RPC

Required for:
UDTINTL430
UDTRPCDEV430

Rise Supported Software Subsets A-3

Subset Name

Contents

UDTPREST0430

Prestoserve (Legato)

Optional

Utililties for monitoring and administering
Prestoserve.

UDTPRINT430

Printer Support Environment

Optional

Printer commands such as lpr, lpq, and
lpd, utilities, configuration files, filters,
and PostScript printer support.

UDTRPCDEV430

RPC Development Environment

Optional

Programs and data that implement the
Remote Procedure Call (RPC) development
environment.

UDTRPCRT430

RPC Runtime Environment

Optional

Programs and data that implement the
Remote Procedure Call (RPC) run-time
environment. This subset is optional.

UDTSCCS430

Source Code Control System

Optional

Programs that make up the UNIX Source
Code Control System, which provides a
regulation mechanism for large software
projects.

UDTSEC430

Enhanced Security Features

Optional

Programs and data that provide enhanced
security features.

UDTSMSCAMP430

Sys. Config. Mgmt. Program (SCAMP)

Optional

This is a menu-driven program for basic
system administration.

A-4 Rise Supported Software Subsets

Dependencies

Requires:
UDTPGMR430

Kernel configuration:
options AUDIT
options SYS_TPATH
pseudodevice audit

Subset Name

Contents

Dependencies

UDTUMAIL430

Extended (Berkeley) Mailer

Required

Programs and data that implement the BSD
sendrnail facility.

Required for:
UDTMH430

UDTUUCP430

UNIX-to-UNIX Copy Facility

Optional

Programs and data files needed to let your
system participate in a network of machines
using the UNIX UUCP facility to transmit
files over serial communications lines.

UDWDECW430

Additional DECwindows Applications

Optional

Additional XIIIDECwindows client
applications such as Calendar and
PostScript Previewer.

UDWFONT430

XIIIDECwindows 75dpi Fonts

Required for
Worksystems

Fonts for XIIIDECwindows.

UDWFONT15430

XIIIDECwindows 100dpi Fonts

Required for
DEC system 5000
Model 200 with
2-D and 3-D
graphics

Workstation font files for systems using
either the VR160 IS-inch monitor or higher
resolution graphics.

UDWFONTSTR430

XIIIDECwindows PEX Fonts

Required for
DECsystem 5000
Model 200 with
3-D graphics

XIIIDECwindows fonts for 3-D graphics
cards.

UDWMAIL430

DECwindows Mail Application

Optional

DECwindows mail application for
dxmail.

UDWMAN430

UWS Reference Pages

Optional

Online UWS reference pages for Sections 1,
4, 5, 6, 7, and 8.

Requires:
UDTINET430
Requires:
UDTCOMM430

Requires:
UDTBASE430

Requires:
UDTMH430
UDTCDABASE430

Requires:
UDTDCMT430

Rise Supported Software Subsets A-5

Subset Name

Contents

Dependencies

UDWMANPGMR430

UWS Ref. Pages for Programmers

Optional

Online UWS reference pages for Sections 2
and 3.

Requires:
UDTDCMT430

UDWSER430

Server

Optional

Server for XIIIDECwindows.

UDWSYSMGNT430

System Management Tools

Optional

XIIIDECwindows system management
programs.

UDWTPV024425

The Personal Visualizer

Optional

Wavefront, Inc. The Personal Visulalizer

UDWTPVMAN425

Personal Visualizer Ref. Pages

Optional

Reference pages for The Personal
Visulalizer.

UDWWSTSER430

Server

Optional

Server for XllRR PXG 3D graphics.

UDWXl1430

XIIIDECwindows User Environment

Required for
W orksystems

X Window System client programs.

UDWXDEV430

W orksystem Development Software

Optional

Library and data files needed to produce X
Window System client applications.
Includes example programs demonstrating
how to get started.

UDWXTXSER430

Server

Optional

Server for True Color Graphics.

A-6 RiSe Supported Software Subsets

Requires:
UDTBASE430

VAX Supported Software Subsets

Table B-1 briefly describes each supported software subset for VAX processors and
lists the names of any other subsets or kernel configuration file options related to
each subset.

Table B-1: VAX Supported Software Subset Descriptions and
Dependencies
Subset Name

Contents

ULTACCT430

Accounting Software

Optional

Programs and data files needed to perform
system accounting. This subset contains log
files that grow automatically. It is intended
for users familiar with ULTRIX system
administration.

Dependencies

ULTAFM430

Adobe Font Metric Files

Optional

Font metrics (character bounding box,
width, name, ligature, kerning, and font
properties) for PostScript outline fonts used
by text formatting applications in PostScript
output devices.

ULTBASE430

Base System

Required

ULTBIN430

Required

ULTCDABASE430

CDA Base System

Optional

Runtime components for CDA.

Required for all
subsets

Required for:
UWSMAIL430

Subset Name

Contents

ULTCDAPGMR430

CDA Software Dev Libraries

Optional

Programming libraries for CDA

ULTBSC430

Bisynchronous Communications

Optional

Dependencies

Kernel
configuration:
Programs needed to use the 3780 and 2780
options BSC
emulation features provided with your
pseudodevice
ULTRIX system.
bsc

ULTCOMM430

Communications Utilities

Optional

Utilities for several types of serial
communications with other systems,
including tip, ftp, and telnet.

Requires:
ULTINET430

ULTDCMT430

Doc. Preparation for Ref. Pages

Required for:

Optional

ULTMAN430
Tools to format, manage, and display
ULTMANPGMR430
reference pages. The nro f f formatter and
UWSMAN430
required macros.
UWSMANPGMR430

ULTDCMTEXT430

Doc. Preparation Extensions

Optional

Additional nro f f macro packages,
bibiography tools, and ro f f tools.

ULTDL430

Diskless Support Environment

Optional

Software for a diskless environment. This
subset is required only for diskless
management services.

ULTEXAMPLES430

Programming Examples

Optional

Programming examples for: dbx, dli,
nes, device drivers, and others.

ULTEXER430

System Exerciser Package

Optional

Programs that help in diagnosing problems
with your hardware and peripheral devices.

ULTINET430

TCPIIP Networking Utilities

Required

Programs and data used to implement
Internet networking on your ULTRIX
system.

Required for:
ULTUUCP430

Requires:
ULTDCMT430

Requires:
ULTPGMR430

Required for:
ULTCOMM430
ULTNFS430
ULTUMAIL430
Kernel
configuration:
options INET

8-2 VAX Supported Software Subsets

Subset Name

Contents

Dependencies

ULTINTLPGMR430

Internationalization Dev. Env.

Optional

Source for internationalization languages.

ULTINTLRT430

Internationalization Runtime Env.

Optional

Internationalization languages for
set locale and internationalization tools.

ULTKERB430

Kerberos Network Authentication

Optional

Programs and data used to implement
Kerberos network authentication on your
ULTRIX system.

ULTMAN430

Ref. Pages for Sys. Admin. & Users

Optional

Online reference pages for Sections 1,4, 5, ULTDCMT430
6,7, and 8 of the ULTRIX Reference Pages.

ULTMANPGMR430

Reference Pages for Programmers

Optional

Requires:

Requires:
Online reference pages for Sections 2 and 3 ULTDCMT430
of the ULTRIX Reference Pages.

ULTMH430

The RAND Mail Handler

Optional

Programs that constitute the RAND
Corporation MH mail reader interface.

Required for:
UWSMAIL430
Requires:
ULTUMAIL430

VAX Supported Software Subsets B-3

Subset Name

Contents

Dependencies

ULTMOP430

Maintenance Operations Protocol

Optional

Software necessary to use your system as a
boot server for LAT, DMS, or RIS.

Kernel configuration:
options DLI
pseudodevice dli

ULTNFS430

Network File System Utilities

Required

Programs and data files you need to share
file systems over the network. This subset
contains the files used to implement the
Yellow Pages facility.

ULTPASCAL430

Pascal

Optional

PASCAL language compiler and associated
libraries and tools.

ULTPGMR430

Software Development Utilities

Optional

ULTPREST0430

Prestoserve (Legato)

Optional

Utilities for monitoring and administering
Prestoserve.

ULTPRINT430

Printer Support Environment

Optional

Printer commands such as lpr, lpq, and
lpd, utilities, configuration files, filters,
and PostScript printer support.

ULTRPCDEV430

RPC Development Environment

Optional

Programs and data that implement the
Remote Procedure Call (RPC) development
environment.

ULTRPCRT430

RPC Runtime Environment

Optional

Programs and data that implement the
Remote Procedure Call (RPC) run-time
environment.

8-4 VAX Supported Software Subsets

Requires:
ULTINET430
Kernel configuration:
options NFS
options RPC

Required for:
ULTINTL430
ULTRPCDEV430

Requires:
ULTPGMR430

Subset Name

Contents

Dependencies

ULTSCCS430

Source Code Control System

Optional

Programs that make up the UNIX Source
Code Control System, which provides a
regulation mechanism for large software
projects.

ULTSEC430

Enhanced Security Features

Optional

Programs and data that provide enhanced
security features.

ULTSMSCAMP430

Sys. Config. Mgmt. Program (SCAMP)

Optional

This is a menu-driven program for basic
system administration.

ULTUMAIL430

Extended (Berkeley) Mailer

Required

Programs and data that implement the BSD
sendmail facility.

ULTUUCP430

UNIX-to-UNIX Copy Facility

Optional

Programs and data files needed to let your
system participate in a network of machines
using the UNIX UUCP facility to transmit
files over serial communications lines.

ULTVAXC430

V AX C Development Package

Optional

VAX C language compiler and associated
libraries and tools.

UWSDECW430

Additional DEC windows Applications

Optional

Additional XIIIDECwindows client
applications such as Calendar and the
PostScript Previewer.

UWSFONT430

XIIIDECwindows 75dpi Fonts

Required for
Worksystems

Fonts for XIIIDECwindows.

UWSFONT15430

XIIIDECwindows 100dpi Fonts

Optional

Workstation font files for systems using
either the VR160 15-inch monitor or higher
resolution graphics.

Kernel configuration:
options AUDIT
options SYS_TPATH
pseudodevice audit

Required for:
ULTMH430
Requires:
ULTINET430

Requires:
ULTCOMM430

Requires:
ULTBASE430

VAX Supported Software Subsets 8-5

Subset Name

Contents

Dependencies

UWS3DFONT430

VS35XX XIIIDECwindows Fonts

Required for
VAXstation
3520/3540

XIIIDECwindows fonts for VAXstation
3520/3540 processors.

Requires:
ULTBASE430

UWSMAIL430

DECwindows Mail Application

Optional

DECwindows mail application for
dxmail.

UWSMAN430

UWS Reference Pages

Optional

Online UWS reference pages for Sections 1,
4, 5, 6, 7, and 8.

UWSMANPGMR430

UWS Ref. Pages for Programmers

Optional

Online UWS reference pages for Sections 2
and 3.

UWSSER430

XIIIDECwindows Servers

Required for
Worksystems

XIIIDECwindows server support.

UWSSYSMGNT

System Management Tools

Optional

XIIIDECwindows system management
programs.

UWSXl1430

XIIIDECwindows User Environment

Required for
Worksystems

X Window System client programs.

UWSXDEV430

Worksystem Development Software

Optional

Library and data files needed to produce X
Window System client applications.
Includes example programs demonstrating
how to get started.

8-6 VAX Supported Software Subsets

Requires:
ULTMH430
ULTCDABASE430

Requires:
ULTDCMT430

Requires:
ULTBASE430

Unsupported Software Subsets

Table C-l briefly describes each software subset available on the ULTRIX
unsupported kit. The "UDX" prefix indicates RISe software subsets. The "ULX"
prefix indicates VAX software subsets.
You can use the set 1 d command to install some or all of the unsupported software
subsets included with your ULTRIX system. See setid(8) for more information.
The asterisk (*) denotes user-contributed software.

Table C-1: Unsupported Software Subset Descriptions and
Dependencies
Subset Name

Contents

ULXAPL430*

APL Development Package

Dependencies

APL language interpreter and associated
utilities.
ULXBASE430* ,

Base Extension

UDXBASE430*

Programs and data files that can be useful
in some environments. These include
obsolete boot programs, drivers for
unsupported devices, the traff package
with fonts, and miscellaneous software.

ULXBIB430* ,

Bibliographic Utilities

UDXBIB430*

Programs and data useful in maintaining
bibliographic information.

ULXCOURIER430* ,

Remote Procedure Call Compiler

UDXCOURIER430*

Modules for producing software using the
COURIER remote procedure call protocoL

ULXCPM430*

CP/M 8in Diskette Utility
Utilities for reading and writing 8-inch
diskettes used with the CP/M operating
system.

Requires:
ULTDCMT430
or
UDTDCMT430

Subset Name

Contents

ULXDCMT430,

Document Preparation Software

UDXDCMT430
Optional

Additional documentation preparation
utilities and fonts

ULXDOC430,

Supplementary Documentation

UDXDOC430

Online copies of Supplementary
Documentation.

ULXEDIT430* ,

GNU Emacs

UDXEDIT430*

The public-domain GNU Emacs editor and
edit-macro files.

ULXF77430

Unsupported Fortran Utilities
Utilities for developing programs using the
UNIX f 77 dialect of FORTRAN.

ULXGAMES430* ,

Games and Diversions

UDXGAMES430*

Programs used for entertainment.

ULXHYPER430*

Hyperchannel Utilities
The Hyperchannel driver and associated
daemons and utilities.

ULXICON430*

ICON (Language) Development Package
Translator and linker for the ICON
programming language.

ULXINGRES430

University INGRES QUEL DBMS
(database management system).

ULXINET430

TCP/IP Networking Util Extension

UDXINET430
Optional

Networking utilities:
traceroute, slip.

ULXLEARN430,

Computer-Aided System Tutor

UDXLEARN430

Software for the 1 earn program, which
provides lessons in aspects of the
computing environment. This subset is
useful for persons new to the UNIX
environment.

C-2 Unsupported Software Subsets

Dependencies

Requires:
ULTDCMT430
or
UDTDCMT430

Dependencies

Subset Name

Contents

ULXLISP430

Franz Lisp Development Package
Programs that make up the Franz Lisp
program development environment,
including interpreter, libraries, and
compiler.

ULXMAN430,

Unsupported Online Manuals

UDXMAN430

Online reference pages for programs found
in the Base Extension subset.

ULXMOD2430,

Modula-2 Development Package

Requires:
UDTDCMT430
or
ULTDCMT430

Modula-2 compiler and libraries.
ULXNEWS430,

USENET News Interface Software

UDXNEWS430

Software needed to participate in the
USENET news network.

ULXNOTES430,

Notesfiles Package

UDXNOTES430

Software that lets you establish
notesfiles on your ULTRIX system.

ULXRCS430,

Revision Control System

UDXRCS430

Programs that make up a package similar to
the SCCS facility provided with the
supported software subsets.

ULXSHELLS430,

Aux. Command Line Interpreters

UDXSHELLS430

The "distributed" shell and a version of
the C shell that features command
completion.

Requires:
ULTCOMM430
and
ULTUUCP430,
or
UDTCOMM430
and
UDTUUCP43°

Unsupported Software Subsets C-3

Subset Name

Contents

ULXSPMS430

Software Project Management System

Dependencies

A package useful for managing large
software development efforts.
ULXTERM430,
UDXTERM430

Additional Terminal Drivers

Optional

Additional terrninfo files and terminal
drivers

ULXTOOLS430* ,

Misc. User-Contributed Utilities

UDXTOOLS430*

Small utilities contributed by the user
community.

ULXUNEXAMP430,

Unsupported DECwindows Examples

UDXUNEXAMP430

DECwindows programming examples.

ULXUNFONTS430

Unsupported MIT fonts

UDXUNFONTS430

MIT fonts

ULXUNMAN430,

Unsupported XII Reference Pages

UDXUNMAN430

Online reference pages for unsupported XII
R4 features that are in the UDXUNMIT430
and ULXUNMIT430 subsets.

ULXUNMIT430

Unsupported XII R4 Components

UDXUNMIT430

Programs and fonts for the X Window
System protocol level 11, Release 4.
Contains applications such as xt errn,
xload, and xedit.

ULXVARIAN430

Raster Plotter Package
Software used to typeset documents on the
VARIAN typesetter.

C-4 Unsupported Software Subsets

Requires:
ULTDCMT430 or
UDTDCMT430

Sample Advanced Installation Procedure

The following is a sample log of an advanced installation performed on a DEC station
5000 Model 200. What the installation software displays depends on the type of
system you have and the type of media you are using, but the installation procedure
for all systems and media is similar.

0.1

Sample Advanced Installation Procedure.
*** STANDALONE ULTRIX ENVIRONMENT ***
If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.
If you require additional installation choices, select the ADVANCED
Installation option.
Select one of the following options:
1) BASIC Installation
2) ADVANCED Installation
3) System management
Enter your choice: 2
*** SYSTEM DISK SELECTION ***
The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:
SYSTEM DISK TABLE
Selection

Device
Name

ULTRIX
Name

Device
Number

1
2
3
4

RZ56
RZ56
RZ56
RZ56

rzO
rz1
rz2
rz3

o
1
2
3

Controller
Name
SCSI
SCSI
SCSI
SCSI

Controller
Number

o
o
o
o

Enter your choice: 1
You selected RZ56, device number O. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.
Use RZ56, rzO, for your system disk? (yin)

[]: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, rzO RZ56.
Making the root file system on rzO RZ56.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, rzO RZ56.
*** BOOTSTRAP COMMAND SEQUENCE ***

Issue the following console commands to set your default bootpath variable
and to boot your system disk:
»
»

setenv boot "5/rzO/vmunix -a"
boot

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter.
For example, tinker.
Enter your system name:

laforge

You selected laforge as the name of your system.
Is this correct? (yin) [y]: y
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:
yymmddhhmm
Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format.
For example, 11:30
p.m. on May 3, 1991 would be entered as:
9105032330
Enter the date and time: 9206161439
*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.
Selection Time Zone
e
c
m
p
g

Eastern
Central
Mountain
Pacific
Greenwich

Enter your choice: e
Does your area alternate between Daylight Savings and Standard
time? (yin) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.
Selection Geographic Area
u

a
e
c
w

USA
Australia
Eastern Europe
Central Europe
Western Europe

Enter your choice [u): u

0-2 Sample Advanced Installation Procedure

The current date and time is Tue Jun 16 14:39:23 EDT 1992

*** FILE SYSTEM DEFAULT OPTION ***
The following table shows the default file system layout on RZ56, rzO:
partition
a
b
g

bottom
0
32768
163840

top
32767
163839
731505

overlap
c
c
c,d,e

size
32768
131072
567666

default
root
swap, dump
/usr

If you choose the defaults, the var area will be allocated to /usr/var.
Do you want to choose the default file system layout? (y/n) : y
Making the new file system for /usr on /dev/rrzOg RZ56

Select one of the options below that describes the type of display
being used:
1) Black and White
2) Color
3) Gray Scale
Enter your choice: 2

*** SUPPORTED SOFTWARE INSTALLATION ***
Remove the tape containing the BOOT/UPGRADE software and replace it with
the tape containing the SUPPORTED software subsets.
Please make sure your installation tape is mounted and on-line.
Are you ready (y/n)? y
Positioning Tape

*** Enter Subset Selections ***
The following subsets are mandatory and will be installed automatically:
* Base System
* Kernel Config Files
* TCP/IP Networking Utilities
* Network File System utilities
* Extended (Berkeley) Mailer
* B&W, Color, or PX Server
* X11R4 PXG Server
* Xll/DECwindows User Environment
* Xll/DECwindows 75dpi Fonts
* Xll/DECwindows 100dpi Fonts
* X11/DECwindows PEX Fonts
The subsets listed below are optional:
1) Truecolor Server
3) RAND Mail Handler
5) Communications Utilities
7) Maintenance Operations Protocol
9) Kerberos Network Authentication
11) Prestoserve Utilities
13) Doc. Preparation for Ref. Pages
15) Adobe Font Metric Files
17) Source Code Control System
19) Internationalization Dev. Env.
21) CDA Software Dev Libraries
23) RPC Development Environment
25) Reference Pages for Programers
27) Additional DECwindows Applications
29) Worksystem Development Environment
31) UWS Runtime Reference Pages
33) Wavefront Personal Visualizer

2)
4)
6)
8)
10)
12)
14)
16)
18)
20)
22)
24)
26)
28)
30)
32)
34)

Printer Support Environment
Sys. Config. Mgmt. Program (SCAMP)
Unix-to-Unix Copy Facility
Accounting Software
Enhanced Security Features
System Exerciser Package
Doc. Preparation Extensions
Software Development Utilities
Internationalization Runtime Env.
CDA Base System
RPC Runtime Environment
Ref. Pages for Sys. Admin. & Users
programming Examples
DECwindows Mail Application
System Management Tools
UWS Development Reference Pages
Personal Visualizer Manual Page

35) All of the Above
36) None of the Above
37) Exit without installing subsets

Sample Advanced Installation Procedure 0-3

Enter your choice(s): 35
You are installing the following subsets:
Base System
TCP/IP Networking Utilities
Extended (Berkeley) Mailer
X11R4 PXG Server
X11/DECwindows 75dpi Fonts
X11/DECwindows PEX Fonts
Printer Support Environment
Sys. Config. Mgmt. Program (SCAMP)
Unix-to-Unix Copy Facility
Accounting Software
Enhanced Security Features
System Exerciser Package
Doc. Preparation Extensions
Software Development Utilities
Internationalization Runtime Env.
CDA Base System
RPC Runtime Environment
Ref. Pages for Sys. Admin. & Users
Programming Examples
DECwindows Mail Application
System Management Tools
UWS Development Reference Pages
Personal Visualizer Manual Page

Kernel Config Files
Network File System Utilities
B&W, Color, or PX Server
X11/DECwindows User Environment
X11/DECwindows 100dpi Fonts
Truecolor Server
RAND Mail Handler
Communications Utilities
Maintenance Operations Protocol
Kerberos Network Authentication
Prestoserve Utilities
Doc. Preparation for Ref. Pages
Adobe Font Metric Files
Source Code Control System
Internationalization Dev. Env.
CDA Software Dev Libraries
RPC Development Environment
Reference Pages for Programers
Additional DECwindows Applications
Worksystem Development Environment
UWS Runtime Reference Pages
Wavefront Personal Visualizer

Is this correct? (y/n): y
Base System (UDTBASE430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 14:52:45 EDT 1992
Working .... Tue Jun 16 14:54:58 EDT 1992
Working .... Tue Jun 16 14:57:14 EDT 1992
Verifying
Working .... Tue Jun 16 14:58:40 EDT 1992
Kernel Config Files (UDTBIN430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 14:59:31 EDT 1992
Working .... Tue Jun 16 15:01:48 EDT 1992
Working .... Tue Jun 16 15:03:53 EDT 1992
Working .... Tue Jun 16 15:06:02 EDT 1992
Verifying
Working .... Tue Jun 16 15:07:11 EDT 1992
TCP/IP Networking Utilities (UDTINET430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:08:19 EDT 1992
Verifying
Network File System Utilities (UDTNFS430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:10:04 EDT 1992
Verifying
Extended (Berkeley) Mailer (UDTUMAIL430)
Copying from /dev/nrmtOh (tape)
Verifying
B&W, Color, or PX Server (UDWSER430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:11:37 EDT 1992
Working .... Tue Jun 16 15:12:16 EDT 1992
Verifying
X11R4 PXG Server (UDWWSTSER430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:13:52 EDT 1992
Working .... Tue Jun 16 15:14:26 EDT 1992
Verifying

D-4 Sample Advanced Installation Procedure

X11/DECwindows User Environment (UDWXl1430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:15:30 EDT 1992
Verifying
X11/DECwindows 75dpi Fonts (UDWFONT430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:17:20 EDT 1992
Verifying
X11/DECwindows 100dpi Fonts (UDWFONT15430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:18:28 EDT 1992
Verifying
X11/DECwindows PEX Fonts (UDWFONTSTR430)
Copying from /dev/nrmtOh (tape)
Verifying
Truecolor Server (UDWXTXSER430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 15:20:13 EDT 1992
Working .... Tue Jun 16 15:21:34 EDT 1992
Verifying
Printer Support Environment
(UDTPRINT430)
Copying from /dev/nrmtOh (tape)
Volume change. Rewinding tape ...

Working .... Tue Jun 16 15:22:25 EDT 1992

Please remove tape volume 1 and replace it with volume 2.
Are you ready (y/n)? y
Working .... Tue Jun 16 16:13:26 EDT 1992
Verifying
RAND Mail Handler
(UDTMH430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:14:26 EDT 1992
Verifying
Sys. Config. Mgmt. Program (SCAMP)
Copying from /dev/nrmtOh (tape)
Verifying

(UDTSMSCAMP430)

Communications utilities
(UDTCOMM430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:17:06 EDT 1992
Verifying
Unix-to-Unix Copy Facility
(UDTUUCP430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:17:45 EDT 1992
Verifying
Maintenance Operations Protocol
(UDTMOP430)
Copying from /dev/nrmtOh (tape)
Verifying
Accounting Software
(UDTACCT430)
Copying from /dev/nrmtOh (tape)
Verifying
Kerberos Network Authentication
(UDTKERB430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:19:38 EDT 1992
Verifying
Enhanced Security Features
(UDTSEC430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:20:36 EDT 1992
Verifying

Sample Advanced Installation Procedure 0-5

Prestoserve Utilities
(UDTPREST0430)
Copying from /dev/nrmtOh (tape)
Verifying
System Exerciser Package
(UDTEXER430)
Copying from /dev/nrmtOh (tape)
Verifying
Doc. Preparation for Ref. Pages
(UDTDCMT430)
Copying from /dev/nrmtOh (tape)
Verifying
Doc. Preparation Extensions
(UDTDCMTEXT430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:22:53 EDT 1992
Verifying
Adobe Font Metric Files
(UDTAFM430)
Copying from /dev/nrmtOh (tape)
Verifying
Software Development Utilities
(UDTPGMR430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:24:09 EDT 1992
Verifying
Source Code Control System (UDTSCCS430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:26:07 EDT 1992
Verifying
Internationalization Runtime Env.
Copying from /dev/nrmtOh (tape)
Verifying

(UDTINTLRT430)

Internationalization Dev. Env.
(UDTINTLPGMR430)
Copying from /dev/nrmtOh (tape)
Verifying
CDA Base System (UDTCDABASE430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:27:53 EDT 1992
Verifying
CDA Software Dev Libraries
(UDTCDAPGMR430)
Copying from /dev/nrmtOh (tape)
Verifying
RPC Runtime Environment
(UDTRPCRT430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:29:48 EDT 1992
Verifying
RPC Development Environment
(UDTRPCDEV430)
Copying from /dev/nrmtOh (tape)
Verifying
Ref. Pages for Sys. Admin. & Users
(UDTMAN430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:31:08 EDT 1992
Verifying
Reference Pages for Programers
(UDTMANPGMR430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:32:54 EDT 1992
Verifying
Programming Examples
(UDTEXAMPLES430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:34:35 EDT 1992
Verifying

0-6 Sample Advanced Installation Procedure

Additional DECwindows Applications (UDWDECW430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:35:17 EDT 1992
Working .... Tue Jun 16 16:37:18 EDT 1992
Verifying
DECwindows Mail Application (UDWMAIL430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:38:01 EDT 1992
Verifying
Worksystem Development Environment (UDWXDEV430)
Copying from /dev/nrmtOh (tape)
Working ... . Tue Jun 16 16:38:53 EDT 1992
Verifying
System Management Tools (UDWSYSMGNT430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:41:25 EDT 1992
Verifying
UWS Runtime Reference Pages (UDWMAN430)
Copying from /dev/nrmtOh (tape)
Verifying
UWS Development Reference Pages (UDWMANPGMR430)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:43:09 EDT 1992
Verifying
Wavefront Personal Visualizer (UDWTPV024425)
Copying from /dev/nrmtOh (tape)
Working .... Tue Jun 16 16:44:40 EDT 1992
Working .... Tue Jun 16 16:46:46 EDT 1992
Verifying
Working .... Tue Jun 16 16:48:36 EDT 1992
Personal Visualizer Manual Page (UDWTPVMAN425)
Copying from /dev/nrmtOh (tape)
Verifying

Installation of Wavefront Personal Visualizer V2.4 for ULTRIX on
Tue Jun 16 16:50:15 EDT 1992

Wavefront Personal Visualizer V2.4 for ULTRIX
Installation Procedure succeeded
Rewinding Tape .. .
Working .... Tue Jun 16 16:50:53 EDT 1992
The installation software has successfully installed the software
subsets. You can now remove the tape containing the software subsets
from the device.
Please mount the tape containing the BOOT/UPGRADE subsets.
Please make sure your installation tape is mounted and on-line.
Are you ready (y/n)? y
Positioning Tape
Working .... Tue Jun 16 16:54:35 EDT 1992
Working .... Tue Jun 16 16:56:35 EDT 1992
Working .... Tue Jun 16 16:58:36 EDT 1992
Working .... Tue Jun 16 17:00:37 EDT 1992
The following subsets will be installed:
* Generic Kernel
Do you wish to continue? (y/n): y
Generic Kernel
(UDTGENVMUNIX431)
Copying from /dev/nrmtOh (tape)

Sample Advanced Installation Procedure 0-7

Working .... Tue Jun 16 17:04:01 EDT 1992
Verifying
Rewinding Tape .. .
Working .... Tue Jun 16 17:05:12 EDT 1992
The installation procedure has successfully installed the Upgrade
subsets
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection
1
2
3
4
5
6
7
8
9
10

Kernel Option

Local Area Transport (LAT)
Bisynchronous Communication protocol (VAX only)
Computer Interconnect (CI) network
Diagnostic/Utilities Protocol (DUP)
IS09660 File System Support (CDFS)
Ethernet Packet Filter
Enhanced Security Features
DECnet
All of the above
None of the above

Enter the selection number for each kernel option you want.
For example, 1 3: 1 2 3 4 5 6 8
You specified the following kernel options:
Local Area Transport (LAT)
Computer Interconnect (CI) network
Diagnostic/Utilities Protocol (DUP)
IS09660 File System Support (CDFS)
Ethernet Packet Filter
DECnet
Is this correct? (y/n)

[nl: y

*** SYSTEM CONFIGURATION PROCEDURE ***

Configuration file complete.
Do you want to edit the configuration file?

(y/n)

[nl: n

*** PERFORMING SYSTEM CONFIGURATION ***
working
Tue Jun 16 17:07:40 EDT 1992
working
Tue Jun 16 17:09:40 EDT 1992
working
Tue Jun 16 17:11:41 EDT 1992
*** DEVICE SPECIAL FILE CREATION ***
working ..... Tue Jun 16 17:12:47 EDT 1992
*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:
/vmunix
/genvmunix
/usr/adm/install.log
/usr/adm/install.FS.log
/usr/adm/install.DEV.log

0-8 Sample Advanced Installation Procedure

customized kernel
generic kernel
installation log file
file systems log file
special device log file

Index

console boot default

advanced installation
defined, 1-3

updating, 4-21
console media
updating, 4-21

example, D-l
selecting menu option, 4-1

console terminal
defined, 1--4
crash dump

defined, 2-5
var area and, 2-7

backing up the system, 1-6
basic installation

crash dump space
allocating, 4-10

defined, 1-2

disk connection and controller, 2-5n

selecting menu option, 4-1

examples of partial, 2-6t

BIND server

requirements, 2-5

files to back up, 1-7
Bisynchronous Communication Protocol, 2-12t

CSR addresses, 1--4

block, 2-1
boot default

updating, 4-21
booting
over the network, 3-1
byte, 2-1

data disk
defined, 1--4
date
specifying, 4-5

daylight savings/standard time status

CDROM optical disc cartridge, 1-1

DECnet,2-12t

chpt command, 2-1

DECstation 2100 processor

specifying, 4-5

querying disk partition layout, 2-3e
client
registering as, 3-1
Computer Interconnect (CI), 2-12t
configuration file
adding kernel options, 4-18
editing during installation, 4-19
planning the file entries, 2-11

booting procedure for, 3--4
DECstation 3100 processor
booting procedure for, 3--4
DECstation 31008 processor
booting procedure for, 3--4
DECstation 5000, Model 100 processor
booting procedure for, 3-6
DECstation 5000, Model 200 processor
booting procedure for, 3-6

DECsystem 3100 processor
booting procedure for, 3--4

DEC system 5000, Model 200 processor

F
Factory Installed Software, 1-1
file system

booting procedure for, 3-6

specifying default partitions, 4-6

DEC system 5100 processor

specifying existing partitions, 4-5

booting procedure for, 3-9

DECsystem 5400 processor

worksheet, 2-11 t

floating address space

booting procedure for, 3-11

hardware devices and, 4-19

DEC system 5500 processor
booting procedure for, 3-12

DECsystem 5810 processor
booting procedure for, 3-15

G
geographic area

DECsystem 5820 processor
booting procedure for, 3-15

DECsystem 5830 processor

specifying, 4-5

Gray Scale Monitor
specifying, 4-12

booting procedure for, 3-15

DECsystem 5840 processor
booting procedure for, 3-15

dfcommand

H
hardware
required for installation, 1--4

measuring space in KB, 2-1

DiagnosticlUtilities Protocol (DUP), 2-12t
disk configuration worksheets, 2-3t
disk partition layout
choosing, 4-3

IS09660 File System Support, 2-12t

deciding whether to accept the default, 2-10
modifying,2-3e

specifying default, 4-6

kernel options, 2-12t

disk quotas
setting, 2-9

Diskless Management Services
booting over the network, 3-1
disks
identifying supported system, 2-2

specifying during installation, 4-18

kilobyte, 2-1

L
Local Area Transport (LAT), 2-12t

enhanced security features, 2-12t

mandatory subsets

error logger file
space requirements for, 2-7

Ethernet packet filter, 2-12t

space allocation for, 2-9

megabyte, 2-1
MicroVAX 2000 processor
booting procedure for, 3-17

MicroVAX 3100 processor
booting procedure for, 3-19
updating console boot default, 4-21

Index-2

MicroVAX 3300 processor
booting procedure for, 3-22

RIse supported software subsets, A-I to A-6
RISe unsupported software subsets, C-l to C--4

updating console boot default, 4-21
MicroVAX 3400 processor
booting procedure for, 3-22
updating console boot default, 4-21
MicroVAX 3500 processor

s
savecore utility
saving a core dump with, 2-7

booting procedure for, 3-24

sector, 2-1

updating console boot default, 4-21

setld command

MicroVAX 3600 processor
booting procedure for, 3-24
MicroVAX 3800 processor
booting procedure for, 3-24
MicroVAX 3900 processor
booting procedure for, 3-24
MicroVAX II processor
booting procedure for, 3-24
MT9 magnetic tape kit, 1-1

adding software subsets, 6-1
deleting software subsets, 6-2
listing software subsets, 6-1
single-system disk
unsupported,2-2n
software distribution device
description, 1--4
selecting, 4-2
software distribution kit
components of, 1-5
software subset

adding, 6-1

network
booting over, 3-1

software subsets
adding, 6-1
adding from file server, 6-2

adding from tape, 6-2
defined,2-9

optional subsets
space allocation for, 2-9

deleting, 6-2
listing, 6-1
RISC supported, A-I to A-6

RISC unsupported, C-l to C--4

post-installation procedures, 4-23
post-installation tasks, 4-23t
processor
booting procedure for, 3-6
processor-specific boot instructions
locations of, 3-1 t

selecting, 4-14
VAX supported, B-1 to B-6
VAX unsupported, C-l to C--4
standalone ULTRIX environment, 7-1 to 7-3
defined, 1--4
subsets
adding, 6-1
deleting, 6-2

installing, 4-14

rebooting procedure, 4-5
Remote Installation Services, 1-2
booting over the network, 3-1
RIS directory

listing status, 6-1
superuser password
logging in with, 4-22
specifying, 4-5, 4-6

space requirements for, 2-8

Index-3

swap space

lusr file system (cont.)

crash dump space and, 2-4

space requirements for, 2-10

defined, 2-4

worksheet, 2-10t

partition a, 2-4n
swapl space

allocating, 4-8
swap2 space
allocating, 4-9
sysinit command
initializing the system with, 3-36
system accounting
space requirements for, 2-7
system disk
selecting, 4-3
system disk drive
defined, 1-4
system disk partition
changing the disk partition table, 4-4
system disks, 2-2t

var area, 2-10
allocating, 4-11
defined, 2-6
determining size, 2-6
space requirements for, 2-6
var area worksheet
completing, 2-8t
VAX 6000-nnn series processor
booting procedure for systems with a CIBCA-AA
controller, 3-32
booting procedure for systems with a CIBCA-AB
controller, 3-33
booting procedure for systems without a CIBCA-

system information

AA controller, 3-32

specifying, 4-5

updating console boot default, 4-21

system management menu option, 4-1
system name
specifying, 4-5
system time
specifying, 4-5
system upgrade, 1-2

VAX 6210 processor
booting procedure for, 3-32
VAX 6220 processor
booting procedure for, 3-32
VAX 6230 processor
booting procedure for, 3-32
VAX 6240 processor
booting procedure for, 3-32

VAX 6310 processor

tape cartridge kit, 1-1
time zone
specifying, 4-5

booting procedure for, 3-32
VAX 6320 processor
booting procedure for, 3-32
VAX 6330 processor

booting procedure for, 3-32
VAX 6340 processor

ULTRIX name of distribution device, 4-2
ULTRIX subsets, 4-14
upgrade installation
defined, 1-2
upgrade procedure, 5-1
user area, 2-9

lusr file system
allocating, 4-7

Index-4

booting procedure for, 3-32
VAX 6350 processor
booting procedure for, 3-32
VAX 6360 processor
booting procedure for, 3-32
VAX 8200 processor
booting procedure for, 3-34
updating console media, 4-21

VAX 8250 processor

VAX-ll/785 processor

booting procedure for, 3-34

booting procedure for, 3-30

updating console media, 4-21

VAX 8300 processor
booting procedure for, 3-34
updating console media, 4-21
VAX 8350 processor
booting procedure for, 3-34
updating console media, 4-21
VAX 8500 processor
booting procedure for, 3-36
VAX 8530 processor
booting procedure for, 3-36
VAX 8550 processor
booting procedure for, 3-36
VAX 8600 processor
booting procedure for, 3-37
updating console media, 4-21
VAX 8650 processor
booting procedure for, 3-37
updating console media, 4-21
VAX 8700 processor
booting procedure for, 3-36
VAX 8800 processor
booting procedure for, 3-36
VAX 8810 processor
booting procedure for, 3-36
VAX 8820 processor
booting procedure for, 3-38
VAX 8830 processor
booting procedure for, 3-38
VAX 8840 processor
booting procedure for, 3-38
VAX 9000 processor
booting procedure for, 3-40
VAX supported software subsets, B-1 to B-6
VAX unsupported software subsets, C-l to C-4
VAX-ll/750 processor

VAXserver 100 processor
booting procedure for, 3-24
VAXserver 2000 processor
booting procedure for, 3-17
VAXserver 3100 processor
booting procedure for, 3-19
VAXserver 3300 processor
booting procedure for, 3-22
updating console boot default, 4-21
VAXserver 3400 processor
booting procedure for, 3-22
updating console boot default, 4-21
VAXserver 3500 processor
booting procedure for, 3-24
VAXserver 3600 processor
booting procedure for, 3-24
VAXserver 3800 processor
booting procedure for, 3-24
VAXserver 3900 processor
booting procedure for, 3-24
VAXserver 6000-nnn series processor
booting procedure for, 3-32
VAXstation 2000 processor
booting procedure for, 3-17
VAXstation 3100 processor
booting procedure for, 3-19
VAXstation 3200 processor
booting procedure for, 3-24
VAXstation 3500 processor
booting procedure for, 3-24
VAXstation 3520 processor
booting procedure for, 3-26
VAXstation 3540 processor
booting procedure for, 3-26
VAXstation II processor

booting procedure for, 3-28

booting procedure for, 3-24

updating console media, 4-21

VAXstation IIIGPX processor

VAX-ll/780 processor
booting procedure for, 3-30

booting procedure for, 3-24
vrnunix, 2-11

updating console media, 4-21

Index-5

w
worksheets

disk configuration, 2-3t
file system, 2-11 t
lusr file system, 2-IOt

var,2-8t

y
Yellow Pages server

files to back up, 1-7

Index-6

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-343-4040 before placing
your electronic, telephone, or direct mail order.

Electronic Orders
To place an order at the Electronic Store, dial 800-234-1998 using a 1200- or 2400-bps modem from
anywhere in the USA, Canada, or Puerto Rico. If you need assistance using the Electronic Store, call
800-DIGITAL (800-344-4825).

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA, Alaska,
or Hawaii

800-DIGITAL

Digital Equipment Corporation
P.o. Box CS2008
Nashua, New Hampshire 03061

Puerto Rico

809-754-7575

Local Digital subsidiary

Canada

800-267-6215

Digital Equipment of Canada
Attn: DECdirect Operations KA0212
P.O. Box 13000
100 Herzberg Road
Kanata, Ontario, Canada K2K 2A6

International

Local Digital subsidiary or
approved distributor

Internala

SSB Order Processing - WMOlE15
or
Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

a For internal orders, you must submit an Internal Software Order Form (EN-OI740-07).

Reader's Comments

ULTRIX
Guide to Installing ULTRIX
AA-PBLOE-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

Please rate this manual:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

D
D
D
D
D
D
D
D

What would you like to see more/less of?

What do you like best about this manual?

What do you like least about this manual?

Please list errors you have found in this manual:
Page
Description

Additional comments or suggestions to improve this manual:

What version of the software described by this manual are you using? _ _ _ _ _ __
NamefTitle
Dept.
Company _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ___ Date _ _ _ _ __
Mailing Address
_ _ _ _ _ _ _ _ _ _ _ _ _ Email

Phone _ _ _ _ _ _ __

· - - - - -.

Do Not Tear - Fold Here and Tape

!lmlDlllM

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL
FIRST-CLASS MAIL PERMIT NO. 33 MAYNARD MA
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
OPEN SOFTWARE PUBLICATIONS MANAGER
ZK03-3N32
110 SPIT BROOK ROAD
NASHUA NH 03062-9987

1111 III did 11111111111 III 111111111 dII 1111111111111
.------.

Do Not Tear- Fold Here

._--------------------------------------------------------------,

Cut
Along
Dotted
Line