The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 1-1.
After reading this chapter, you will ... |
---|
Perform preinstallation tasks. |
Decide whether to use CD-ROM or the network for the distribution media. |
Decide what type of installation you want to do. |
The following statements qualify you as an experienced user:
If you have experience performingfull installations... | FollowInstructions In: |
---|---|
Perform preinstallation tasks for the full installation. | Section 1.4 |
Shut down and halt your processor, then use the processor-specific boot commands to boot off the CD-ROM or network. | Table 4-2 |
Enter all information requested by the installation procedure. | Chapter 5 |
Log in to the newly-installed system. | Section 5.21 |
Set up your system for general use. | Chapter 6 |
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.
Similarities between user interfaces include ... |
---|
All questions are asked and answered before your system is changed in any way |
Free disk space is calculated and displayed automatically during software selection |
Software subset dependencies are checked and resolved automatically |
Online help is available |
A UNIX shell is available to access UNIX commands and utilitiesbefore and during the installation setup process. The UNIX shell can also be used for disaster recovery and maintenance purposes. |
Installation Task | FollowInstructions In: |
---|---|
Check the hardware for installation readiness. | Section 1.4.1 |
Check the Software Distribution Kit. | Section 1.4.2 |
If you are performing a RIS installation, ensure your system is registered as a client of the RIS server. | Section 1.4.3 |
Read the Digital UNIX Release Notes. | Section 1.4.4 |
Back up (save) the current version of your operating system. | Section 1.4.5 |
Update the system firmware. | Section 1.4.6 |
Run hardware configuration utilities. | Section 1.4.7 |
Decide the type of installation to perform (update, default, custom, or cloned). | Section 1.5 |
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.
>>> help isacfg
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:
>>> isacfg -all
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.
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 |
>>> 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:
# /sbin/ping -c2 serverSuccessful 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 msIn the previous example, system9 is the name of the RIS server.
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.
Alpha System | Minimum Firmware Level |
---|---|
AlphaPC64 SBC | Version 4.5 |
AlphaPC164 SBC | Version 4.5 |
AlphaServer 300 | Correct firmware is installed. ° |
AlphaServer 400 | Version 6.3 |
AlphaServer 1000 | Version 4.7 |
AlphaServer 1000A | Version 4.7 |
AlphaServer 2000 | Version 4.7 |
AlphaServer 2100 | Version 4.7 |
AlphaServer 2100A | Version 4.7 |
AlphaServer 4000/4100 | Version 3.0 |
AlphaServer 8200 | Version 4.1 |
AlphaServer 8400 | Version 4.1 |
AlphaStation 200 | Version 6.3 |
AlphaStation 250 | Version 6.3 |
AlphaStation 255 | Version 6.3 |
AlphaStation 400 | Version 6.3 |
AlphaStation 500 | Version 6.3 |
AlphaStation 600 | Version 6.3 |
Alpha VME 4/224 | Version 1.0 |
Alpha VME 4/288 | Version 1.0 |
Alpha VME 5/nnn | Version 1.0 |
AXPvme 64 | Version 16.0 |
AXPvme 100 | Version 16.0 |
AXPvme 160 | Version 16.0 |
AXPvme 166 | Version 15.0 |
AXPvme 230 | Version 15.0 |
AXPpci | X4.7 |
DEC 2000 | Version 2.2 |
DEC 3000 | Version 6.9 |
DEC 4000 | Version 3.9 |
DEC 7000 | Version 4.9 |
DEC 10000 | Version 4.9 |
Digital Alpha VME 2100 | Version 4.3 |
Digital 21064A PICMG Alpha CPU | X4.7 |
Digital 21164A PICMG Alpha CPU | X4.7 |
EB64+ SBC | Version 4.5 |
EB66+ SBC | Version 4.5 |
EB164 SBC | Version 4.5 |
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.
If you plan to run this system as a dataless client of a DMS server, refer to the Sharing Software on a Local Area Network guide for more information. Note
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.
See Appendix C for more information on installation cloning and user-supplied scripts. NOTE
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.
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:
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.
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.
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.
Installation Task | Applies to Default orCustom Installation? | InformationLocated In: |
---|---|---|
Complete preinstallation tasks. | Default/Custom | Section 1.4 |
Plan disk space and file system layout. | Custom | Chapter 3 |
Optionally, create user-supplied files. | Default/Custom | Appendix C |
Invoke the full installation procedure by booting the system from the network or CD-ROM. | Default/Custom | Chapter 4 |
Select the type of installation to perform. | Default/Custom | Section 5.3 |
Enter a host name, location and time zone, and date and time for CD-ROM installations. | Default/Custom | Section 5.4 through Section 5.7 |
Select a disk for the root file system. | Default/Custom | Section 5.8 |
Select the file system type for the root file system. | Custom | Section 5.9 |
Select the disk and partitions for the /usr and /var file systems. | Custom | Section 5.10 and Section 5.11 |
Select the file system type for /usr and /var. | Custom | Section 5.9 |
Select up to two swap areas. | Custom | Section 5.12 |
Install mandatory software subsets only. | Default | Section 5.13 |
Install mandatory and select optional software subsets. | Custom | Section 5.14 |
Enter commands to reboot the system. | Default/Custom | Section 5.18 |
The installation procedure configures the system and software. | Default/Custom | Section 5.19 |
The installation procedure builds the kernel for default installations. | Default | Section 5.20 |
After you select kernel options, the installation procedure builds the kernel. | Custom | Section 5.20.1 |
Log in for the first time as the user root. | Default/Custom | Section 5.21 |
Set up system for general use. | Default/Custom | Chapter 6 |
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.