![[Return to Library]](BOOKSHLF.GIF)
![[TOC]](TOC.GIF)
![[PREV]](REW.GIF)
![[NEXT]](FF.GIF)
![[INDEX]](INDEX.GIF)
![[Help]](HELP.GIF)
The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 1-1.
1.1 Quick Start for Experienced Users of the Full Installation
If you are an experienced user of the Digital UNIX operating system,
you should read the overview information in this chapter. The Digital UNIX Version 4.0B
installation procedure has two user interfaces that you may want to read about
before beginning. After reading the overview information in this chapter refer
to Table 1-2 for quick start instructions.
The following statements qualify you as an experienced user:
If you want to perform an update installation and you are an experienced user, go directly to Chapter 2.
If you are not an experienced user, Digital recommends that you read this chapter in its entirety.
While you are entering information during the installation setup phase,
the graphical and text-based interfaces record your responses in a configuration
description file (CDF). The installation procedure uses the information stored
in the CDF to configure disk and file systems and to install the selected
software subsets. After the installation, the CDF is located on the newly-installed
system in /var/adm/smlogs/install.cdf.
The CDF can be used to clone another system with
a similar hardware configuration. Refer to Section 1.5.4
for a description of cloned installations.
Table 1-3 lists the common characteristics
of the two user interfaces.
1.2 Software Distribution Media
There are two types of distribution media you can use to install the Digital UNIX
base operating system:
Deciding which distribution media to use for the installation
depends on the following:
1.3 Types of User Interfaces: Graphical and Text Based
Two user interfaces are available for the Digital UNIX full installation
process:
The type of interface presented during the full installation
is determined automatically based on your hardware configuration and the amount
of memory on your system. Systems with graphical consoles and a minimum of
32 MB of memory present a graphical interface to the installation. Systems
with consoles that do not have graphics capabilities or have less than 32
MB of memory present a text-based interface.
1.4 Preinstallation Tasks
Table 1-4
summarizes the preinstallation tasks to complete before beginning any software
installation.
If you plan to run your system as a dataless client of a DMS server, consult your DMS server administrator or Sharing Software on a Local Area Network. On a dataless client, the root and /usr file systems are located on a dataless server and are exported to your system. You do not need the instructions in this book to run your system as a dataless client. Note
You need some or all of the following
items to install the Digital UNIX operating system software:
You need at least one supported disk to contain the root
and /usr file systems and swap space.
You will use this disk to boot your system after the installation. If you
perform a custom installation, you can allocate the /usr
and /var file systems and swap spaces
to disks other than the disk that contains the root file system. Refer to Section 3.4 for more information about supported disks.
A data disk is a disk on which data and user files are stored and on
which no Digital UNIX file system resides. The installation procedure does
not configure these disks.
The console terminal communicates with your system during the installation.
If you plan to connect ISA
devices to your system (for example, floppy controllers, graphics cards),
use the isacfg console command to supply the appropriate
configuration information.
The isacfg console command is available on systems
that have an ISA bus. There is information about the command in the user
documentation for each of the systems that support ISA bus devices. If you
need to know more about the format of the command, enter
The System Reference Manual (SRM) console firmware provides information
about
the
ISA bus devices that come configured with Digital systems as well as the device
handles that are set up. Use the following console firmware command to view
this information:
When you specify a device with the isacfg command,
you must use a handle as the name of the device. The following table lists
the handles for optional ISA devices that you can configure for your system.
1.4.1 Check the Hardware for Installation Readiness
Ensure that you have the hardware needed for an installation.
You must know the location and function of the controls and indicators on
your hardware. Verify that all cables and connectors are hooked up and that
the system is plugged in. Refer to your hardware owner's documentation for
more information.
1.4.1.1 Configuring ISA Devices Before the Installation
The information in this section
applies only if your system has an Integrated System Architecture (ISA) bus
(most AlphaStations).
>>> help isacfg
>>> isacfg -all
| Device | Handle |
|---|---|
| Ethernet LeMAC (DE203, DE204, DE205) | DE200-LE |
| Sound board | PCXBJ |
| ATI Mach64 SVGA graphics | MACH64 |
| Generic VGA graphics | ISA--VGA °Section 5.18 |
| Any other kernel device driver kit | Handle defined by vendor °Section 5.18 |
Use the -handle handle-name flag to specify the device handle. The following example sets the parameters for configuring the DE205 Ethernet controller. When you issue such a command, let the input line wrap; do not press the Return key in the middle of the line:
>>> isacfg -slot 1 -dev 0 -mk -handle DE200-LE -irq0 5 -iobase0 300 -membase0 d0000 -memlen0 10000 -etyp 1 -enadev 1See your hardware documentation for more information about ISA configuration.
You should install the DGLTA ATM adapter before installing Digital UNIX Version 4.0B
so that the installation procedure properly detects the presence of the ATM
adapter and automatically installs the ATM software subsets. If you install
the ATM adapter after installing Digital UNIX, you must boot the system using
the generic kernel /genvmunix, install the ATM software
subsets from the CD-ROM or RIS server, and then run the doconfig program to rebuild your system kernel to enable the added ATM support.
You need a connection to the network (via Ethernet, Token Ring, or FDDI)
and to a RIS server if you plan to perform a Remote Installation Services
(RIS) installation over a local area network (LAN). Refer to your hardware
installation guide for information about network connections.
If you are installing over a network connection to a RIS server, follow
these steps:
Your system is not able to communicate with the RIS server if you obtain
the following results from the /sbin/ping command:
If you obtain the previous results, ask the RIS server System Administrator
to troubleshoot the problem.
Refer to Sharing Software on a Local Area Network for more information about RIS.
The Release Notes also provide descriptions of features that are new
to the Digital UNIX Version 4.0B operating system or have changed significantly
from previous releases.
A printed version of the Release Notes is included in the Digital UNIX Software Distribution Kit
you received.
Before you begin any software installation procedure, Digital recommends
that you perform a full back up of your current operating system. Refer to System Administration
for information about backing up your system.
The Alpha AXP Systems Firmware Update Release Notes Overview
describes how to mount the firmware CD-ROM
and how to print processor-specific firmware update instructions. To mount
the firmware CD-ROM if your system is already running Digital UNIX, the kernel
must be configured for the ISO 9660 Compact Disc File System (CDFS). The CDFS option must be present in the kernel configuration file to
configure CDFS in the kernel. Refer to System Administration for more information.
Table 1-6 provides the minimum firmware requirements
for processors running Digital UNIX Version 4.0B.
1.4.1.2 Installing ATM Adapters Before the Installation
The information in this section applies only if you plan to use
Asynchronous Transfer Mode (ATM) adapters.
1.4.1.3 Installing on SCSI RAID Devices
If you are installing the Digital UNIX
operating system on a SCSI RAID device, only LUN 0 can
be used for the installation's target device. The RAID device's LUN 0 must be configured before you attempt to install the software.
Refer to Section 1.4.7.2 for more information about RAID
devices.
1.4.2 Check the Software Distribution Kit
You should have received a Software Distribution Kit
that contains, among other items, the Digital UNIX CD-ROMs. A Part
Listing is included in the box and lists the contents of the Software Distribution Kit.
At a minimum, the Software Distribution Kit contains the following CD-ROMs and
documents:
1.4.3 Check Network Connections for RIS Installations
If you have a RIS server at your site, ask the RIS server administrator
whether or not you can perform a RIS installation.
# /sbin/ping -c2 server
Successful
output of the /sbin/ping command is similar to the following:
# ping -c2 system9
PING system9 (16.59.l24.96): 56 data bytes
64 bytes from 16.59.l24.96: icmp_seq=0 ttl=255 time=1 ms
64 bytes from 16.59.l24.96: icmp_seq=1 ttl=255 time=0 ms
----system9 PING Statistics----
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1 ms
In the previous example, system9 is the name of the RIS server.
1.4.4 Read the Digital UNIX Release Notes
Read the Digital UNIX Release Notes
before beginning any software installation procedure. The Release Notes document
any last-minute changes to the software. This information might be required
for a successful installation.
1.4.5 Back Up the System
This step applies only if your system
is already running the Digital UNIX operating system and you have critical
files that you want to preserve.
1.4.5.1 Special Considerations for Systems Running LSM, LVM, Prestoserve, and
AdvFS
If your system is currently running Digital UNIX and is using the Logical
Storage Manager (LSM), the Logical Volume Manager (LVM), Prestoserve, or the
Advanced File System (AdvFS), refer to Appendix A for
special preinstallation backup tasks for these products.
1.4.6 Update System Firmware
Digital distributes console
firmware for certain processors whenever the operating system is updated or
as is required. To run Digital UNIX Version 4.0B, your system might require
a firmware update. Firmware updates are located on the Alpha Systems Firmware CD-ROM Version 3.8
compact disc that is included with your Digital UNIX Software Distribution Kit.
Firmware updates for all supported processors reside on the firmware CD-ROM.
The firmware revision level may be different for each processor.
Hardware configuration diskettes are usually shipped with a system when
you first receive it. If you do not have the appropriate diskette and did
not receive one in the Software Distribution Kit, contact your local Digital sales
office or the vendor from which you obtained the hardware.
For Digital UNIX Version 4.0B software, the supported ECU firmware revision
is 1.9 or higher. If your
system has an EISA bus you will receive a floppy disk that contains the ECU.
This floppy disk may be included in the Digital UNIX Software Distribution Kit.
For Digital UNIX Version 4.0B software, the supported RCU revision level
is 3.11 or higher. The
RCU is included on the Alpha Systems Firmware CD-ROM Version 3.8.
An update installation updates your operating system from Digital UNIX Version 4.0 or 4.0A
to Digital UNIX Version 4.0B. If your operating system predates Digital UNIX Version 4.0 or 4.0A,
you can perform successive update installations to reach Version 4.0B. Refer
to Table 2-3 for instructions on how to perform successive
update installations.
A full installation affects many of the system files from the previous
version of Digital UNIX. File systems and swap areas created during a full
installation will overwrite existing data on disks and partitions where they
are installed. The full installation searches for and invokes user-supplied
files to enable customizations on the system to be installed. The files can
be on diskette, a RIS server, the /var/tmp directory on
the system to be installed, or on CD-ROM.
A cloned installation refers to the process of configuring file systems
and installing software on your system exactly as another similar-type system
is configured. The cloned installation searches for and invokes user-supplied
files to enable customizations on the system to be installed. The files can
be on diskette, a RIS server, the /var/tmp directory on
the system to be installed, or on CD-ROM.
The following sections describe these types of installations.
You should not perform an update installation if you want to change
file system type or change the location of file systems. An update installation
does not permit changes to file systems or disk layout.
An update installation does not update optional layered products, but
you can still perform an update installation if you have layered products
installed. Some layered products operate properly with Digital UNIX Version 4.0B
and others must be reinstalled with a version that is compatible with Digital UNIX Version 4.0B.
Some layered products, such as DECnet/OSI for Digital UNIX, must be deleted
before the update begins and then reinstalled after the update completes. Section 2.5 provides a complete list of the layered products that
must be deleted before the update installation.
Completion time varies depending on your processor type,
the number of software subsets to be updated, whether you are
using CD-ROM or RIS to perform the update, and the speed of your CD-ROM
drive if you are using CD-ROM. You need to respond to prompts only during
the initial phase of the update. After that, the update installation runs
unattended.
1.4.6.1 Updating Firmware on AlphaPC64, AlphaPC164, EB64+, EB66+, and EB164 Single-Board Computers
The EB64+ single-board computer uses a socketed firmware ROM chip. The
EB66+, AlphaPC64, AlphaPC164, and EB164 single-board computers use an EPROM
that can be updated with new firmware. Refer to your hardware owner's documentation
for details on how to update the console firmware on these systems.
1.4.7 Run Hardware Configuration Utilities
As
described in the following sections, depending upon the type of hardware you
have, you may have to run hardware configuration update utilities before the
installation.
1.4.7.1 Minimum EISA Configuration Utility (ECU) Firmware Revision Level
Before installing Digital UNIX on a system with an
Extended Integrated System Architecture (EISA) bus, you must run the EISA
Configuration Utility (ECU). Follow the instructions in your hardware owner's
guide.
1.4.7.2 Minimum RAID Configuration Utility (RCU) Revision Level
Before installing Digital UNIX on a system employing
RAID technology, you must run the RAID Configuration Utility (RCU). Follow
the instructions provided in your hardware owner's guide.
1.4.7.3 Updating the Advanced RISC Computing (ARC) Console
Advanced
RISC Computing (ARC) is an alternate console interface that was designed to
support the Windows NT operating system. Some system configuration utilities
may require you to switch to the ARC console. Refer to your hardware owner's
guide for more information. To run Digital UNIX Version 4.0B, you may need
to update the console firmware. The ARC firmware update is included on the Alpha Systems Firmware CD-ROM Version 3.8.
1.4.7.4 Updating the System Reference Manual (SRM) Console
To run Digital UNIX Version 4.0B, you may
need to update the SRM console firmware. The SRM firmware update is included
on the Alpha Systems Firmware CD-ROM Version 3.8. Refer to your hardware owner's guide for more information.
1.5 Installation Types: Update, Full, and Cloned
You
can perform an update installation, a full installation which has default
or custom procedures, or a cloned installation procedure to install the Digital UNIX Version 4.0B
operating system.
Note
NOTE
1.5.1 Description of an Update Installation
An update installation updates
the Digital UNIX base
operating system from Version 4.0 or 4.0A to Digital UNIX Version 4.0B.
The update installation preserves user files, data files, print and network
configurations, user accounts, and any other system setup and customization
you may have done. Preserving this data is an advantage over the full installation
because a full installation creates new file systems and swap areas that overwrite
any existing data on the disk partitions where the file systems and swap areas
are to be installed.
| How do you start an update installation? |
|---|
| Follow the instructions in Chapter 2. |
The file system type for all file systems is the UNIX File System (UFS).
One swapping area is configured; other swap areas can be added after the
installation. Optional software subsets can be installed later by using the setld command. By performing a default installation, you can have
your operating system running with a minimum amount of work because a default
installation uses preset defaults for file system layout, file system type,
and kernel build options. Following is the file system layout for a default
installation:
1.5.2 Description of a Default Installation
A default installation is a full installation that
installs a default, mandatory set of Digital UNIX software subsets on a
predetermined file system layout on a single disk. The only decision you have
to make is what single disk will contain the root and /usr file systems and swap area.
| How do you start a default installation? |
|---|
|
Systems with less than 32 MB of memory do not have the option to select
the Advanced File System (AdvFS) as the file system type for root, /usr or /var.
In addition to installing the mandatory set of Digital UNIX software
subsets, the custom installation lets you select optional software subsets
to customize your system. Dependencies between optional software subsets
are checked and resolved.
The amount of free space remaining in the root, /usr, and /var file systems is displayed as you
select each optional software subset to install.
The graphical user interface provides access to the Disk Configuration
Utility. This utility lets you repartition disks before or after you select
optional software if the partition you chose is too small for a particular
file system.
1.5.3 Description of a Custom Installation
A custom installation is a full installation that
lets you customize the file system layout and lets you select optional software
to install. You can use one or more disks, and you have the option to configure
a second swap area. You can choose the UNIX File System (UFS) or the Advanced
File System (AdvFS) as the file system type for the root, /usr, and /var file systems. You may also choose
additional kernel options to tailor your kernel for specific use.
| How do you start a custom installation? |
|---|
|
When a system is installed with Digital UNIX Version 4.0B, a configuration
description file (CDF) is generated that contains installation-specific configuration
information based on the results of the questions answered during the installation.
This file is located on the installed system in the /var/adm/smlogs directory under the file name install.cdf. The
CDF contains all the configuration information required to perform an initial
system installation on a client system.
Once a suitable CDF has been located and optionally modified, the administrator
has minimal involvement in the installation cloning process on the client
systems. A cloned installation procedure uses the same disks and partitions
to create a file system layout and installs the same set of software subsets
as defined in the CDF. If your system is set up to perform a cloned installation,
you do not have to answer any installation questions related to disk and software
selections because the answers are already stored in the CDF.
When you start a text-based, menu-driven installation, the UNIX shell
is presented as an option from the first menu. If you are using the graphical
interface, you access the UNIX shell from a button labeled UNIX Shell.
Regardless of the interface, this option
puts your system into a Bourne shell in single-user mode with superuser privileges.
To restart the installation procedure for the UNIX shell, enter restart.
The distribution media (CD-ROM or RIS) contains file systems that
are laid out just as the software would be installed on the system and contains
directly accessible root, /usr, and /var areas. This format makes almost every Digital UNIX command
and utility available in the UNIX shell even if your operating system is not
yet fully functional. In effect, the mounted distribution media is a complete Digital UNIX
file system.
The UNIX shell provides a way for you to recover from serious problems
such as root file system corruption and enables you to
perform general file system and disk maintenance tasks during the installation.
Digital recommends that only experienced users choose the UNIX shell option.
Refer to Chapter 7 for more information about
the UNIX shell.
If you decided to perform an update installation, Chapter 2
contains all the information you need.
If the RIS administrator has set up your system for a cloned installation,
make sure you perform the preinstallation tasks described in Section 1.4
and then boot your system from the RIS server as described in Chapter 4.
Refer to Section 5.1.3 for the sequence of events
during a cloned installation.
1.5.4 Description of a Cloned Installation
A cloned installation lets you duplicate the file system layout,
file system type, and software subset selections from a system that has already
been installed with Digital UNIX Version 4.0B.
1.6 UNIX Shell Option
Both the text-based and graphical installation interfaces provide a
way for you to access a UNIX shell. The primary purpose of the UNIX shell
option is to provide a way to perform disk and file system maintenance before
the installation and to perform disaster recovery tasks.
1.7 Summary of the Installation Procedure
Table 1-10 summarizes the procedure for
the default and custom installations regardless of the interface (graphical
or text-based). Review these steps to prepare yourself for the information
you must enter during the actual installation procedure.
Connect the hardware as shown in the hardware documentation, and turn
on power to the processor and monitor. After some initial system initialization
messages are displayed, you are prompted to enter information such as the
system's host name, root password, geographic location
and time zone, and the current date and time. The FIS Quick Reference
Card is also included in the box with your system and describes
how to respond to the prompts for this information.
After
the kernel build process is complete, refer to Chapter 6
for information about setting up your system for general use.
If the FIS setup halts unexpectedly and you see the root
system prompt (#), make a note of any error
messages that appear on the screen. Then, press Ctrl/d
to restart the configuration phase. Usually the installation continues, but
you will need to correct the error when setup is complete. Refer to the appropriate Digital UNIX
document or hardware document to identify and correct the error.
If the error prevents the configuration from proceeding, it may be necessary
to reinstall Digital UNIX. To do this, boot your processor as shown in Chapter 4 and refer to Section 1.5
to decide whether you need to do a default or custom installation. You can
also consult the RIS system administrator to determine if your system is a
suitable candidate for a cloned installation. If you choose the custom installation,
be aware that the system disk may already have a customized disk partition
table. The customization is usually done at the factory to create disk partitions
that are large enough to hold all the software originally installed on the
disk.
During the text-based custom installation, you are asked whether you
want to preserve the customized partitions or use the default partition table.
This option is described in Section 5.8.5. If
you choose not to preserve the customized partitions, you may not be able
to reload all the software that was originally installed.
A FIS system is generally installed with all base operating system software
subsets (those that are prefixed with OSF) and some associated
products. If you do not need to reinstall all the original software subsets
and want to install mandatory software subsets only, perform a default installation.
If you want to install mandatory and optional software, perform a custom
installation. Use the setld command if you want to install
or remove software subsets after an installation.
The default and custom installation procedures are described in Chapter 5.
If you want to install the latest version of the worldwide language
support software subsets, your system must already be installed with the Digital UNIX Version 4.0B
base operating system. Then, follow the worldwide installation instructions
in Chapter 9.
The worldwide language support software subsets are located on the CD-ROM
labeled Digital UNIX V4.0B Associated Products Volume 1.
If you want to perform an update installation of the latest version
of the worldwide language subsets, follow the worldwide update installation
instructions in Chapter 10.
Descriptions of the worldwide language support software subsets are
located in Appendix F.
1.8 If Your System Has Factory Installed Software (FIS)
Your
system may have been delivered to you with Factory Installed Software (FIS);
that is, a version of Digital UNIX is already installed. Included in the box
with your system is the Factory Installed Software Information
Sheet that describes the software products that are preinstalled
for you and how the system is configured.
1.9 Installing Worldwide Language Support Software
Digital UNIX is an internationalized operating system. The worldwide
language support software subsets provide support for various native languages
and countries.
Installing the worldwide language support software
subsets enables software developers to develop internationalized software
that can be used in different countries.