ULTRIX and UWS Guide to Installing ULTRIX and UWS Order Number: AA-PBL0G-TE March 1994 Product Version: ULTRIX and UWS, Version 4.4 This guide describes the basic and advanced installation procedures for ULTRIX and UWS on all supported processors. This guide also describes how to upgrade a system without performing 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). Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Copyright Digital Equipment Corporation 1987, 1988, 1989, 1990, 1992, 1993, 1994 All rights reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, Alpha AXP, AXP, Bookreader, CDA, DDIS, DEC, DEC FUSE, DECnet, DECstation, DECsystem, DECUS, DECwindows, DTIF, MASSBUS, MicroVAX, OpenVMS, Q-bus, ULTRIX, ULTRIX Mail Connection, ULTRIX Worksystem Software, UNIBUS, VAX, VAXstation, VMS, XUI, and the DIGITAL logo. IBM is a registered trademark of International Business Machines Corporation. INGRES is a registered 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 registered trademark of Interface Technologies Corporation. Open Software Foundation, OSF, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. Adobe, PostScript, and Display PostScript are registered trademarks of Adobe Systems, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc., a wholly-owned subsidiary of Novell, Inc. All other trademarks and registered trademarks are the property of their respective holders. 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: +o 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. +o Standalone system management procedures, which operate in a memory-resident environment to support limited system management activities. _A_u_d_i_e_n_c_e The audience for this guide is anyone installing an ULTRIX system. The guide assumes that: +o You or a Digital Field Service representative has checked the hardware to ensure that it is working properly. +o You have read the documentation supplied with your hardware. +o You have read the current version of the _R_e_l_e_a_s_e _N_o_t_e_s. +o You know the location and function of the controls and indicators on your hardware. +o You understand how to load and unload the installation media and know which disks are needed during the installation. +o You have a basic understanding of the ULTRIX file system and commands. _O_r_g_a_n_i_z_a_t_i_o_n This guide has seven chapters, five 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 _s_e_t_l_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. Appendix E Provides notes about installation and upgrade issues occurring before Version xii About This Manual 4.4. Read these notes to see if they pertain to your configuration. _R_e_l_a_t_e_d _D_o_c_u_m_e_n_t_a_t_i_o_n 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. _R_e_l_e_a_s_e _N_o_t_e_s This document contains media labeling, subset sizes, and other installation-related notes, for the operating system and for layered products. Please read the release notes sections on installation, upgrades, and layered products before beginning the installation or upgrade procedures. 3. _U_L_T_R_I_X _a_n_d _U_W_S _S_y_s_t_e_m _N_o_t_e_s This document contains installation-related notes, for the operating system and for layered products. Please read the system notes sections on installation, upgrades, and layered products before beginning the installation or upgrade procedures. 4. _G_u_i_d_e _t_o _S_y_s_t_e_m _a_n_d _N_e_t_w_o_r_k _S_e_t_u_p This document can help you determine what to do after you complete the advanced installation. 5. _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k This documentation describes how to install software products over the network. About This Manual xiii _C_o_n_v_e_n_t_i_o_n_s # 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. _c_a_t(1) A cross-reference to a reference page includes the appropriate section number in parentheses. For example, _c_a_t(1) indicates that you can find information on the _c_a_t 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, ). xiv About This Manual Preparing for the Installation 1 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: +o Read the _R_e_l_e_a_s_e _N_o_t_e_s and the _U_L_T_R_I_X _a_n_d _U_W_S _S_y_s_t_e_m _N_o_t_e_s The _R_e_l_e_a_s_e _N_o_t_e_s and the _U_L_T_R_I_X _a_n_d _U_W_S _S_y_s_t_e_m _N_o_t_e_s contain information about installing and upgrading the software. Included are hardware, boot, and general installation notes, such as outstanding problems and their workarounds. Additionally, the notes contain information about layered products that installers may need to know. The _R_e_l_e_a_s_e _N_o_t_e_s 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 systems you will install. +o Check to be sure you have the hardware needed for the installation +o Check the contents of the software distribution kit against the Bill of Materials +o Back up the system if you need to retain any information from your previous system +o 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. +o 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. Work through Chapter 2 before beginning the advanced installation to determine if you have enough disk space on your system. _1._1 _C_h_e_c_k_i_n_g _t_h_e _H_a_r_d_w_a_r_e _N_e_e_d_e_d _f_o_r _I_n_s_t_a_l_l_a_t_i_o_n 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: +o 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. +o 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. +o 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. +o 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. 1-2 Preparing for the Installation You may need to 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 _e_d 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 _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e for information about the configuration file. _N_o_t_e 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._2 _C_h_e_c_k_i_n_g _t_h_e _S_o_f_t_w_a_r_e _D_i_s_t_r_i_b_u_t_i_o_n _K_i_t Use the Part Listing to check your software distribution kit. The software distribution kit includes this installation guide and one of the following: +o A TK50 for systems with TK50 or TK70 tape cartridge drives +o A CD-ROM optical disc kit for systems with RRD40 or RRD42 optical disc drives +o 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. Preparing for the Installation 1-3 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. _1._3 _B_a_c_k_i_n_g _U_p _t_h_e _S_y_s_t_e_m Whether you perform an upgrade or an installation, you should back up your system before starting the procedure. _1._3._1 _B_a_c_k_u_p_s _B_e_f_o_r_e _U_p_g_r_a_d_e_s Before you begin an upgrade procedure, you should back up your system disk so you can restore your system to a known state should any errors occur during the upgrade procedure. _1._3._2 _B_a_c_k_u_p_s _B_e_f_o_r_e _B_a_s_i_c _a_n_d _A_d_v_a_n_c_e_d _I_n_s_t_a_l_l_a_t_i_o_n_s 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 _c_h_p_t 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 _G_u_i_d_e _t_o _B_a_c_k_u_p _a_n_d _R_e_s_t_o_r_e. 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 _g_e_t_t_y_t_a_b file. Other files, for example your existing _h_o_s_t_s 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-4 Preparing for the Installation Table 1-1: _N_a_m_e_s _o_f _D_i_r_e_c_t_o_r_i_e_s _a_n_d _F_i_l_e_s _t_o _B_a_c_k _U_p _______________________________________________________________ Directory File _______________________________________________________________ / .cshrc .login .mailrc .profile .rhosts /etc acucap aliases aliases.dir aliases.pag automount.master crontab dumpdates exports fstab gettytab group hosts hosts.equiv hosts.lpd passwd phones printcap rc.local remote resolv.conf sendmail.cf sendmail.fc sendmail.hf sendmail.st services svc.conf svcorder termcap ttys /usr/var/adm aculog lastlog lpd-errs /usr/var/uucp L.cmds LIST.DAY LIST.HOUR LIST.NIGHT LIST.NOON uucp.hour uucp.longhall uucp.night uucp.noon uucp.week USERFILE _______________________________________________________________ You may also want to save the _s_y_s_l_o_g file from the /_u_s_r/_v_a_r/_s_p_o_o_l/_m_q_u_e_u_e directory. In addition to your site-specific files, you need to save the following files and directories: +o If your system runs as a master or a slave Yellow Pages (YP) server, save the /_u_s_r/_v_a_r/_y_p/domain-name directory for your domain. +o 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 /_u_s_r/_v_a_r/_y_p/_s_r_c, save this directory as well. +o If your system runs as a BIND/Hesiod primary server, save the _n_a_m_e_d._b_o_o_t file in the /_u_s_r/_v_a_r/_d_s_s/_n_a_m_e_d_b default directory, all Preparing for the Installation 1-5 database files named in the _n_a_m_e_d._b_o_o_t file, and the /_u_s_r/_v_a_r/_d_s_s/_n_a_m_e_d_b/_s_r_c directory, where the source files are located. Database files have ._d_b extensions, source files have ._r_e_v extensions. _1._4 _D_e_c_i_d_i_n_g _o_n _t_h_e _T_y_p_e _o_f _I_n_s_t_a_l_l_a_t_i_o_n ULTRIX software can be installed on your system in the following ways: +o From TK50 tape cartridges. +o From an RRD40 or RRD42 CD-ROM optical disc cartridge. +o From MT9 magnetic tapes. +o From the network. A Remote Installation Services (RIS) client and a Diskless Management System (DMS) client use the network to install software from a server that has been established with a RIS/DMS area containing the software subsets. +o If your system comes with Factory Installed Software (FIS), all of the ULTRIX supported software subsets are installed at the factory. If you have FIS, you do not need this guide. Refer to the FIS documentation included with your processor. The installation procedure provides four paths for you to follow: the upgrade installation, the basic installation, the advanced installation, or the system managment option. _1._4._1 _U_p_g_r_a_d_e _I_n_s_t_a_l_l_a_t_i_o_n 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 complete the upgrade to the new system version. 1-6 Preparing for the Installation There is one restriction: any customizable files that you have modified and that 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._4._2 _B_a_s_i_c _I_n_s_t_a_l_l_a_t_i_o_n 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 postinstallation 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: +o The root file system +o The /_u_s_r file system +o The crash dump space and the swap space The _v_a_r area is created as a directory under the /_u_s_r file system. The basic installation loads the following required supported software subsets: +o Base System +o Kernel Configuration Files +o Generic Kernel +o TCP/IP Networking Utilities +o Network File System Utilities +o Extended (Berkeley) Mailer If your system is licensed to install ULTRIX Worksystem Software, the following supported software Preparing for the Installation 1-7 subsets are also loaded during the basic installation: +o X11/DECwindows User Environment (when the X11/DECwindows (XUI) user environment is chosen as the preferred windowing interface) +o OSF/Motif User Environment (when the DECwindows for OSF/Motif user environment is chosen as the preferred windowing interface) +o X11/DECwindows 100 dpi fonts or 75 dpi fonts, depending on the user environment +o X11/DECwindows Servers - B&W, Color, or PX Server - True Color Server - PXG Server The basic installation performs the following tasks: +o Builds the kernel +o Reboots the ULTRIX operating system If after completing the installation you decide that you want additional subsets, you can install these subsets using the _s_e_t_l_d utility. See the _s_e_t_l_d(8) reference page for further information. _1._4._3 _A_d_v_a_n_c_e_d _I_n_s_t_a_l_l_a_t_i_o_n 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: +o Preserving customized partitions +o Selecting file system layouts other than the default layouts +o Allocating the /_u_s_r file system to any disk partition on your system 1-8 Preparing for the Installation +o Allocating up to two swap areas to any disk partition on your system +o Allocating the crash dump space to the same disk partition as one of the swap areas or allocating it to a different disk partition +o Allocating the _v_a_r area to the same disk partition as /_u_s_r or allocating it to a different disk partition +o Selecting optional subsets +o Adding options to the kernel configuration file Performing these tasks during the advanced installation has the following advantages: +o It allows for greater flexibility in allocating the file systems to the most appropriate disk partition. +o 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. _N_o_t_e Advanced installations are required for VAXstation 3520 and 3540 systems. _1._4._4 _S_y_s_t_e_m _M_a_n_a_g_e_m_e_n_t _O_p_t_i_o_n 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 Preparing for the Installation 1-9 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._4._5 _N_e_x_t _S_t_e_p 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. 1-10 Preparing for the Installation Planning Your Disk Space 2 You need to complete the following tasks before starting the advanced installation: +o Identify available disks +o Plan the swap space +o Plan the crash dump space +o Plan the _v_a_r area +o Plan the /_u_s_r file system +o Plan the kernel configuration file items +o 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: +o _G_u_i_d_e _t_o _D_i_s_k _M_a_i_n_t_e_n_a_n_c_e +o _G_u_i_d_e _t_o _S_y_s_t_e_m _C_r_a_s_h _R_e_c_o_v_e_r_y +o _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e 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 _c_h_p_t command gives the size of partitions in blocks or sectors. However, the _d_f 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: +o One kilobyte (kB) equals 1024 bytes. +o One block equals 1/2 kB (512 bytes); a sector is the same as a block. +o 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 _r_a(4)) or the size in blocks (as displayed by the _c_h_p_t command) by 2048, as shown in the following table: 2-2 Planning Your Disk Space _____________________________________________________ Partition Size in Blocks Size in MB _____________________________________________________ _a 32768 16 _b 131072 64 _c 547041 267 _d 163840 80 _e 471041 230 _f 76001 37 _g 383201 187 _____________________________________________________ When you examine disk partitions with the _c_h_p_t command or look in the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s 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 file system 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 _I_d_e_n_t_i_f_y_i_n_g _S_u_p_p_o_r_t_e_d _S_y_s_t_e_m _D_i_s_k_s 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 _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s for information on the default disk partition layout. Table 2-1: _S_u_p_p_o_r_t_e_d _S_y_s_t_e_m _D_i_s_k_s ________________________________________________ ULTRIX Mnemonic Device Name ________________________________________________ _h_p RM05 Planning Your Disk Space 2-3 Table 2-1: (continued) ________________________________________________ ULTRIX Mnemonic Device Name ________________________________________________ _r_a RA60, RA70, RA71, RA72, RA73, RA80, RA81, RA82, RA90, RA92, RD53, RD54, RF30, RF31, RF71, RF72 _r_d RD53 (MicroVAX 2000 and VAXstation 2000 only), RD54 (MicroVAX 2000 and VAXstation 2000 only) _r_z RZ23, RZ23L, RZ24, RZ24L, RZ25, RZ25L, RZ26, RZ28, RZ55, RZ56, RZ57, RZ58, RZ73, RZ74 ________________________________________________ _N_o_t_e RD53, RZ23, and RZ23L disks are not supported as single-system disks. You will need a second suitably sized disk to perform the installation. The system disk contains the root file system and the swap1 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. Using 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 _c_h_p_t 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 2-4 Planning Your Disk Space unit 0, issue the following command: # _c_h_p_t -_q /_d_e_v/_r_r_a_0_a The existing disk partition layout is displayed. Table 2-2: _D_i_s_k _C_o_n_f_i_g_u_r_a_t_i_o_n _W_o_r_k_s_h_e_e_t ________________________________________________________________ Partition Disk Number Device Name ULTRIX Name Partition Size in MB ________________________________________________________________ 0 _____ _____ _a __________ _b __________ _c __________ _d __________ _e __________ _f __________ _g __________ _h __________ 1 _____ _____ _a __________ _b __________ _c __________ _d __________ _e __________ _f __________ _g __________ _h __________ 2 _____ _____ _a __________ _b __________ _c __________ _d __________ _e __________ _f __________ _g __________ _h __________ Planning Your Disk Space 2-5 Table 2-2: (continued) ________________________________________________________________ Partition Disk Number Device Name ULTRIX Name Partition Size in MB ________________________________________________________________ 3 _____ _____ _a __________ _b __________ _c __________ _d __________ _e __________ _f __________ _g __________ _h __________ ________________________________________________________________ _2._2 _P_l_a_n_n_i_n_g _t_h_e _S_w_a_p _S_p_a_c_e 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: swap1 and swap2. (You can allocate additional swap space during day-to-day system management. See the _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e for instructions on how to do this.) Allocate the swap1 space either by accepting the default or by specifying another partition. If you choose the default allocation, the installation software allocates the swap1 space to the _b partition of the system disk. There is no default allocation for swap2 space. _N_o_t_e 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 three 2-6 Planning Your Disk Space to four 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 100 MB of swap space, you could allocate 50 MB to the swap1 space and 50 MB to the swap2 space. Dividing the swap space will improve swapping performance. _N_o_t_e 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 _______________________________________________________________ swap1 _______ ________ ________ ________ swap2 _______ ________ ________ ________ _______________________________________________________________ _2._3 _P_l_a_n_n_i_n_g _t_h_e _C_r_a_s_h _D_u_m_p _S_p_a_c_e The crash dump space is the area on the disk where the kernel writes the memory contents in the event of Planning Your Disk Space 2-7 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 swap1 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 _p_l_u_s the size of the kernel, _v_m_u_n_i_x. The size of the kernel can be up to approximately 4.1 MB. See the _G_u_i_d_e _t_o _S_y_s_t_e_m _C_r_a_s_h _R_e_c_o_v_e_r_y for more information about calculating crash dump space. _N_o_t_e The crash dump space must be on a disk connected to the same controller as the system disk. Table 2-3: _P_a_r_t_i_a_l _C_r_a_s_h _D_u_m_p _S_p_a_c_e _R_e_q_u_i_r_e_m_e_n_t_s ________________________________________________________________ Physical Memory Maximum Number Space Needed Space Needed in MB of Users for RISC (MB) for VAX (MB) ________________________________________________________________ 6 2 not applicable 6 8 2 8 8 16 16 14 10 32 32 20 12 64 64 28 16 128 128 40 26 256 128 40 26 2-8 Planning Your Disk Space Table 2-3: (continued) ________________________________________________________________ 512 256 48 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 _P_l_a_n_n_i_n_g _t_h_e _v_a_r _A_r_e_a The _v_a_r area contains volatile, machine-specific directories and files, like _t_m_p, _s_p_o_o_l, and _a_d_m. You can allocate the _v_a_r 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 _v_a_r area as the directory /_u_s_r/_v_a_r. In determining the size of the _v_a_r area, you need to consider the following: Planning Your Disk Space 2-9 +o The crash dump space +o The error logger +o System accounting +o The size of the _v_a_r/_a_d_m/_r_i_s directory, if appropriate for your system The following sections briefly describe how these items affect the size of _v_a_r. Complete the worksheet in Section 2.4.5 as you work through the sections. _2._4._1 _S_i_z_e _o_f _t_h_e _v_a_r/_a_d_m/_c_r_a_s_h _D_i_r_e_c_t_o_r_y The file system requires room to accommodate the crash dump space. When the system crashes, the _s_a_v_e_c_o_r_e utility writes a partial copy (for partial dumps) or a complete copy (for full dumps) of main memory (_v_m_c_o_r_e) and the _v_m_u_n_i_x image located in the root file system into the swap space. When the system comes back up, _s_a_v_e_c_o_r_e writes these copies of _v_m_c_o_r_e and _v_m_u_n_i_x to files located in the _v_a_r/_a_d_m/_c_r_a_s_h directory. The _v_a_r/_a_d_m/_c_r_a_s_h 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 _G_u_i_d_e _t_o _S_y_s_t_e_m _C_r_a_s_h _R_e_c_o_v_e_r_y 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 _E_r_r_o_r _L_o_g_g_e_r The _v_a_r 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: +o 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. +o Increase this recommended number if you have a 2-10 Planning Your Disk Space 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. +o 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. +o Decrease this recommended number if you have a processor with less memory or a smaller number of peripheral devices. The _G_u_i_d_e _t_o _t_h_e _E_r_r_o_r _L_o_g_g_e_r 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 _S_y_s_t_e_m _A_c_c_o_u_n_t_i_n_g The _a_d_m directory in the _v_a_r area contains data files generated by administrative programs such as _a_c_c_t, _a_c_u_l_o_g, and _w_t_m_p. The data that these programs generate can vary widely from system to system and over time. For example, the file _a_d_m/_a_c_c_t in the _v_a_r 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 for accounting files that occupy about 300 kB for workstations and 3 MB for large systems. See the _G_u_i_d_e _t_o _D_i_s_k _M_a_i_n_t_e_n_a_n_c_e 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 _S_i_z_e _o_f _t_h_e _v_a_r/_a_d_m/_r_i_s _D_i_r_e_c_t_o_r_y If you are going to set up a network kit on your Planning Your Disk Space 2-11 system, you can choose to transfer software subsets from distribution media to the _a_d_m/_r_i_s directory in the _v_a_r area. Anyone with a processor from the VAXstation, MicroVAX, DECstation, or certain DECsystem series of processors can then install the software subsets residing in this directory using the Ethernet. See the _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k for more information on setting up the network kit. You must reserve enough space in the _a_d_m/_r_i_s directory in the _v_a_r 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 _R_e_l_e_a_s_e _N_o_t_e_s for the subset sizes. Fill in the fourth item of the worksheet in Table 2-4 with the amount of space needed for the _a_d_m/_r_i_s directory in the _v_a_r area. _2._4._5 _C_o_m_p_l_e_t_i_n_g _t_h_e _v_a_r _W_o_r_k_s_h_e_e_t Complete the worksheet in Table 2-4 to determine the space requirements for the _v_a_r area. Table 2-4: _v_a_r _W_o_r_k_s_h_e_e_t _____________________________________________________ Item Obtain number from ... Total for var _____________________________________________________ Crash dump Section 2.4.1 ________ space Error logger Section 2.4.2 ________ System Section 2.4.3 ________ accounting Size of the Section 2.4.4 ________ _v_a_r/_a_d_m/_r_i_s directory TOTAL ________ _____________________________________________________ If you plan on using a separate partition for the _v_a_r area, record the ULTRIX name, disk number, and partition where you plan to allocate the _v_a_r file 2-12 Planning Your Disk Space system. _____________________________________________________ ULTRIX Name Disk Number Partition __________ ___________ ___________ _____________________________________________________ _2._5 _P_l_a_n_n_i_n_g _t_h_e /_u_s_r _F_i_l_e _S_y_s_t_e_m The /_u_s_r file system is the directory structure that contains such directories as /_u_s_r/_s_y_s, /_u_s_r/_a_d_m, and /_u_s_r/_b_i_n. You must allocate the /_u_s_r 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 /_u_s_r file system, you need to consider the following: +o The software subsets you plan to install on /_u_s_r +o The amount of user space needed +o The size of the _v_a_r area if it is on the same partition as /_u_s_r The following sections briefly describe how these items affect the size of /_u_s_r. Table 2-5 contains a worksheet that you will complete by working through the sections. _2._5._1 _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s _W_i_t_h_i_n _t_h_e /_u_s_r _F_i_l_e _S_y_s_t_e_m The /_u_s_r 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 _n_r_o_f_f and _c_a_t_m_a_n. Use the tables in the _R_e_l_e_a_s_e _N_o_t_e_s that list RISC 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 Planning Your Disk Space 2-13 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-1 (for RISC 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 _U_s_e_r _A_r_e_a 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 10 MB 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 _G_u_i_d_e _t_o _D_i_s_k _M_a_i_n_t_e_n_a_n_c_e 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. _2._5._3 _v_a_r _A_r_e_a If you plan to place the _v_a_r area on the same partition as /_u_s_r, you must add the size of the _v_a_r area that you determined with the worksheet in Table 2-4 to the total of /_u_s_r. If appropriate for your system, fill in the third item of the worksheet in Table 2-5 with the amount of space needed for _v_a_r. _2._5._4 _C_o_m_p_l_e_t_i_n_g _t_h_e /_u_s_r _W_o_r_k_s_h_e_e_t Complete the worksheet in Table 2-5 to determine the 2-14 Planning Your Disk Space space requirements for the /_u_s_r area. Table 2-5: /_u_s_r _W_o_r_k_s_h_e_e_t _____________________________________________________ Item Obtain Number From ... Total for /usr _____________________________________________________ Software The _R_e_l_e_a_s_e _N_o_t_e_s ________ subsets Size of the Section 2.5.2 ________ user area Size of the Table 2-4 for the _v_a_r ________ _v_a_r area total TOTAL ________ _____________________________________________________ Refer to Table 2-2 to identify partitions that are large enough for the /_u_s_r file system. Record the ULTRIX name, disk number, and partition where you plan to allocate the /_u_s_r file system: _____________________________________________________ ULTRIX Name Disk Number Partition __________ ___________ ___________ _____________________________________________________ _2._6 _D_e_t_e_r_m_i_n_i_n_g _t_h_e _D_i_s_k _P_a_r_t_i_t_i_o_n _L_a_y_o_u_t 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 _c_h_p_t command to use a customized partition layout. If you modify the partition tables for the system disk, the partitions for root and swap1 must meet the following minimum space requirements: +o The root or _a partition must be at least 32,768 blocks (16 MB). Planning Your Disk Space 2-15 +o 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 space requirements for your system. Table 2-6: _F_i_l_e _S_y_s_t_e_m _W_o_r_k_s_h_e_e_t ____________________________________________________________________ Items Approximate SizeDisk Partition ____________________________________________________________________ Root (from Table 2-2) ______ ______ ______ swap1 (from Section 2.2) ______ ______ ______ swap2 (from Section 2.2) ______ ______ ______ Crash dump space (from Section 2.3) ______ ______ ______ /_v_a_r (from Table 2-4; fill in disk ______ (______)(______) and partition lines if applicable) /_u_s_r 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 _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s 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 2-16 Planning Your Disk Space 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 _P_l_a_n_n_i_n_g _t_h_e _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _E_n_t_r_i_e_s Certain layered products require that an entry be added to your system's configuration file for that product to work. For example, Ethernet or _l_a_t drivers require entries 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, _v_m_u_n_i_x. 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. Table 2-7: _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _E_n_t_r_i_e_s _____________________________________________________ Kernel Option Description Add? _____________________________________________________ Local Area Gives you the kernel __________ Transport options and devices (LAT) required to facilitate communications with Digital's Ethernet local area terminal server. Planning Your Disk Space 2-17 Table 2-7: (continued) _____________________________________________________ Kernel Option Description Add? _____________________________________________________ Bisynchronous Gives you access to __________ Communication the 2780 and 3780 protocol (VAX remote job entry only) terminals. Computer Gives you kernel __________ interconnect options and devices (CI) network required to use the internet protocols on the CI wires. Diagnostic Provides a method of __________ utilities communication between protocol a host class driver (DUP) 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. ISO9660 File Allows you to access __________ System an ISO9660 formatted Support CD-ROM as a local, (CDFS) read-only file system. Ethernet Allows you to __________ packet filter implement networking protocols without modifying the kernel, and allows you to monitor the network by receiving packets destined for machines other than your own. 2-18 Planning Your Disk Space Table 2-7: (continued) _____________________________________________________ Kernel Option Description Add? _____________________________________________________ Enhanced Gives you audit, __________ security additional features 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 _S_e_c_u_r_i_t_y _G_u_i_d_e _f_o_r _A_d_m_i_n_i_s_t_r_a_t_o_r_s for further information. 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 installation. You will need to edit the configuration file in the following situations: +o Your system's configuration does not conform to control status register (CSR) address assignment rules. +o You have disk controllers in floating address space. +o You have multiple MSCP controllers, such as KDA50, RQDX, RC25, RRD50, or KFQSA, on the Q-bus. For more information on editing your system's configuration file, see the _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n Planning Your Disk Space 2-19 _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e. Now you are ready to begin the installation. 2-20 Planning Your Disk Space Booting the System 3 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 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 CD-ROM optical disc to boot your system, follow the instructions in the hardware manual included with the CD-ROM. You are booting your system from the network when you are: +o Initiating an installation from a remote server +o Booting a diskless system +o Booting a standalone kernel from a remote server to perform system management tasks To boot your system from the network, you must be registered as a client on a DMS or RIS server. See the _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k 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. Table 3-1: _L_o_c_a_t_i_o_n _o_f _P_r_o_c_e_s_s_o_r-_S_p_e_c_i_f_i_c _B_o_o_t _I_n_s_t_r_u_c_t_i_o_n_s _________________________________________________________ Processor Section _________________________________________________________ DECstation 2100 Section 3.1 Table 3-1: (continued) _________________________________________________________ Processor Section _________________________________________________________ DECstation 3100 Section 3.1 DECstation 3100S Section 3.1 DECstation 5000, Model 100 series Section 3.2 DECstation 5000, Model 200 series Section 3.2 DECstation/DECsystem 5000, Model 150 Section 3.2 DECstation/DECsystem 5000, Model 260 Section 3.2 DECsystem 5900 Model 260 Section 3.2 Personal DECstation/DECsystem Model 50 Section 3.2 Personal DECstation 5000, Model 20, 25, 33 Section 3.2 DECsystem 3100 Section 3.1 DECsystem 5000, Model 25 Section 3.2 DECsystem 5000, Model 200 series Section 3.2 DECsystem 5100 Section 3.3 DECsystem 5400 Section 3.4 DECsystem 5500 Section 3.5 DECsystem 5810 Section 3.6 DECsystem 5820 Section 3.6 DECsystem 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 VAXserver 100 Section 3.10 VAXserver 2000 Section 3.7 VAXserver 3100 Section 3.8 3-2 Booting the System Table 3-1: (continued) _________________________________________________________ Processor Section _________________________________________________________ VAXserver 3300 Section 3.9 VAXserver 3400 Section 3.9 VAXserver 3500 Section 3.10 VAXserver 3600 Section 3.10 VAXserver 3800 Section 3.10 VAXserver 3900 Section 3.10 VAXserver 6000-nnn series Section 3.14 VAXstation II Section 3.10 VAXstation II/GPX Section 3.10 VAXstation 2000 Section 3.7 VAXstation 3100 Section 3.8 VAXstation 3200 Section 3.10 VAXstation 3500 Section 3.10 VAXstation 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 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 Booting the System 3-3 Table 3-1: (continued) _________________________________________________________ Processor Section _________________________________________________________ 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 _________________________________________________________ 3-4 Booting the System _3._1 _D_E_C_s_t_a_t_i_o_n _2_1_0_0/_3_1_0_0/_3_1_0_0_S _o_r _D_E_C_s_y_s_t_e_m _3_1_0_0 _P_r_o_c_e_s_s_o_r To prepare the DECstation 2100/3100/3100S or DECsystem 3100 hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the power to the processor. 3. Remove any TK50 tape cartridges and CD-ROM 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, CD-ROM, or network. The boot command for each distribution kit is described in this section. _3._1._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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/UWS V4.4 (RISC) BOOT/UPGRADE 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: >> _t_e_s_t -_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(0, _u_n_i_t-_n_u_m_b_e_r) Replace _u_n_i_t-_n_u_m_b_e_r with the unit number of your tape drive. Booting the System 3-5 The following example shows the command to boot the system from tape drive number 5. >> _b_o_o_t -_f _t_z(_0,_5) 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 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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 CD-ROM optical disc with the label ULTRIX/UWS V4.4 (RISC) 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: >> _t_e_s_t -_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(0, _u_n_i_t-_n_u_m_b_e_r,0)vmunix Replace _u_n_i_t-_n_u_m_b_e_r 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: >> _b_o_o_t -_f _r_z(_0,_4,_0)_v_m_u_n_i_x Next, the installation software displays some system information, followed by the memory and hardware configurations. 3-6 Booting the System You have completed booting your system. Continue the installation procedure with Chapter 4. _3._1._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type a command with the following syntax at the console mode prompt: boot -f mop(_n_e_t-_i_n_t_e_r_f_a_c_e) If you have more than one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with the number of the interface you want to use. If you have only one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with zero (0). 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. Booting the System 3-7 _3._2 _D_E_C_s_t_a_t_i_o_n _5_0_0_0 _S_e_r_i_e_s, _D_E_C_s_y_s_t_e_m _5_0_0_0 _S_e_r_i_e_s, _P_e_r_s_o_n_a_l _D_E_C_s_t_a_t_i_o_n _5_0_0_0 _S_e_r_i_e_s, _a_n_d _t_h_e _D_E_C_s_y_s_t_e_m _5_9_0_0 _P_r_o_c_e_s_s_o_r_s To prepare these processors: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the power to the processor. 3. Remove any TK50 tape cartridges and CD-ROM 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, CD-ROM, or network. Before beginning, you must determine the slot and device numbers of your boot device. _3._2._1 _D_e_t_e_r_m_i_n_i_n_g _t_h_e _S_l_o_t _a_n_d _D_e_v_i_c_e _N_u_m_b_e_r_s _o_f _Y_o_u_r _B_o_o_t _D_e_v_i_c_e The instructions in this section assume that if you have multiple disk drives, CD-ROM 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 _D_e_t_e_r_m_i_n_i_n_g _t_h_e _S_l_o_t _N_u_m_b_e_r (_D_e_f_a_u_l_t) To determine which controllers and devices are configured on your system, type the following command at the console prompt: >> _c_n_f_g This command displays the options present on the system. Your system will display output similar to the following (the output will differ depending on 3-8 Booting the System your system configuration): 7:KN02-AA DEC V5.3a TCF0 (16 MB) 6:PMAD-AA DEC V5.3a TCF0 (enet:08-00-2b-16-85-7e) 5:PMAZ-AA DEC v5.3a TCF0 (SCSI=7) 2:PMAZ-AA DEC v5.3a TCF0 (SCSI=7) 1:PMAG-AA DEC T3.0a TCF0 (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 X5.4g TCF0 (32 MB) (enet: 08-00-2b-16-58-d6) (SCSI = 7) 1: PMAG-CA DEC V5.3a TCF0 (PX -- D=8) _3._2._1._2 _D_e_t_e_r_m_i_n_i_n_g _t_h_e _B_o_o_t _D_e_v_i_c_e _N_u_m_b_e_r To determine the device number of your boot device, type a command with the following syntax: cnfg _s_l_o_t__n_u_m_b_e_r For example, to determine the device number of a SCSI disk drive with a controller in slot 5, type the following command: >> _c_n_f_g _5 The system displays a table similar to the following: 5: PMAZ-AA DEC V5.3a TCF0 (SCSI = 7) ----------------------------------------------------------- DEV PID VID REV SCSI DEV ----------------------------------------------------------- ----------------------------------------------------------- rz3 RZ56 (C)DEC DEC 0200 DIR tz5 SEQ In this 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). Booting the System 3-9 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 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (RISC) BOOT UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. To determine the device number of the SCSI tape, use the same slot number and device number determined by the _c_n_f_g command in Section 3.2.1.2. For example to boot a SCSI tape (tz) at slot 5, drive 5, type the following command: >> _b_o_o_t _5/_t_z_5 You have completed booting your system. Continue the installation procedure with Chapter 4. _3._2._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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 CD-ROM optical disc with the label ULTRIX/UWS V4.4 (RISC) 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: 3-10 Booting the System boot _s_l_o_t__n_u_m_b_e_r/rz_d_e_v_i_c_e__n_u_m_b_e_r/vmunix Replace _s_l_o_t-_n_u_m_b_e_r with the slot number of the CD-ROM controller. Replace _d_e_v_i_c_e-_n_u_m_b_e_r 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: >> _b_o_o_t _1/_r_z_4/_v_m_u_n_i_x You have completed booting your system. Continue the installation procedure with Chapter 4. _3._2._4 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system from the network, use a command with the following syntax: boot _s_l_o_t__n_u_m_b_e_r/mop Replace _s_l_o_t__n_u_m_b_e_r with the slot number of the network controller. For example, to boot from the network on slot number 6, type the following command: >> _b_o_o_t _6/_m_o_p 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. Booting the System 3-11 _3._3 _D_E_C_s_y_s_t_e_m _5_1_0_0 _P_r_o_c_e_s_s_o_r To prepare the DECsystem 5100 hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the power to the processor. 3. Remove any TK50 tape cartridges and CD-ROM 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, CD-ROM, or network. The boot command for each distribution kit is described in this section. _3._3._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (RISC) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Use the following command to determine the unit number of the drive for your device: >> _c_o_n_f 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(0, _u_n_i_t-_n_u_m_b_e_r) Replace _u_n_i_t-_n_u_m_b_e_r with the unit number of your tape drive. 3-12 Booting the System The following example shows the command to boot the system from tape drive number 5: >> _b_o_o_t -_f _t_z(_0,_5) 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._3._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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 CD-ROM optical disc with the label ULTRIX/UWS V4.4 (RISC) 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: >> _c_o_n_f 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(0,_u_n_i_t-_n_u_m_b_e_r,0)vmunix Replace _u_n_i_t-_n_u_m_b_e_r 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: >> _b_o_o_t -_f _r_z(_0,_4,_0)_v_m_u_n_i_x Next, the installation software displays some system information, followed by the memory and hardware configurations. Booting the System 3-13 You have completed booting your system. Continue the installation procedure with Chapter 4. _3._3._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type a command with the following syntax at the console mode prompt: boot -f mop(_n_e_t-_i_n_t_e_r_f_a_c_e) If you have more than one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with the number of the interface you want to use. If you have only one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with zero (0). 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-14 Booting the System _3._4 _D_E_C_s_y_s_t_e_m _5_4_0_0 _P_r_o_c_e_s_s_o_r To prepare the DECsystem 5400 hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the 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.4 (RISC) BOOT/UPGRADE into the tape drive. Ensure the tape is on line 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: >> _m_a_i_n_t When the VAX console prompt appears, enter the following command: >>> _s_h_o_w _d_e_v_i_c_e 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: >>> _e_x_i_t 4. Use a command with the following syntax to boot your system: boot -f tm(0, _u_n_i_t-_n_u_m_b_e_r) Replace _u_n_i_t-_n_u_m_b_e_r with the unit number of your tape drive. Booting the System 3-15 The following example shows the command to boot the system from tape drive number 0: >> _b_o_o_t -_f _t_m(_0,_0) 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-16 Booting the System _3._5 _D_E_C_s_y_s_t_e_m _5_5_0_0 _P_r_o_c_e_s_s_o_r To prepare the DECsystem 5500 series processor hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the power to the processor. 3. Remove any TK50 tape cartridges and CD-ROM 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, CD-ROM, 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.4 (RISC) BOOT/UPGRADE into the tape drive. Ensure the tape is on line 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: >> _m_a_i_n_t When the VAX console prompt appears, enter the following command: >>> _s_h_o_w _d_e_v_i_c_e 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: >>> _e_x_i_t Booting the System 3-17 _3._5._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _S_C_S_I _T_a_p_e _D_e_v_i_c_e Use a command with the following syntax to boot your system: boot -f tz(0, _u_n_i_t-_n_u_m_b_e_r) Replace _u_n_i_t-_n_u_m_b_e_r with the unit number of your tape drive. The following example shows the command to boot the system from tape drive number 0: >> _b_o_o_t -_f _t_z(_0,_0) You have completed booting your system. Continue the installation procedure with Chapter 4. _3._5._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _Q-_b_u_s _T_a_p_e _D_e_v_i_c_e Use a command with the following syntax to boot your DECsystem 5500 from a Q-bus tape: boot -f tm(0, _u_n_i_t-_n_u_m_b_e_r) Replace _u_n_i_t-_n_u_m_b_e_r with the unit number of your tape drive. The following example shows the command to boot your DECsystem 5500 from tape drive number 0: >> _b_o_o_t -_f _t_m(_0,_0) You have completed booting your system. Continue the installation procedure with Chapter 4. _3._5._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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 CD-ROM optical disc with the label ULTRIX/UWS V4.4 (RISC) SUPPORTED into the drive. Wait for the drive to be on line and ready. 2. Use the following command to determine the unit 3-18 Booting the System number of the drive for your device: >> _s_h_o_w _d_e_v_i_c_e_s 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(_c_o_n_t_r_o_l_l_e_r-_n_u_m_b_e_r, _u_n_i_t-_n_u_m_b_e_r,0)vmunix Replace _c_o_n_t_r_o_l_l_e_r-_n_u_m_b_e_r with the controller number. Replace _u_n_i_t-_n_u_m_b_e_r 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: >> _b_o_o_t -_f _r_z(_0,_4,_0)_v_m_u_n_i_x 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._5._4 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type a command with the following syntax at the console mode prompt: boot -f mop(_n_e_t-_i_n_t_e_r_f_a_c_e) If you have more than one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with the number of the interface you want to use. If you have only one network interface, replace _n_e_t-_i_n_t_e_r_f_a_c_e with zero (0). 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. Booting the System 3-19 _3._6 _D_E_C_s_y_s_t_e_m _5_8_1_0/_5_8_2_0/_5_8_3_0/_5_8_4_0 _P_r_o_c_e_s_s_o_r To prepare the DECsystem 5810/5820/5830/5840 hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Turn on the 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: >> 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.4 (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: >> _s_h_o_w _c_o_n_f_i_g A display, similar to the following, appears on your screen. It shows what is assigned to each slot number on your system: Type Rev 1+ KN58A/A (8081) 0000 2 KN58A/B 9+ MS62A (4001) 0002 E+ DWMBA/A (2001) 0002 XBI E 1+ DWMBA/B (2107) 000A 2+ KDB50 (010E) 131C 4+ CIBCA (0108) 41C2 6+ TBK70 (410B) 0307 C+ DEBNI (0118) 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 3-20 Booting the System 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(/x0x_s_l_o_t-_n_u_m_b_e_r/b_n_o_d_e-_n_u_m_b_e_r, _u_n_i_t- _n_u_m_b_e_r) Replace _s_l_o_t-_n_u_m_b_e_r with the slot number of your XBI adapter. Replace _n_o_d_e-_n_u_m_b_e_r with the node number on the XBI where your TBK70 controller is located. Replace _u_n_i_t-_n_u_m_b_e_r 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 for a TBK70 controller located on XBI node 6: >> _b_o_o_t -_f _t_m_s(/_x_0_x_e/_b_6,_6) 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. Booting the System 3-21 _3._7 _M_i_c_r_o_V_A_X _2_0_0_0, _V_A_X_s_e_r_v_e_r _2_0_0_0, _o_r _V_A_X_s_t_a_t_i_o_n _2_0_0_0 _P_r_o_c_e_s_s_o_r The following instructions assume you have no bootable software on any device in your system. To prepare the MicroVAX 2000, VAXserver 2000, or VAXstation 2000 hardware: 1. Set the system unit on/off switch to 1 (on). 2. Turn on the power to the disk expansion box (if present). 3. Turn on the power to the TZK50 expansion box (if present). 4. Turn on the power to peripheral devices, such as printers or modems. 5. Remove any TK50 tape cartridges and RX50 or RX33 diskettes from their associated drives. After about 20 seconds, the monitor displays a power-up test sequence similar to: KA410 V1.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: TK50 or network. The boot command for each distribution kit is described in this section. 3-22 Booting the System _3._7._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (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 _m_u_a_0 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._7._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type the following command at the console mode prompt: >>> _b _e_s_a_0 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. Booting the System 3-23 _3._8 _M_i_c_r_o_V_A_X _3_1_0_0, _V_A_X_s_e_r_v_e_r _3_1_0_0, _o_r _V_A_X_s_t_a_t_i_o_n _3_1_0_0 _P_r_o_c_e_s_s_o_r The following instructions assume you have no bootable software on any device in your system. To prepare the MicroVAX 3100, VAXserver 3100, or VAXstation 3100 hardware: 1. Set the monitor on/off switch to 1 (on). 2. Turn on the power to all disk expansion boxes (if present). 3. Turn on the power to all TZK50 and CD-ROM optical disc expansion boxes (if present). 4. Set the system unit on/off switch to 1 (on). 5. Turn on the power to peripheral devices, such as printers and modems. 6. Remove any TK50 tape cartridges and CD-ROM optical discs from their associated drives. After about 20 seconds, the monitor displays a power-up test sequence similar to this: KA42-B V1.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, CD-ROM, or network. The boot command for each distribution kit is described in this section. 3-24 Booting the System _3._8._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (VAX) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Type the following command to determine the drive from which to boot: >>> _s_h_o_w _d_e_v_i_c_e 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 _s_h_o_w _d_e_v_i_c_e 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 _m_k_a_5_0_0 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._8._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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-25 Follow this procedure to boot the system: 1. Load the CD-ROM optical disc with the label ULTRIX/UWS V4.4 (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: >>> _s_h_o_w _d_e_v_i_c_e 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 _s_h_o_w _d_e_v_i_c_e 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 _d_k_b_4_0_0 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._8._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type the following command at the console mode prompt: >>> _b _e_s_a_0 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-26 Booting the System _3._9 _M_i_c_r_o_V_A_X _3_3_0_0/_3_4_0_0 _o_r _V_A_X_s_e_r_v_e_r _3_3_0_0/_3_4_0_0 _P_r_o_c_e_s_s_o_r To prepare the MicroVAX 3300/3400 or VAXserver 3300/3400 hardware: 1. Turn on the power to the console terminal and all additional peripheral devices. 2. Set the front panel HALT ENABLE/DISABLE switch to the halt enabled position. 3. Turn on the 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 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (VAX) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Type the following command at the console mode Booting the System 3-27 prompt: >>> _b _m_u_a_0 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._9._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type the following command at the console mode prompt: >>> _b _e_s_a_0 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-28 Booting the System _3._1_0 _M_i_c_r_o_V_A_X _I_I, _M_i_c_r_o_V_A_X _3_5_0_0/_3_6_0_0/_3_8_0_0/_3_9_0_0, _V_A_X_s_e_r_v_e_r _1_0_0/_3_5_0_0/_3_6_0_0/_3_8_0_0/_3_9_0_0, _V_A_X_s_t_a_t_i_o_n _3_2_0_0/_3_5_0_0, _V_A_X_s_t_a_t_i_o_n _I_I, _o_r _V_A_X_s_t_a_t_i_o_n _I_I/_G_P_X _P_r_o_c_e_s_s_o_r This section describes how to boot the following processors: +o MicroVAX II +o MicroVAX 3500/3600/3800/3900 +o VAXserver 100/3500/3600/3800/3900 +o VAXstation 3200/3500 +o VAXstation II +o VAXstation II/GPX To prepare the hardware: 1. Turn on the 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 ENABLE/DISABLE switch to the halt enabled position. 4. Turn on the 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.V1.3 Performing normal system tests. 7..6..5..4..3.. 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. Booting the System 3-29 _3._1_0._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (VAX) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Type the following command at the console mode prompt: >>> _b _m_u_a_0 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_0._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type the following at the console mode prompt: >>> _b _x_q_a_0 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-30 Booting the System _3._1_1 _V_A_X_s_t_a_t_i_o_n _3_5_2_0 _o_r _V_A_X_s_t_a_t_i_o_n _3_5_4_0 _P_r_o_c_e_s_s_o_r The following instructions assume you have no bootable software on any device in your system. To prepare the VAXstation 3520 or VAXstation 3540 hardware: 1. Set the monitor on/off switch to 1 (on). 2. Set the system unit on/off switch to 1 (on). 3. Turn on the power to the CD-ROM box (if present). 4. Turn on the power to peripheral devices, such as printers and modems. 5. Remove any TK50 tape cartridges and CD-ROM optical discs from their associated drives. After about 20 seconds, the monitor displays a power-up test sequence similar to this: KA60 V1.0 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: CPU1c>>> You are now ready to type the boot command. The boot command you type depends on the software distribution kit: TK50, CD-ROM, or network. The boot command for each distribution kit is described in this section. _3._1_1._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t Follow the instructions included with your TK50 tape kit for inserting the TK50 tape into the tape drive. Booting the System 3-31 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.4 (VAX) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Type the following command at the console mode prompt: >>> _b _m_u_a_0 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_1._2 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _C_D-_R_O_M _O_p_t_i_c_a_l _D_i_s_c _K_i_t If your CD-ROM 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 CD-ROM optical disc with the label ULTRIX/UWS V4.4 (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: >>> _s_h_o_w _s_c_s_i A seven-column table is displayed. This table contains the commands for possible devices from which to boot. 3. Look at column 4, labeled _D_E_V_N_A_M, which contains device names. Find the RRD40 or RRD42 device name in the list. 4. Find the corresponding boot command in column 2, labeled _V_M_B, which contains the virtual memory boot command for each device. 5. Type the appropriate boot command from the list in 3-32 Booting the System column 2, for example: >>> _b _d_k_a_6_0_0 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_1._3 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k To boot the system over the network, type the following command at the console mode prompt: >>> _b _e_s_a_0 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. Booting the System 3-33 _3._1_2 _V_A_X-_1_1/_7_5_0 _P_r_o_c_e_s_s_o_r To prepare the VAX-11/750 hardware: 1. Turn on the 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 1/1 into the console TU58 drive on the front of the processor. 2. Type the following command at the console mode prompt: >>> _b _d_d_a_0 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 1/1. 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 3-34 Booting the System display similar to 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 to 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. More system information appears, followed by a display similar to 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 (VAX) 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 1/1. This media is necessary for booting your system if your configuration requires Booting the System 3-35 access to hardware microcode. You have completed booting your system. Continue the installation procedure with Chapter 4. 3-36 Booting the System _3._1_3 _V_A_X-_1_1/_7_8_0 _o_r _V_A_X-_1_1/_7_8_5 _P_r_o_c_e_s_s_o_r To prepare the VAX-11/780 or VAX-11/785 hardware: 1. Turn on the 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 RX01 console diskette that is in the drive inside the processor. 2. Insert the RX01 diskette labeled ULTRIX V4.2 RX01 BOOT 1/1. The diskette label should point toward the handle of the diskette drive. 3. Type the following at the console mode prompt: >>> _b 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: 4. Remove the RX01 diskette labeled ULTRIX V4.2 RX01 BOOT 1/1. 5. Insert the first standalone system volume, labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #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. . . . . . Booting the System 3-37 Load the RX01 labeled `STANDALONE ULTRIX RX01 #2'. Press the Return key when ready. 6. Remove the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #1, replace it with the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #2, and press Return. A display similar to this appears: . . . Load the RX01 labeled `STANDALONE ULTRIX RX01 #3'. Press the Return key when ready. 7. Remove the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #2, replace it with the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #3, and press Return. The installation software displays the memory and hardware configurations. A display similar to this appears: . . . Load the RX01 labeled `STANDALONE ULTRIX RX01 #4'. Press the Return key when ready. 8. Remove the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #3, replace it with the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #4, and press Return. 9. Remove the RX01 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX01 #4. 10.Reload the RX01 diskette labeled ULTRIX V4.2 RX01 BOOT 1/1. You have completed booting your system. Continue the installation procedure with Chapter 4. 3-38 Booting the System _3._1_4 _V_A_X _6_0_0_0-_n_n_n _S_e_r_i_e_s _o_r _V_A_X_s_e_r_v_e_r _6_0_0_0-_n_n_n _S_e_r_i_e_s _P_r_o_c_e_s_s_o_r This section describes how to boot the following processors: +o VAX 6000-210/220/230/240 +o VAX 6000-310/320/330/340/350/360 +o VAX 6000-410/420/430/440/450/460 +o VAX 6000-510/520/530/540/550/560 Note that VAXserver 6000-nnn processors were formerly known as VAXserver 6210/6220 or VAXserver 6310/6320/6330/6340/6350/6360 processors. To prepare the hardware: 1. Turn on the power to the processor. 2. Turn on the 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 CIBCA-AA 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._1_4._1 _B_o_o_t_i_n_g _f_r_o_m _t_h_e _T_K_5_0 _T_a_p_e _C_a_r_t_r_i_d_g_e _K_i_t 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.4 (VAX) BOOT/UPGRADE into the tape drive. Ensure the tape is on line and ready to use. 3. Type the following command at the console mode Booting the System 3-39 prompt to begin the installation: >>> _b /_r_5:_1_0_0_0_8 _c_s_a_1 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_4._2 _B_o_o_t_i_n_g _f_r_o_m _a _S_y_s_t_e_m _w_i_t_h _a _C_I_B_C_A-_A_A _C_o_n_t_r_o_l_l_e_r 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. Type the following command at the console mode prompt: >>> _b /_r_5:_1_0_0_0_8 _c_s_a_1 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.4 (VAX) BOOT/UPGRADE into the console drive. Ensure the tape is on line and ready to use. Type YES to the prompt. More system information appears, followed by a 3-40 Booting the System 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._1_4._3 _B_o_o_t_i_n_g _f_r_o_m _a _S_y_s_t_e_m _w_i_t_h _a _C_I_B_C_A-_A_B _C_o_n_t_r_o_l_l_e_r 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 cartridge labeled ULTRIX AND UWS V4.4 (VAX) BOOT/UPGRADE into the console drive. Ensure the tape is online and ready to use. 3. Type the following command at the console mode prompt: >>> _b /_r_5:_1_0_0_0_8 _c_s_a_1 You have completed booting your system. Continue the installation procedure with Chapter 4. Booting the System 3-41 _3._1_5 _V_A_X _8_2_0_0/_8_2_5_0 _o_r _V_A_X _8_3_0_0/_8_3_5_0 _P_r_o_c_e_s_s_o_r To prepare the VAX 8200/8250 or VAX 8300/8350 hardware: 1. Turn on the 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 1/1 in the processor's removable drive. Use the left 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 _c_s_a_1 After the boot media has been read, a message similar to the following displays: Please remove the volume "ULTRIX-32" from the console drive. Insert the first standalone system volume and enter "YES" when ready: 3. Remove the RX50 diskette labeled ULTRIX V4.2 (VAX) RX50 BOOT 1/1. 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 3-42 Booting the System 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 (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 1/1. This media is necessary for booting your system if your configuration requires access to hardware microcode. 9. Enter your boot sequence, as displayed for you on the console display. You have completed booting your system. Continue the installation procedure with Chapter 4. Booting the System 3-43 _3._1_6 _V_A_X _8_5_0_0/_8_5_3_0/_8_5_5_0, _V_A_X _8_7_0_0, _o_r _V_A_X _8_8_0_0/_8_8_1_0 _P_r_o_c_e_s_s_o_r To prepare the VAX 8500/8530/8550, VAX 8700, or VAX 8800/8810 hardware: 1. Turn on the power to the processor. 2. Turn on the power to the console subsystem. 3. Initialize the system with the @_s_y_s_i_n_i_t command procedure. 4. Turn on the 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 0. Use the left 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: >>> @_c_n_s_l._c_o_m 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 (VAX) STANDALONE ULTRIX RX50 #2, and press Return. The installation software displays the memory and hardware configurations. 3-44 Booting the System 4. Remove the RX50 diskette labeled ULTRIX V4.3 (VAX) STANDALONE ULTRIX RX50 #2, replace it with the RX50 diskette labeled ULTRIX V4.3 (VAX) 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. Booting the System 3-45 _3._1_7 _V_A_X _8_6_0_0/_8_6_5_0 _P_r_o_c_e_s_s_o_r To prepare the VAX 8600/8650 hardware: 1. Turn on the power to the processor. 2. Set the processor power-on action switch to HALT and the rotary key switch to LOCAL. 3. Turn on the 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: >>> @_c_n_s_l._c_o_m After the boot media has been read, a message similar to the following is displayed: Please remove the volume "8600 console" from the console device. 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 3-46 Booting the System 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-47 _3._1_8 _V_A_X _8_8_2_0/_8_8_3_0/_8_8_4_0 _P_r_o_c_e_s_s_o_r Look in the configuration section of your site management guide for the following numbers for the RA60 installation device: +o VAX Bus Interconnect (VAXBI) number, which is the VAXBI bus to which the controller is connected +o VAXBI node number, which is the node on the VAXBI bus to which the controller is connected +o Disk (dn) number, which is the unit number of the RA60 disk to which the controller is connected +o 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. Turn on the power to the processor. 2. Initialize the system with the @_s_y_s_i_n_i_t command procedure. 3. Turn on the 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 label ULTRIX AND UWS V4.4 (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._1_8._1 _B_o_o_t_i_n_g _S_e_q_u_e_n_c_e _f_o_r _a _S_y_s_t_e_m _D_i_s_k _C_o_n_n_e_c_t_e_d _t_o _a _L_o_c_a_l _C_o_n_t_r_o_l_l_e_r Enter the numbers and the boot command specified in the following order: _d _r_1BI-number BI-node _d _r_3disk-number 3-48 Booting the System @_b_d_a_r_a The following example shows the sequence for BI number 2, BI node 1, and RA60 disk 0: >>> _d _r_1 _2_1 >>> _d _r_3 _0 >>> @_b_d_a_r_a 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._1_8._2 _B_o_o_t_i_n_g _S_e_q_u_e_n_c_e _f_o_r _a _S_y_s_t_e_m _D_i_s_k _C_o_n_n_e_c_t_e_d _t_o _a_n _H_S_C Enter the numbers and the boot command specified in the following order: _d _r_1BI-number BI-node _d _r_2HSC-node-number _d _r_3disk-number @_b_c_a_r_a The following example shows the sequence for BI number 3, BI node 4, HSC node 8, and RA60 disk 2: >>> _d _r_1 _3_4 >>> _d _r_2 _8 >>> _d _r_3 _2 >>> @_b_c_a_r_a 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-49 _3._1_9 _V_A_X _9_0_0_0 _P_r_o_c_e_s_s_o_r To prepare the VAX 9000 hardware, follow these steps: 1. Turn on the 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 TK50 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 TK50 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: >>> _m_o_u_n_t _m_u_a_7: _u_l_t_r_i_x 4. Next, copy the following command to the _u_s_e_r_f_i_l_e_s directory. This command takes approximately 7-10 minutes to complete. >>> _c_o_p_y _m_u_a_7:[]_u_l_t_r_i_x._i_m_a [_u_s_e_r_f_i_l_e_s] 5. Type the following command before removing the TK50 tape: >>> _d_i_s_m_o_u_n_t _m_u_a_7: 6. Remove the TK50 tape from the tape drive. 7. Copy the standalone boot command procedure located in the _u_s_e_r_f_i_l_e_s directory to the ULTRIX boot 3-50 Booting the System command procedure by typing the following command: >>> _c_o_p_y [_u_s_e_r_f_i_l_e_s]_s_a_b_k_u_p_b_o_o._c_m_d [_u_s_e_r_f_i_l_e_s]_u_l_t_r_i_x_b_o_o._c_m_d 8. Next, define _u_l_t_r_i_x._i_m_a as the root image and then identify the disk unit information for your system. To do this, you need to edit the _u_l_t_r_i_x_b_o_o._c_m_d file. To invoke the editor, type the following command: >>> _e_d_i_t [_u_s_e_r_f_i_l_e_s]_u_l_t_r_i_x_b_o_o._c_m_d The screen displays an end-of-buffer message: [EOB] If you have a video display terminal, the _e_d_i_t command invokes a full-screen editor similar to EDT. If you have a hardcopy terminal, it invokes a line editor. _N_o_t_e Online help for full-screen or line editing is available at any time during the editing session. Press the PF2 key or type _h_e_l_p 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: _D_E_F_I_N_E/_S_Y_S_T_E_M _S_Y_S$_R_O_O_T_I_M_A_G_E [_U_S_E_R_F_I_L_E_S]_U_L_T_R_I_X._I_M_A Your file should look similar to the following: !Inputs: ! ! P1 - "TRUE" for /START "FALSE" otherwise . . . ! All other GRPs are clear DEFINE/SYS SYS$ROOTIMAGE [USERFILES]ULTRIX.IMA Move the cursor to the last line in the section containing the DEPOSIT commands. Open up a line Booting the System 3-51 for editing and add the following command: _D_E_P_O_S_I_T _R_5 %_X_8 This entry tells the system that the _D_E_P_O_S_I_T command for register 5 is %X8. Your file should look similar to the following: EXAMINE/SYMBOL=START_ADDRESS PC !Get the start address . . . DEPOSIT R0 %X40 ! Set device type (CONSOLE) DEPOSIT R3 1 ! Set the disk unit number DEPOSIT R5 %X8 ! required mode for ULTRIX To end the editing session, press Ctrl/Z. The system will display an asterisk (*). Type _e_x_i_t. The installation procedure returns you to the system prompt. 9. To initialize the hardware, type the following command: >>> _i/_k 10.To boot the ULTRIX software, type the following command. This will take several minutes to complete. >>> _b _u_l_t_r_i_x You have completed booting your system. Continue the installation procedure with Chapter 4. 3-52 Booting the System Performing the Installation 4 This chapter describes how to perform the basic and advanced installations. You must perform an installation in these situations: +o When you have never installed ULTRIX or ULTRIX Worksystem Software systems. +o When you have the ULTRIX or ULTRIX Worksystem Software installed, but the product version is not Version 4.2 or higher. _N_o_t_e 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: +o You can select the default disk partitions, the default file system layout, and a choice of optional subsets. +o You can select customized disk partitions, a customized file system layout, and a choice of optional subsets. There are some postinstallation 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. Example D-1 is an example of an advanced installation. If you want to abort an installation at any time, enter _C_t_r_l/_c. The installation procedure will stop. You will need to restart the installation procedure from the beginning. _4._1 _C_h_o_o_s_i_n_g _t_h_e _T_y_p_e _o_f _I_n_s_t_a_l_l_a_t_i_o_n 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. _N_o_t_e Advanced installations are required for VAXstation 3520 and 3540 systems. 4-2 Performing the Installation _4._2 _S_e_l_e_c_t_i_n_g _t_h_e _S_o_f_t_w_a_r_e _D_i_s_t_r_i_b_u_t_i_o_n _D_e_v_i_c_e This section applies only if your system uses console boot media. The following processors use console boot media: +o VAX-11/750 +o VAX-11/780 +o VAX-11/785 +o VAX 8200/8250 +o VAX 8300/8350 +o VAX 86XX +o VAX 85XX +o VAX 87XX +o 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. ULTRIX Name 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. 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 Performing the Installation 4-3 with the same device number. For example, a VAX-11/785 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 Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RA60 ra2 2 KDB50 4 2 TU81 tms0 0 TU81 20 ---------------------------------------------------------------------- To select the software distribution device, follow these steps: 1. Type the selection number corresponding to the device you want. 2. Load the Boot/Upgrade 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 _S_e_l_e_c_t_i_n_g _t_h_e _D_i_s_k _f_o_r _t_h_e _r_o_o_t _P_a_r_t_i_t_i_o_n 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. 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. 4-4 Performing the Installation 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 swap1 space. The system displays a table similar to the one shown in the following example of a DECstation 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 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 ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 1 ---------------------------------------------------------------------- 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 Performing the Installation 4-5 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? (y/n) []: _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 ) Default partition table 2 ) 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. _N_o_t_e 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-6 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 _R_e_b_o_o_t_i_n_g _t_h_e _S_y_s_t_e_m 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/vmunix -a" >> boot For example, at the prompt for the DECsystem 5000, enter: >> _s_e_t_e_n_v _b_o_o_t "_2/_r_z_5/_v_m_u_n_i_x -_a" >> _b_o_o_t Performing the Installation 4-7 _4._5 _S_p_e_c_i_f_y_i_n_g _S_y_s_t_e_m _I_n_f_o_r_m_a_t_i_o_n 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: +o 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. +o The date and time +o Your time zone +o Whether your area alternates between daylight savings and standard time +o Your geographic area +o 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: _f_a_R!_K_l_e Verify: _f_a_R!_K_l_e 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 4-8 Performing the Installation Section 4.6. _4._6 _A_l_l_o_c_a_t_i_n_g _F_i_l_e _S_y_s_t_e_m_s 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: +o The root file system +o The /_u_s_r file system +o The swap1 space +o 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 bottom top size overlap default a 0 32767 32768 c root b 32768 163839 131072 c swap, dump g 163840 731505 567666 c,d,e /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 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 Performing the Installation 4-9 4.7. If you enter _n at the prompt, continue with Section 4.6.1. _4._6._1 _A_l_l_o_c_a_t_i_n_g _t_h_e /_u_s_r _F_i_l_e _S_y_s_t_e_m 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 DECstation 5000. This table lists the disks connected to your processor. Select the disk on which you want to allocate the /_u_s_r 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 Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 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/n) []: _y After you enter your confirmation, a message is displayed indicating: +o The partitions available on the disk you selected +o The size in kB of each available partition +o Other partitions over which each available partition extends 4-10 Performing the Installation The system instructs you to enter the letter of the partition on which you want to allocate the /_u_s_r file system. Refer to the /_u_s_r 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 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) overlap ------------------------------------------------ d --- 146265 c,g e --- 146265 c,g,h f --- 275137 c,h g --- 283833 c,d,e h --- 283834 c,e,f ------------------------------------------------ Type the letter of the partition on which you want to allocate the /usr file system [no default]: _g Making the new file system for /usr on /dev/rrz13g RZ56 _4._6._2 _A_l_l_o_c_a_t_i_n_g _t_h_e _s_w_a_p_1 _S_p_a_c_e 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 swap1 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 ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 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 swap1 space? (y/n) []: _y After you enter your confirmation, a message is displayed indicating: +o The partitions available on the disk you selected +o The size in kB of each available partition +o Other partitions over which each available partition extends Refer to the file system worksheet in Table 2-6 for the disk name and partition. _N_o_t_e 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 --- 65536 c f --- 275137 c,h h --- 283834 c,e,f ------------------------------------------------ 4-12 Performing the Installation Type the letter of the partition on which you want to allocate the swap1 space [b]: _b _N_o_t_e If you want to upgrade the system in future releases, you must allocate the swap1 space on partition _b of the system disk. _4._6._3 _A_l_l_o_c_a_t_i_n_g _t_h_e _s_w_a_p_2 _S_p_a_c_e 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 _n, 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? (y/n) [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 Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 1 ---------------------------------------------------------------------- Enter your choice: _1 Performing the Installation 4-13 You selected RZ55, device number 0. Make sure this disk is on line and write-enabled (if applicable to this drive) and then confirm your choice. Use RZ55, rz0 for swap2 space? (y/n) []: _y After you enter your confirmation, a message is displayed indicating: +o The partitions available on the disk you selected +o The size in kB of each available partition +o 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 rz0 you selected from the previous table has the following partitions available, on which you can allocate the swap2 space: partition size (Kbytes) overlap ------------------------------------------------ b --- 73728 c c --- 324520 a,b,d,e,f,g,h d --- 40960 c,g e --- 40960 c,g f --- 122880 c,g g --- 234408 c,d,e,f,h h --- 29608 c,g ------------------------------------------------ Type the letter of the partition on which you want to allocate the swap2 space [no default]: _b _4._6._4 _A_l_l_o_c_a_t_i_n_g _t_h_e _C_r_a_s_h _D_u_m_p _S_p_a_c_e 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 4-14 Performing the Installation table below. See the Guide to Installing ULTRIX for an explanation of this table: CRASH DUMP SPACE ALLOCATION TABLE Selection Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 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? (y/n) []: _y After you enter your confirmation, a message is displayed indicating: +o The partitions available on the disk you selected +o The size in kB of each available partition +o 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 swap1 or swap2. Refer to the file system worksheet in Table 2-6 for the disk name. _N_o_t_e The crash dump space must be on a disk connected to the same controller as the system disk. Performing the Installation 4-15 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 --- 275137 c,h h --- 283834 c,e,f b --- 65536 c ------------------------------------------------ Type the letter of the partition on which you want to allocate the crash dump space [b]: _b _4._6._5 _A_l_l_o_c_a_t_i_n_g _t_h_e _v_a_r _A_r_e_a 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 _v_a_r 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 ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ55 rz0 0 SCSI 0 2 RZ56 rz1 1 SCSI 0 3 RZ56 rz13 5 SCSI 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. 4-16 Performing the Installation Use RZ56, rz13 for var file system? (y/n) []: _y After you enter your confirmation, a message is displayed indicating: +o The partitions available on the disk you selected +o The size in kB of each available partition +o 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 _v_a_r area. You can allocate the _v_a_r area either to a separate partition as a file system, or as a directory under the /_u_s_r file system. If you want to allocate the _v_a_r area to the /_u_s_r 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 --- 275137 c,h h --- 283834 c,e,f g --- 283833 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 /dev/rrz13h RZ56 Continue with Section 4.7. _4._7 _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _W_o_r_k_s_y_s_t_e_m _S_o_f_t_w_a_r_e 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 Performing the Installation 4-17 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? y/n []: 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. Type the selection number at the prompt. 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: After you enter your choice, continue with Section 4.8. _4._8 _L_o_a_d_i_n_g _t_h_e _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s 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 CD-ROM, 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 _I_n_s_t_a_l_l_i_n_g _f_r_o_m _T_K_5_0 _o_r _M_T_9 _T_a_p_e 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 4-18 Performing the Installation 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.4 BOOT/UPGRADE and replace it with the tape marked ULTRIX AND UWS V4.4 SUPPORTED SOFTWARE Volume 1. _N_o_t_e The tape marked ULTRIX AND UWS V4.4 BOOT/UPGRADE 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. _4._8._2 _I_n_s_t_a_l_l_i_n_g _f_r_o_m _a _C_D-_R_O_M If you are installing from a CD-ROM, 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 _L_o_a_d_i_n_g _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s _f_o_r _t_h_e _B_a_s_i_c _I_n_s_t_a_l_l_a_t_i_o_n When you choose the basic installation, the system Performing the Installation 4-19 first displays the following request: *** Select the DECwindows User Interface *** 1) DECwindows for OSF/Motif 2) X11/DECwindows (XUI) Enter your choice [1]: After you make your choice, the system loads the software subsets and displays copying, working, and verifying messages. For example: Base System (UDTBASE440) Copying from /dev/nrmt0h (tape) Working....Tue May 10 17:38:02 EDT 1994 . . . Verifying Working....Tue May 10 17:42:22 EDT 1994 . . . 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... Working...Tue May 10 17:01:00 GMT 1994 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-20 Performing the Installation _4._8._4 _L_o_a_d_i_n_g _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s _f_o_r _t_h_e _A_d_v_a_n_c_e_d _I_n_s_t_a_l_l_a_t_i_o_n When you choose the advanced installation, the system first displays the following request: *** Select the DECwindows User Interface *** 1) DECwindows for OSF/Motif 2) X11/DECwindows (XUI) Enter your choice [1]: After you make your choice, 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 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: . . . Performing the Installation 4-21 Is this correct? (y/n): _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 (UDTBASE440) Copying from /dev/nrmt0h (tape) Working....Tue May 10 17:38:02 EDT 1994 . . . Verifying Working....Tue May 10 17:42:22 EDT 1994 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... Working...Tue May 10 17:01:00 GMT 1994 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. _N_o_t_e For VAXstation 3520 and 3540 systems, you must choose the VS35XX X11/DECwindows 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 4-22 Performing the Installation 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 _L_o_a_d_i_n_g _t_h_e _S_o_f_t_w_a_r_e _S_u_b_s_e_t _U_p_g_r_a_d_e_s This release of ULTRIX and UWS contains software subset upgrades. How you install these subsets depends on your distribution media. If you are installing from TK50 or MT9 tape, continue with Section 4.9.1. If you are installing from CD-ROM, continue with Section 4.9.2. If you are installing from the network, continue with Section 4.10. _4._9._1 _L_o_a_d_i_n_g _U_p_g_r_a_d_e_s _f_r_o_m _T_K_5_0 _o_r _M_T_9 _T_a_p_e If you are installing from a TK50 tape, the system asks you to remove the tape labeled ULTRIX AND UWS V4.4 SUPPORTED SOFTWARE and replace it with the tape labeled ULTRIX AND UWS V4.4 BOOT/UPGRADE. 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. _N_o_t_e The tape labeled ULTRIX AND UWS V4.4 BOOT/UPGRADE 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 Performing the Installation 4-23 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. 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. _N_o_t_e 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 4-24 Performing the Installation 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 _L_o_a_d_i_n_g _U_p_g_r_a_d_e_s _f_r_o_m _C_D-_R_O_M If you are installing from CD-ROM 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. 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. Performing the Installation 4-25 _N_o_t_e 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._1_0 _S_p_e_c_i_f_y_i_n_g _K_e_r_n_e_l _O_p_t_i_o_n_s _f_o_r _t_h_e _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e 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 Kernel Option --------------------------------------------------------------- 1 Local Area Transport (LAT) 2 Bisynchronous Communication protocol (VAX only) 3 Computer Interconnect (CI) network 4 Diagnostic/Utilities Protocol (DUP) 5 ISO9660 File System Support (CDFS) 4-26 Performing the Installation 6 Ethernet Packet Filter 7 Enhanced Security Features 8 All of the above 9 None of the above ---------------------------------------------------------------- Enter the selection number for each kernel option you want. For example, 1 3 : _1 _3 _5 _7 You specified the following kernel options: Local Area Transport (LAT) Computer Interconnect (CI) network ISO9660 File System Support (CDFS) Enhanced Security Features 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? (y/n) [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 on uba0 at 160354 dz0 on uba0 at 160100 dz1 on uba0 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 Performing the Installation 4-27 configuration file and how to use the _e_d editor. (For more information on editing your system's configuration file, see the _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e.) Do you want to edit the configuration file? (y/n) [n]: If you answer _n, the installation procedure continues by performing the system's configuration. You will need to edit the configuration file in the following situations: +o 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. +o 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 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: uq0, uq17, and uq18, of which uq17 and uq18 are in the floating address space, and each controller has one drive attached to it, unit numbers 0, 1, and 3, respectively. The 4-28 Performing the Installation software places the following information in the configuration file: controller uda0 at uba0 controller uq0 at uda0 csr 0172150 vector uqintr disk ra0 at uq0 drive 0 controller uda1 at uba0 controller uq17 at uda1 csr 0160334 vector uqintr controller uda2 at uba0 controller uq18 at uda2 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 uda0 at uba0 controller uq0 at uda0 csr 0172150 vector uqintr disk ra0 at uq0 drive 0 controller uda1 at uba0 controller uq17 at uda1 csr 0160334 vector uqintr disk ra1 at uq17 drive 1 controller uda2 at uba0 controller uq18 at uda2 csr 0160340 vector uqintr disk ra2 at uq18 drive 3 +o You have multiple MSCP controllers on the Q-bus. If your system has controllers 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. _N_o_t_e 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 Performing the Installation 4-29 according to processor. _4._1_1 _C_o_n_s_o_l_e _B_o_o_t _D_e_f_a_u_l_t_s _a_n_d _C_o_n_s_o_l_e _M_e_d_i_a 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._1_1._1 _U_p_d_a_t_i_n_g _t_h_e _C_o_n_s_o_l_e _B_o_o_t _D_e_f_a_u_l_t If you have one of the following processors, the next step in the installation procedure is to update the console boot defaults: +o MicroVAX 3100 +o MicroVAX 3500 +o MicroVAX 3300/3400 +o VAXserver 3300/3400 +o 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 _G_u_i_d_e _t_o _S_y_s_t_e_m _S_h_u_t_d_o_w_n _a_n_d _S_t_a_r_t_u_p for more information. Continue the installation procedure with Section 4.12. _4._1_1._2 _U_p_d_a_t_i_n_g _t_h_e _C_o_n_s_o_l_e _M_e_d_i_a If you have one of the following processors with the system disk connected to a Hierarchical Storage Controller (HSC), the next step in the installation procedure is to update the console media: +o VAX-11/750 +o VAX-11/780 +o VAX-11/785 +o VAX 8600/8650 +o VAX 8200/8250 +o VAX 8300/8350 4-30 Performing the Installation 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. . . . 6. What you do next depends on which processor you have. - For a VAX-11/750, remove the TU58 tape cassette from the drive and write-lock 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 1/1, an equivalent tape, or a customized tape built for a CI/HSC system disk should remain in its drive at all times. This Performing the Installation 4-31 is necessary to load required CI microcode. - For a VAX-11/780 or VAX-11/785, 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 VAX 8200/8250/8300/8350, if your system includes a Computer Interconnect (CI), the distributed console diskette labeled ULTRIX V4.2 BOOT 1/1, an equivalent diskette, or a customized diskette built for a CI/HSC 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._1_2 _C_o_m_p_l_e_t_i_n_g _t_h_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _R_e_b_o_o_t_i_n_g _t_h_e _S_y_s_t_e_m Depending on your processor type and system disk, the software either reboots the system automatically or displays instructions on how to reboot your system. _N_o_t_e 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 - customized kernel /genvmunix - generic kernel /usr/adm/install.log - installation log file /usr/adm/install.FS.log - file systems log file 4-32 Performing the Installation /usr/adm/install.DEV.log - 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 example: . . . Ultrixboot - V4.4 Fri Jun 10 06:15:25 EDT 1994 . . . ULTRIX V4.4 System #1: Fri Jun 10 04 06:18:28 EDT 1994 . . . ULTRIX V4.4 (mysystem) login: If you are installing to a workstation, a Start Session dialog box is displayed indicating that your ULTRIX Worksystem 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 _r_o_o_t at the login prompt and the superuser password specified earlier in the installation at the password prompt. See the _D_E_C_w_i_n_d_o_w_s _U_s_e_r'_s _G_u_i_d_e for information about how to use ULTRIX Worksystem Software, including how to log in and use the Session Manager. _4._1_3 _P_o_s_t_i_n_s_t_a_l_l_a_t_i_o_n _P_r_o_c_e_d_u_r_e_s A message referring to the locations of /_v_m_u_n_i_x, /_g_e_n_v_m_u_n_i_x, and the log files is included in the message-of-the-day file, /_e_t_c/_m_o_t_d, and will appear each time you log in to your system. If you want, you can delete these references from your /_e_t_c/_m_o_t_d file. See the _G_u_i_d_e _t_o _S_y_s_t_e_m _a_n_d _N_e_t_w_o_r_k _S_e_t_u_p for information about the /_e_t_c/_m_o_t_d file. Print out the _l_o_g files generated in /_u_s_r/_a_d_m during your installation. You may need information from these files for system maintenance. Each system has a two-user 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 _G_u_i_d_e _t_o _S_o_f_t_w_a_r_e _L_i_c_e_n_s_i_n_g for information about registering PAKs. Performing the Installation 4-33 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 _G_u_i_d_e _t_o _S_y_s_t_e_m _a_n_d _N_e_t_w_o_r_k _S_e_t_u_p for more information about the tasks you will need to complete after the installation to establish your system's environment. See the _S_e_c_u_r_i_t_y _G_u_i_d_e _f_o_r _A_d_m_i_n_i_s_t_r_a_t_o_r_s for instructions on how to set up your system for enhanced security. _N_o_t_e 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 _G_u_i_d_e _t_o _S_y_s_t_e_m _a_n_d _N_e_t_w_o_r_k _S_e_t_u_p for more information. Table 4-1: _P_o_s_t_i_n_s_t_a_l_l_a_t_i_o_n _T_a_s_k_s _______________________________________________________________ Task Utility _______________________________________________________________ Using the License Management Facility lmf(8) Setting up the License Management Facility lmfsetup(8) Adding users and setting up a users' file area adduser(8) Adding devices MAKEDEV(8) Setting up printers* lprsetup(8) Setting up a local area network netsetup(8) Setting up a Network File System nfssetup(8) Setting up _u_u_c_p* _u_u_c_p_s_e_t_u_p(8) Setting up the Yellow Pages service ypsetup(8) Setting up the BIND/HESIOD 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 4-34 Performing the Installation installation you will not be able to set up your printer unless you install the optional subsets. Use the _s_e_t_l_d utility to load the unsupported software subsets and to add and delete software subsets. Proper use of _s_e_t_l_d will help you manage disk space. For further information about the _s_e_t_l_d(8) utility see the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. Performing the Installation 4-35 Performing an Upgrade 5 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.4 system by following the instructions in this chapter. When you upgrade an existing system, you do not have to perform a complete installation. When you use this upgrade procedure, the ULTRIX system that existed on your previous system is upgraded, with the following exceptions: +o The UWS DECwindows user environment on your system The UWS DECwindows User Environment that existed on your previous system is not automatically upgraded. During the upgrade procedure you must choose which UWS DECwindows User Environment you want your upgraded system to employ, either the DECwindows for OSF/Motif interface, or the X11/DECwindows (XUI) interface. Thus, you can choose to upgrade to a newer version of your current DECwindows User Interface, or you can switch from one interface style to another through the upgrade procedure. +o The unsupported subsets on your system The upgrade procedure does not upgrade any unsupported subsets. If your system has unsupported subsets installed on it, you must remove them before performing the upgrade procedure. There are two reasons why you should do this. First, the contents of the subsets may change over time, so that newer versions of the subsets may contain corrected or different software. Second, the files from earlier, unsupported subsets, if not deleted remain on your system wasting disk space. Use the _s_e_t_l_d -_d command to remove unsupported subsets after you have backed up your current system and before you begin the upgrade procedure. Before you begin the upgrade procedure, be sure to review the _U_L_T_R_I_X _a_n_d _U_W_S _R_e_l_e_a_s_e _N_o_t_e_s and the _U_L_T_R_I_X _a_n_d _U_W_S _S_y_s_t_e_m _N_o_t_e_s for information about the upgrade procedures and about layered products. _N_o_t_e You cannot use this upgrade procedure on any system running ULTRIX or ULTRIX Worksystem 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: +o If you are upgrading a local system from TK50 or MT9 tapes, from CD-ROM, or from the network as a client of a Remote Installation Services (RIS) server, go to Section 5.1. +o If you are upgrading a new or existing RIS area on a server, go to Section 5.2. +o If you are upgrading a new or existing Diskless Management System (DMS) area on a server, go to Section 5.3. _N_o_t_e 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. 5-2 Performing an Upgrade _5._1 _U_p_g_r_a_d_i_n_g _a _L_o_c_a_l _S_y_s_t_e_m Depending on the load device of your processor, use one of the following distribution devices to load the software: +o TK50 cartridge tape +o 9-track magnetic tape +o CD-ROM +o Network (from a RIS server) The upgrade procedure makes use of the _s_e_t_l_d 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 _S_t_a_r_t_i_n_g _t_h_e _U_p_g_r_a_d_e To start the upgrade, follow these steps: 1. Log in to your system as _r_o_o_t. 2. Bring your system down to single-user mode. Your system must be in single-user mode to perform the upgrade procedure. The following command brings the system down to single-user mode after a delay of five minutes: # /_e_t_c/_s_h_u_t_d_o_w_n +_5 "_U_p_g_r_a_d_i_n_g _t_o _U_L_T_R_I_X _V_4._4" For more information on shutting down your system, see the _G_u_i_d_e _t_o _S_y_s_t_e_m _S_h_u_t_d_o_w_n _a_n_d _S_t_a_r_t_u_p and the _s_h_u_t_d_o_w_n(8) reference page. 3. Unmount all file systems and remount all ULTRIX file systems by entering the following commands: # /_e_t_c/_u_m_o_u_n_t -_a -_f # /_e_t_c/_m_o_u_n_t -_a -_t _u_f_s 4. Run the /_e_t_c/_u_p_d_a_t_e program to start the daemon that will keep your file system consistent. Enter Performing an Upgrade 5-3 the following command: # /_e_t_c/_u_p_d_a_t_e Refer to _u_p_d_a_t_e(8) for more information. _N_o_t_e If you are keeping a script for the session, this is a good place to start the script. Continue with the section that describes the upgrade for the distribution media you are using: +o Section 5.1.2, for upgrading from a TK50 or MT9 +o Section 5.1.3, for upgrading from a CD-ROM +o Section 5.1.4, for upgrading from the network _5._1._2 _U_p_g_r_a_d_i_n_g _f_r_o_m _a _T_K_5_0 _o_r _M_T_9 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: # /_e_t_c/_s_e_t_l_d -_l /_d_e_v/_n_r_m_t_N_h 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 (y/n) ? When you have determined that the tape is mounted and on line, answer _y to the prompt. Go to Section 5.1.5. 5-4 Performing an Upgrade _5._1._3 _U_p_g_r_a_d_i_n_g _f_r_o_m _a _C_D-_R_O_M If you are upgrading from a CD-ROM, follow these steps: 1. Load the CD-ROM onto your system's distribution device. 2. Enter the following command: replace _N with the logical unit number of the device you are using: # /_e_t_c/_m_o_u_n_t -_r /_d_e_v/_r_z_N_c /_m_n_t 3. If your system is a RISC machine, enter the following command: # /_e_t_c/_s_e_t_l_d -_l /_m_n_t/_R_I_S_C/_B_A_S_E If your system is a VAX machine, enter the following command: # /_e_t_c/_s_e_t_l_d -_l /_m_n_t/_V_A_X/_B_A_S_E Go to Section 5.1.5. _5._1._4 _U_p_g_r_a_d_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k If your system is a registered client and you are upgrading from the network, enter the following command: replace _s_e_r_v_e_r: with the name of your RIS server, followed by a colon: # /_e_t_c/_s_e_t_l_d -_l _s_e_r_v_e_r: Refer to Section 5.2 for information about setting up a RIS server. Continue with Section 5.1.5. _5._1._5 _L_o_a_d_i_n_g _t_h_e _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s If you are upgrading from tape, the procedure displays a _P_o_s_i_t_i_o_n_i_n_g _T_a_p_e message. Then, the procedure displays the following request: *** Select the DECwindows User Interface *** 1) DECwindows for OSF/Motif 2) X11/DECwindows (XUI) Performing an Upgrade 5-5 Enter your choice [1]: After you have made your choice, the procedure begins to extract the subsets from the distribution media. If you are upgrading from CD-ROM or the network, the procedure does not display a positioning tape message before it asks you to select the DECwindows user interface. 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 want 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. 5-6 Performing an Upgrade _N_o_t_e 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 UDTACCT440, be sure to also install the corresponding update subset UDTACCT441. _5._1._6 _L_o_a_d_i_n_g _t_h_e _S_o_f_t_w_a_r_e _S_u_b_s_e_t _U_p_d_a_t_e_s 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, CD-ROM, or the network. _5._1._6._1 _U_p_d_a_t_i_n_g _f_r_o_m _a _T_K_5_0 _o_r _M_T_9 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 BOOT/UPGRADE onto your system's software distribution device. 2. Enter the following command, replacing _N with the actual logical unit number of the device you are using: # /_e_t_c/_s_e_t_l_d -_l /_d_e_v/_n_r_m_t_N_h 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 (y/n) ? 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 Performing an Upgrade 5-7 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 _U_p_d_a_t_i_n_g _f_r_o_m _C_D-_R_O_M If your distribution media is CD-ROM, follow these instructions to load the software subset updates. If your system is a RISC machine, enter the following command: # /_e_t_c/_s_e_t_l_d -_l /_m_n_t/_R_I_S_C/_B_A_S_E__U_P_G_R_A_D_E If your system is a VAX machine, enter the following command: # /_e_t_c/_s_e_t_l_d -_l /_m_n_t/_V_A_X/_B_A_S_E__U_P_G_R_A_D_E The subsets are loaded. After the subsets are loaded, unmount the disk by entering the following command: # /_e_t_c/_u_m_o_u_n_t /_m_n_t 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 _U_p_d_a_t_i_n_g _f_r_o_m _t_h_e _N_e_t_w_o_r_k 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 5-8 Performing an Upgrade kernel is not available. _5._1._7 _R_e_b_u_i_l_d_i_n_g _a _K_e_r_n_e_l _w_h_e_n _t_h_e _R_e_q_u_i_r_e_d _K_e_r_n_e_l _I_s _A_v_a_i_l_a_b_l_e To rebuild a kernel on a system when the required kernel is available, take the following steps: 1. Use the _d_o_c_o_n_f_i_g command with the -_c option to rebuild your kernel. Replace _H_O_S_T_N_A_M_E in the following command with the name of your system typed in all capital letters: # /_e_t_c/_d_o_c_o_n_f_i_g -_c _H_O_S_T_N_A_M_E The -_c option specifies that the new kernel be built using the configuration file that already exists in the /_s_y_s/_c_o_n_f/_v_a_x directory for VAX processors or the /_s_y_s/_c_o_n_f/_m_i_p_s directory for RISC processors. 2. Note that the doconfig command allows you to edit the configuration file. For more information about editing the system configuration file, see the _G_u_i_d_e _t_o _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _M_a_i_n_t_e_n_a_n_c_e. The following prompt appears immediately after you invoke the _d_o_c_o_n_f_i_g 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 _n_o at this prompt. The _d_o_c_o_n_f_i_g program then displays the following message as it begins to rebuild your kernel: *** PERFORMING SYSTEM CONFIGURATION *** When the _d_o_c_o_n_f_i_g command finishes executing, it reports the location of a newly built VAX kernel as follows: The new kernel is /sys/VAX/_H_O_S_T_N_A_M_E/vmunix It reports the location of a newly built RISC Performing an Upgrade 5-9 kernel as follows: The new kernel is /sys/MIPS/_H_O_S_T_N_A_M_E/vmunix When the _d_o_c_o_n_f_i_g program completes, it returns you to the superuser prompt. 3. Copy the new VAX kernel to _r_o_o_t by entering the following command: # _m_v /_s_y_s/_V_A_X/_H_O_S_T_N_A_M_E/_v_m_u_n_i_x /_v_m_u_n_i_x Or, copy the new RISC kernel to _r_o_o_t by entering the following command: # _m_v /_s_y_s/_M_I_P_S/_H_O_S_T_N_A_M_E/_v_m_u_n_i_x /_v_m_u_n_i_x 4. The generic kernel, /_g_e_n_v_m_u_n_i_x was loaded from the software distribution during the upgrade. Now, copy it to _r_o_o_t by entering the following command: # _c_p /_u_s_r/_g_e_n_v_m_u_n_i_x /_g_e_n_v_m_u_n_i_x _N_o_t_e If you are keeping a script of the session, end it now by entering Ctrl/D. 5. To complete the upgrade and activate the new kernel, reboot the system by entering the following command: # /_e_t_c/_r_e_b_o_o_t When the _r_e_b_o_o_t command returns you to the login prompt, the upgrade is complete. _5._1._8 _R_e_b_u_i_l_d_i_n_g _a _K_e_r_n_e_l _w_h_e_n _t_h_e _R_e_q_u_i_r_e_d _K_e_r_n_e_l _I_s _N_o_t _A_v_a_i_l_a_b_l_e To rebuild a kernel on a system when the required kernel is not available, take the following steps: 1. Copy _g_e_n_v_m_u_n_i_x to _v_m_u_n_i_x by entering the following 5-10 Performing an Upgrade command: # _c_p /_u_s_r/_g_e_n_v_m_u_n_i_x /_v_m_u_n_i_x _N_o_t_e If you are keeping a script of the session, end it now by entering Ctrl/D. 2. Unmount all file systems and reboot your system by entering the following commands: # /_e_t_c/_u_m_o_u_n_t -_a # /_e_t_c/_r_e_b_o_o_t 3. When your system comes up to multiuser mode, log in as _r_o_o_t and bring your system to single-user mode by entering the following command: # /_e_t_c/_s_h_u_t_d_o_w_n _n_o_w "_s_w_i_t_c_h_i_n_g _t_o _s_i_n_g_l_e-_u_s_e_r" 4. Unmount all file systems and remount all UFS file systems by entering the following command: # /_e_t_c/_u_m_o_u_n_t -_a -_f # /_e_t_c/_m_o_u_n_t -_a -_t _u_f_s 5. If you have customized your system's configuration file, enter the following command to make a copy of your system's configuration file: # _c_p /_s_y_s/_c_o_n_f/_m_i_p_s/_H_O_S_T_N_A_M_E /_s_y_s/_c_o_n_f/_m_i_p_s/_H_O_S_T_N_A_M_E._V_4._3_A Replace the _H_O_S_T_N_A_M_E in the example with the name of your system. _N_o_t_e 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 _d_o_c_o_n_f_i_g program is running, enter _y_e_s when you are asked if you want to edit the newly created Performing an Upgrade 5-11 configuration file. The _d_o_c_o_n_f_i_g program places you in the _e_d editor and you can add the necessary customizations. - During step 8, as the _d_o_c_o_n_f_i_g program is running, enter _n_o when you are asked if you want to edit the newly created configuration file. After the _d_o_c_o_n_f_i_g 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 _d_o_c_o_n_f_i_g -_c command. For more information on using the _d_o_c_o_n_f_i_g command with the -_c option, see the _d_o_c_o_n_f_i_g(8) reference page. 6. Invoke the _d_o_c_o_n_f_i_g command with no options, as follows: # _d_o_c_o_n_f_i_g While the system is running with a generic kernel, the _d_o_c_o_n_f_i_g 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 _d_o_c_o_n_f_i_g 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 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]: _y The program next asks you for the date and time and the time zone for your system. 8. The _d_o_c_o_n_f_i_g program then asks you if you want to edit the configuration file. Enter _n_o 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 _d_o_c_o_n_f_i_g program will place you into an editing session. After you exit from the editing session, the _d_o_c_o_n_f_i_g program resumes. 5-12 Performing an Upgrade 9. When the _d_o_c_o_n_f_i_g 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 /_d_e_v directory. For example, building on a system named _S_A_M_S_A: *** PERFORMING SYSTEM CONFIGURATION *** working ..... Mon Jun 10 09:11:45 EDT 1993 working ..... Mon Jun 10 09:13:45 EDT 1993 working ..... Mon Jun 10 09:15:46 EDT 1993 *** DEVICE SPECIAL FILE CREATION *** working ..... Mon Jun 10 09:16:35 EDT 1993 A log file listing Special Device Files is located in /dev/MAKEDEV.log The new kernel is /sys/MIPS/SAMSA/vmunix 10.Move /_v_m_u_n_i_x to /_g_e_n_v_m_u_n_i_x by entering the following command: # _m_v /_v_m_u_n_i_x /_g_e_n_v_m_u_n_i_x 11.Copy the new kernel created by the _d_o_c_o_n_f_i_g program to the _r_o_o_t partition. For example: # _c_p /_s_y_s/_M_I_P_S/_S_A_M_S_A/_v_m_u_n_i_x /_v_m_u_n_i_x _N_o_t_e If you are running BIND/Hesiod, edit the /_e_t_c/_r_c._l_o_c_a_l file and add the BIND extension to the _h_o_s_t_n_a_m_e entry, because _d_o_c_o_n_f_i_g overwrites the existing _h_o_s_t_n_a_m_e 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 /_e_t_c/_t_t_y_s file. Enter the following command: # /_e_t_c/_s_e_r_v_e_r__s_c_p_s 13.Reboot your system to bring in the new kernel by Performing an Upgrade 5-13 entering the following command: # /_e_t_c/_r_e_b_o_o_t When the _r_e_b_o_o_t command returns you to the login prompt, the upgrade procedure is complete. _5._2 _U_p_g_r_a_d_i_n_g _a _R_e_m_o_t_e _I_n_s_t_a_l_l_a_t_i_o_n _S_e_r_v_i_c_e_s _A_r_e_a 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 _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k. You can upgrade an existing RIS area only on Version 4.3 or higher servers. To upgrade a RIS area, follow these steps: 1. Log in to the server system as _r_o_o_t. 2. Run the /_e_t_c/_r_i_s 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 RISC) from the menu. 5. If your current system is Version 4.2A or higher, delete the current ULTRIX Supported Product and ULTRIX BOOT/UPGRADE 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.4 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 _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k for these instructions. You are required to repeat this step twice. First, to install the Supported volumes, then to install the Boot/Upgrade volume. 5-14 Performing an Upgrade The procedure is complete when the the /_e_t_c/_r_i_s 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 modifying each client. 8. When the RIS main menu reappears, choose the exit option to return to the superuser prompt. _5._3 _U_p_g_r_a_d_i_n_g _a _D_i_s_k_l_e_s_s _M_a_n_a_g_e_m_e_n_t _S_y_s_t_e_m _A_r_e_a 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. If your server supports multiple diskless areas, you must repeat the upgrade process for each area. _N_o_t_e 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 CD-ROM, use the _m_o_u_n_t command as follows; replace _N with the logical unit number of the device you are using: # /_e_t_c/_m_o_u_n_t -_r /_d_e_v/_r_z_N_c /_m_n_t Performing an Upgrade 5-15 4. Invoke the _d_m_s utility: # /_e_t_c/_d_m_s 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 CD-ROM. 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 with the logical unit number of the device you are using: /_d_e_v/_r_m_t_N_h Make sure that the installed media is write- protected. _N_o_t_e 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 CD-ROM to an area 5-16 Performing an Upgrade serving RISC clients, enter the following command: /_m_n_t/_R_I_S_C/_B_A_S_E If you are installing from CD-ROM to an area serving VAX clients, enter the following command: /_m_n_t/_V_A_X/_B_A_S_E 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? (y/n): 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. 10.Next, the procedure displays the following request: *** Select the DECwindows User Interface *** 1) DECwindows for OSF/Motif 2) X11/DECwindows (XUI) Enter your choice [1]: After you make your choice, the system lists mandatory and optional subsets from the Supported media and installs them. The system copies and verifies each subset you selected. 11.If your installation media is TK50 or MT9, remove the Supported tape from the drive and load the Boot/Upgrade tape in the drive. 12.Choose the Install Software option from the Diskless Management Services menu. 13.The system presents you with two software installation options. Choose the option, Add software to Existing Area from the Install Software menu. 14.The system asks you into which existing diskless environment you want to install software, and Performing an Upgrade 5-17 lists your options. Select the appropriate environment. 15.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 CD-ROM. 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 with the actual logical unit number of the device you are using: /_d_e_v/_r_m_t_N_h Make sure that the installed media is write- protected. If you are installing from CD-ROM to an area serving RISC clients, enter the following command: /_m_n_t/_R_I_S_C/_B_A_S_E__U_P_G_R_A_D_E If you are installing from CD-ROM to an area serving VAX clients, enter the following command: /_m_n_t/_V_A_X/_B_A_S_E__U_P_G_R_A_D_E 16.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? (y/n): 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 Boot/Upgrade media and installs them. The system copies and verifies each subset you selected. 17.If your upgrade media is a CD-ROM, use the following command to unmount the disk: # /_e_t_c/_u_m_o_u_n_t /_m_n_t If your installation media is TK50 or MT9 tape, remove it from the drive. 5-18 Performing an Upgrade 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. Performing an Upgrade 5-19 Adding and Deleting Software Subsets 6 The _s_e_t_l_d utility is used to install and manage software. You can save disk space with the _s_e_t_l_d command by specifying and loading only the software subsets that you need. This chapter describes how to use the _s_e_t_l_d utility. You must have superuser privileges to modify the system software using _s_e_t_l_d. The _s_e_t_l_d utility has several command line syntaxes to list, add, and delete software subsets. Although the command lines differ, the _s_e_t_l_d command lines use certain command arguments as follows: +o The dir 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 _r_o_o_t (/). +o The optional subset argument specifies the name of the subset. +o The location 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 dir 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 _s_e_t_l_d command, its functions, and the command line syntax, see _s_e_t_l_d(8) in the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. _6._1 _L_i_s_t_i_n_g _S_o_f_t_w_a_r_e _S_u_b_s_e_t_s To display the status of all subsets known to the system, specify the _s_e_t_l_d command with the -_i (inventory) function. The format is as follows: _s_e_t_l_d [-_D dir] -_i [subset] For example, to display a list of subsets, enter the following: # _s_e_t_l_d -_i To display the files included in a particular subset, for example, UDTUUCP435, enter the following: # _s_e_t_l_d -_i _U_D_T_U_U_C_P_4_3_5 _6._2 _A_d_d_i_n_g _S_u_b_s_e_t_s To add a subset to your system, use the _s_e_t_l_d command with the -_l (load) function, the location argument and the subset argument. The format is as follows: _s_e_t_l_d [-_D dir ] -_l subset [subset...] The following examples show how to add subsets to your system from tape and from a file server. _6._2._1 _A_d_d_i_n_g _S_u_b_s_e_t_s _f_r_o_m _T_a_p_e To add or reinstall a subset on the /_m_n_t directory of your system from a kit residing at tape drive /_d_e_v/_r_m_t_1_h, enter a command like the following: # _s_e_t_l_d -_D /_m_n_t -_l /_d_e_v/_r_m_t_1_h _U_D_T_U_U_C_P_4_3_0 _6._2._2 _A_d_d_i_n_g _S_u_b_s_e_t_s _f_r_o_m _a _F_i_l_e _S_e_r_v_e_r 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: # _s_e_t_l_d -_l _s_e_r_v_e_r: _6._3 _D_e_l_e_t_i_n_g _S_u_b_s_e_t_s To delete a subset from your system, use the _s_e_t_l_d command with the -_d function and the subset argument. The syntax is as follows: _s_e_t_l_d [-_D dir] -_d subset [subset...] 6-2 Adding and Deleting Software Subsets For example, to delete the UDTUUCP435 subset from your system, enter the following: # _s_e_t_l_d -_d _U_D_T_U_U_C_P_4_3_5 Adding and Deleting Software Subsets 6-3 Working in the Standalone ULTRIX Environment 7 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: +o Restoring a damaged root file system +o Checking the consistency of the root file system +o Restoring the boot block image +o 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 _I_n_v_o_k_i_n_g _t_h_e _S_t_a_n_d_a_l_o_n_e _U_L_T_R_I_X _E_n_v_i_r_o_n_m_e_n_t 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 _S_t_a_n_d_a_l_o_n_e _U_L_T_R_I_X _E_n_v_i_r_o_n_m_e_n_t _C_a_p_a_b_i_l_i_t_i_e_s 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 _m_k_f_s command instead of the _n_e_w_f_s command. _N_o_t_e 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 _M_A_K_E_D_E_V command. You can use the standalone system to perform the following tasks: +o Edit a file using the _e_d editor +o Repair corrupted file systems with the _f_s_c_k command +o Create new file systems with the _m_k_f_s command +o Restore the boot block with the _d_d command +o Restore file systems with the _r_e_s_t_o_r_e command +o Modify partition tables with the _c_h_p_t command 7-2 Working in the Standalone ULTRIX Environment +o Mount other disks and file systems with the _m_o_u_n_t command The _G_u_i_d_e _t_o _B_a_c_k_u_p _a_n_d _R_e_s_t_o_r_e gives an example of how to restore the root file system using the standalone ULTRIX environment after a catastrophic event has occurred. _7._3 _E_x_t_e_n_d_i_n_g _t_h_e _S_t_a_n_d_a_l_o_n_e _U_L_T_R_I_X _E_n_v_i_r_o_n_m_e_n_t 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: # _c_d /_d_e_v After changing directories, use the following syntax to create the special device files: _M_A_K_E_D_E_V device The following example shows the command for making a device special file for _r_z_0_a. # _M_A_K_E_D_E_V _r_z_0_a 2. Mount the device. For example, to mount the _r_z_0_a device on the /_m_n_t file system, use the following format: # /_e_t_c/_m_o_u_n_t /_d_e_v/_r_z_0_a /_m_n_t 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: # _l_s /_m_n_t The system responds by displaying the contents of /_m_n_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 /_m_n_t/_b_i_n Working in the Standalone ULTRIX Environment 7-3 to your path, enter the following command: # _P_A_T_H = "$_P_A_T_H:/_m_n_t/_b_i_n"; _e_x_p_o_r_t _P_A_T_H To exit the standalone environment and halt the processor, enter the following command: # /_e_t_c/_h_a_l_t To exit the standalone environment and return to the menu, press Ctrl/d. 7-4 Working in the Standalone ULTRIX Environment RISC Supported Software Subsets A Table A-1 contains the following information about each supported software subset for RISC processors: +o The subset name and contents. +o Whether the subset is required for a minimum ULTRIX system or whether it is optional. +o Whether the subset is dependent on other subsets. That is, the subset will not function unless the subsets on which it is dependent are installed before it is. +o Any system configuration file entries that must be edited into the system configuration file for the subset to function. _N_o_t_e All subsets require UDTBASE440, the Base System subset. Table A-1: _R_I_S_C _S_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s _D_e_s_c_r_i_p_t_i_o_n_s _a_n_d _D_e_p_e_n_d_e_n_c_i_e_s _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXMDECW440 Additional OSF/Motif Apps Optional The OOTB applications for the OSF/Motif user interface. _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXMMAIL440 DECwindows OSF/Motif UDTCDABASE440 Optional Mail UDTINET440 The mailer for the UDTMH440 OSF/Motif user UDTUMAIL440 interface. DXMMAN440 OSF/Motif Reference UDTDCMT440 Pages Optional Reference pages for the OSF/Motif user interface. DXMX11440 OSF/Motif User Optional Environment The MIT X11R5 tools. DXMDEVG0440 UWS Worksystem UDTPGMR440, Development G0 Library DXMXM440 Optional The G0 libraries for UWS. DXMXM440 OSF/Motif Development UDTPGMR440 Optional Env. The OSF/Motif development environment. UDTACCT440 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. A-2 RISC Supported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ UDTAFM440 Adobe Font Metric Optional Files 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. UDTBASE440 Base System Required for Required Fundamental utilities all subsets 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. UDTBIN440 Kernel Configuration Required to Required Files install Utility programs and layered binary files required products that to configure ULTRIX require the kernels. This subset kernel to be can be deleted after rebuilt. installation. UDTCDABASE440 CDA Base System Optional Run-time components for CDA. RISC Supported Software Subsets A-3 _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ UDTCDAPGMR440 CDA Software Dev UDTPGMR440 Optional Libraries Programming libraries for CDA. UDTCOMM440 Communications UDTINET440 Optional Utilities Utilities for several types of serial communications with other systems, including _t_i_p, _f_t_p, and _t_e_l_n_e_t. UDTDCMT440 Doc. Preparation Optional Extensions Tools to format, manage, and display reference pages. The _n_r_o_f_f formatter and required macros. UDTDCMTEXT440 Other Doc. Preparation UDTDCMT440 Software Optional Additional _n_r_o_f_f macro packages, bibiography tools, and _r_o_f_f tools. UDTDL440 Diskless Environment Optional Support Software for a diskless environment. This subset is required only for diskless management services. A-4 RISC Supported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ UDTEXAMPLES440 Programming Examples Optional Programming examples for: _d_b_x, _d_l_i, _n_c_s, device drivers, and others. UDTEXER440 System Exerciser Optional Package Programs that help in diagnosing problems with your hardware and peripheral devices. UDTINET440 TCP/IP Networking Kernel Required Utilities configuration: Programs and data used options INET to implement Internet networking on your ULTRIX system. RISC Supported Software Subsets A-5 ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDTINTLPGMR440 Internationalization Optional Dev. Env. Source for internationalization languages. UDTINTLRT440 Internationalization UDTPGMR440 Run-time Env. Optional Internationalization languages for _s_e_t_l_o_c_a_l_e and internationalization tools. UDTKERB440 Kerberos Network Authentication Optional Programs and data used to implement Kerberos network authentication on your ULTRIX system. UDTMAN440 Ref. Pages for Sys. UDTDCMT440 Admin. & Users Optional Online reference pages for Sections 1, 4, 5, 6, 7, and 8 of the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. UDTMANPGMR440 Reference Pages for UDTDCMT440 Programmers Optional Online reference pages for Sections 2 and 3 of the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. A-6 RISC Supported Software Subsets ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDTMH440 RAND Mail Handler UDTUMAIL440 Optional Programs that UDTINET440 constitute the RAND Corporation MH mail reader interface. UDTMIPSPGMR440 MIPS 3 Libraries UDTPGMR440 Optional Contains the -_m_i_p_s_3 libraries for programmers who want to compile programs using the -_m_i_p_s_3 option. UDTMOP440 Maintenance Operations Kernel Protocol configuration: Optional options DLI Software necessary to pseudodevice use your system as a dli boot server for LAT, DMS, or RIS. UDTNFS440 Network File System UDTINET Utilities Kernel Required configuration: Programs and data options NFS files you need to options RPC share file systems over the network. This subset contains the files used to implement the Yellow Pages facility. ________________________________________________________ RISC Supported Software Subsets A-7 ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDTPGMR440 Software Development Utilities Optional Libraries and utilities useful for software development. These include the libraries for linking programs to be analyzed with the _d_b_x debugger, the _l_i_n_t program verifier, the _l_e_x and _y_a_c_c parser packages, and the G0 libraries. UDTPRESTO440 Prestoserve Utilities Optional Utilities for monitoring and administering Prestoserve. UDTPRINT440 Printer Support Optional Environment Printer commands such as _l_p_r, _l_p_q, and _l_p_d, utilities, configuration files, filters, and PostScript printer support. UDTRPCDEV440 RPC Development UDTPGMR440 Optional Environment Programs and data that implement the Remote Procedure Call (RPC) development environment. A-8 RISC Supported Software Subsets ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDTRPCRT440 RPC Run-time Optional Environment Programs and data that implement the Remote Procedure Call (RPC) run-time environment. This subset is optional. UDTSCCS440 Source Code Control Optional System Programs that make up the UNIX Source Code Control System, which provides a regulation mechanism for large software projects. UDTSEC440 Enhanced Security Kernel Optional Features configuration: Programs and data that options AUDIT provide enhanced options security features. SYS_TPATH pseudodevice audit UDTSMSCAMP440 Sys. Config. Mgmt. Program (SCAMP) Optional This is a menu-driven program for basic system administration. UDTUMAIL440 Extended (Berkeley) UDTINET440 Required Mailer Programs and data that implement the BSD _s_e_n_d_m_a_i_l facility. RISC Supported Software Subsets A-9 ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDTUUCP440 UNIX-to-UNIX Copy UDTCOMM440 Optional Facility UDTINET440 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. UDT21OPGMR440 Symbolic Links for 210 UDTPGMR440 Optional Compiler Contains necessary symbolic links between layered products which depend on MIPS Version 2.10 tools and the current directories. UDWDECW440 Additional DECwindows Applications Optional Additional X11/DECwindows client applications such as Calendar and PostScript Previewer. UDWFONT440 X11/DECwindows 75dpi Fonts Required for Worksystems Fonts for X11/DECwindows. UDWFONT15440 X11/DECwindows 100dpi Fonts Required for DECsystem 5000 Workstation font files Model 200 with for systems using 2-D and 3-D either the VR160 15- graphics inch monitor or higher resolution graphics. A-10 RISC Supported Software Subsets ________________________________________________________ Subset Name Contents Requires ________________________________________________________ UDWFONTSTR440 X11/DECwindows PEX Required for Fonts DECsystem 5000 X11/DECwindows fonts Model 200 with for 3-D graphics 3-D graphics cards. UDWMAIL440 DECwindows Mail UDTUMAIL440 Optional Application UDTMH440 DECwindows mail UDTINET440 application for UDTCDABASE440 _d_x_m_a_i_l. UDWMAN440 UWS Runtime Reference UDTDCMT440 Optional Pages Online UWS reference pages for Sections 1, 4, 5, 6, 7, and 8. RISC Supported Software Subsets A-11 ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ UDWMANPGMR440 UWS Development UDTDCMT440 Optional Reference Pages Online UWS reference pages for Sections 2 and 3. UDWSER440 B&W, Color, or PX Server Optional Server for X11/DECwindows. UDWSYSMGNT440 System Management Optional Tools X11/DECwindows system management programs. UDWWSTSER440 X11R4 PXG Server Optional Server for X11RR PXG 3D graphics. UDWX11440 X11/DECwindows User Environment Required for Worksystems X Window System client programs. UDWXDEV440 Worksystem Development UDTBASE440 Environment Optional Library and data files needed to produce X Window System client applications. Includes example programs demonstrating how to get started. UDWXTXSER440 Truecolor Server Optional Server for True Color Graphics. ________________________________________________________ A-12 RISC Supported Software Subsets VAX Supported Software Subsets B Table B-1 contains the following information about each supported software subset for VAX processors: +o The subset name and contents. +o Whether the subset is required for a minimum ULTRIX system or whether it is optional. +o Whether the subset is dependent on other subsets. That is, the subset will not function unless the subset(s) on which it is dependent are installed before it is. +o Any system configuration file entries that must be edited into the system configuration file for the subset to function. _N_o_t_e All subsets require ULTBASE440, the Base System subset. Table B-1: _V_A_X _S_u_p_p_o_r_t_e_d _S_o_f_t_w_a_r_e _S_u_b_s_e_t _D_e_s_c_r_i_p_t_i_o_n_s _a_n_d _D_e_p_e_n_d_e_n_c_i_e_s _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXVDECW440 Additional OSF/Motif Appls. Optional The OOTB applications for the OSF/Motif user interface. _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXVMAIL440 DECwindows OSF/Motif ULTCDABASE440 Optional Mail ULTINET440 The mailer for the ULTMH44O OSF/Motif user ULTUMAIL440 interface. DXVMAN440 OSF/Motif Reference ULTDCMT440 Pages Optional The reference pages for the OSF/Motif user interface. DXVX11440 OSF/Motif User Optional Environment The MIT X11R5 tools. DXVXM440 The OSF/Motif ULTPGMR440 Development Env. Optional The OSF/Motif development environment. ULTACCT440 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. B-2 VAX Supported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULTAFM440 Adobe Font Metric Optional Files 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. ULTBASE440 Base System Required for Required Fundamental utilities all subsets 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. ULTBIN440 Kernel Configuration Required to Required Files install Utility programs and layered binary files required products that to configure ULTRIX require the kernels. This subset kernel to be can be deleted after rebuilt. installation. ULTCDABASE440 CDA Base System Optional Run-time components for CDA. VAX Supported Software Subsets B-3 _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULTCDAPGMR440 CDA Software Dev ULTPGMR440 Optional Libraries. Programming libraries for CDA. ULTBSC440 Bisynchronous Kernel Optional Communications configuration: Programs needed to use options BSC the 3780 and 2780 pseudodevice emulation features bsc provided with your ULTRIX system. ULTCOMM440 Communications ULTINET440 Optional Utilities Utilities for several types of serial communications with other systems, including _t_i_p, _f_t_p, and _t_e_l_n_e_t. ULTDCMT440 Doc. Preparation for Optional Ref. Pages Tools to format, manage, and display reference pages. The _n_r_o_f_f formatter and required macros. ULTDCMTEXT440 Doc. Preparation ULTDCMT440 Optional Extensions Additional _n_r_o_f_f macro packages, bibiography tools, and _r_o_f_f tools. B-4 VAX Supported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULTDL440 Diskless Support Optional Environment Software for a diskless environment. This subset is required only for diskless management services. ULTEXAMPLES440 Programming Examples Optional Programming examples for: _d_b_x, _d_l_i, _n_c_s, device drivers, and others. ULTEXER440 System Exerciser Optional Package Programs that help in diagnosing problems with your hardware and peripheral devices. ULTINET440 TCP/IP Networking Required Utilities Programs and data used to implement Internet networking on your ULTRIX system. ULTINTLPGMR440 Internationalization ULTPGMR440 Dev. Env. Optional Source for internationalization languages. VAX Supported Software Subsets B-5 _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULTINTLRT440 Internationalization Optional Run-time Env. Internationalization languages for _s_e_t_l_o_c_a_l_e and internationalization tools. ULTKERB440 Kerberos Network Optional Authentication Programs and data used to implement Kerberos network authentication on your ULTRIX system. ULTMAN440 Ref. Pages for Sys. ULTDCMT440 Optional Admin. & Users Online reference pages for Sections 1, 4, 5, 6, 7, and 8 of the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. ULTMANPGMR440 Reference Pages for ULTDCMT440 Optional Programmers Online reference pages for Sections 2 and 3 of the _U_L_T_R_I_X _R_e_f_e_r_e_n_c_e _P_a_g_e_s. ULTMH440 The RAND Mail Handler ULTINET440 Optional Programs that ULTUMAIL440 constitute the RAND Corporation MH mail reader interface. _____________________________________________________ B-6 VAX Supported Software Subsets ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULTMOP440 Maintenance Operations Kernel Optional Protocol configuration: Software necessary to options DLI use your system as a pseudodevice boot server for LAT, dli DMS, or RIS. ULTNFS440 Network File System ULTINET440 Required Utilities Kernel Programs and data configuration: files you need to options NFS share file systems options RPC over the network. This subset contains the files used to implement the Yellow Pages facility. ULTPASCAL440 Pascal Development Optional Package Pascal language compiler and associated libraries and tools. ULTPGMR440 Software Development Required for: Optional Utilities ULTINTL440 Libraries and ULTRPCDEV440 utilities useful for software development. These include the libraries for linking programs to be analyzed with the _d_b_x debugger, the _l_i_n_t program verifier, and the _l_e_x and _y_a_c_c parser packages. VAX Supported Software Subsets B-7 ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULTPRESTO440 Prestoserve Utilities Optional Utilities for monitoring and administering Prestoserve. ULTPRINT440 Printer Support Optional Environment Printer commands such as _l_p_r, _l_p_q, and _l_p_d, utilities, configuration files, filters, and PostScript printer support. ULTRPCDEV440 RPC Development ULTPGMR440 Optional Environment Programs and data that implement the Remote Procedure Call (RPC) development environment. ULTRPCRT440 RPC Run-time Optional Environment Programs and data that implement the Remote Procedure Call (RPC) run-time environment. ________________________________________________________ B-8 VAX Supported Software Subsets ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULTSCCS440 Source Code Control Optional System Programs that make up the UNIX Source Code Control System, which provides a regulation mechanism for large software projects. ULTSEC440 Enhanced Security Kernel Optional Features configuration: Programs and data that options AUDIT provide enhanced options security features. SYS_TPATH pseudodevice audit ULTSMSCAMP440 Sys. Config. Mgmt. Program (SCAMP) Optional This is a menu-driven program for basic system administration. ULTUMAIL440 Extended (Berkeley) ULTINET440 Mailer Required Programs and data that implement the BSD _s_e_n_d_m_a_i_l facility. ULTUUCP440 UNIX-to-UNIX Copy ULTCOMM440 Facility ULTINET440 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. VAX Supported Software Subsets B-9 ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULTVAXC440 VAX C Development Optional Package VAX C language compiler and associated libraries and tools. UWSDECW440 Additional DECwindows Optional Applications Additional X11/DECwindows client applications such as Calendar and the PostScript Previewer. UWSFONT440 X11/DECwindows 75dpi Required for Fonts Worksystems Fonts for X11/DECwindows. UWSFONT15440 X11/DECwindows 100dpi Optional Fonts Workstation font files for systems using either the VR160 15- inch monitor or higher resolution graphics. ________________________________________________________ B-10 VAX Supported Software Subsets ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ UWS3DFONT440 VS35XX X11/DECwindows Required for Fonts VAXstation X11/DECwindows fonts 3520/3540 for VAXstation 3520/3540 processors. UWSMAIL440 DECwindows Mail ULTINET440 Optional Application ULTCDABASE440 DECwindows mail ULTMH440 application for ULTUMAIL440 _d_x_m_a_i_l. UWSMAN440 UWS Runtime Reference ULTDCMT440 Optional Pages Online UWS reference pages for Sections 1, 4, 5, 6, 7, and 8. UWSMANPGMR440 UWS Ref. Pages for ULTDCMT440 Optional Programmers Online UWS reference pages for Sections 2 and 3. UWSSER440 X11/DECwindows Servers Requires: Required for X11/DECwindows server ULTBASE440 Worksystems support. UWSSYSMGNT System Management Requires: Optional Tools ULTBASE440 X11/DECwindows system management programs. UWSX11440 X11/DECwindows User Required for Environment Worksystems X Window System client programs. VAX Supported Software Subsets B-11 ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ UWSXDEV440 Worksystem Development ULTPGMR44 Optional Environment Library and data files needed to produce X Window System client applications. Includes example programs demonstrating how to get started. ________________________________________________________ B-12 VAX Supported Software Subsets Unsupported Software Subsets C Table C-1 contains the following information about each unsupported software subset on the RISC and VAX software distribution: +o The subset name and contents. The UDX and DXM prefixes indicate RISC software subsets. The ULX and DXV prefixes indicate VAX software subsets. +o Whether the subset is dependent on other subsets. That is, the subset will not function unless the subset(s) on which it is dependent are installed before it is. +o The asterisk (*) denotes user-contributed software. _N_o_t_e All RISC subsets require the UDTBASE440 subset; all VAX subsets requre the ULTBASE440 subset. You can use the _s_e_t_l_d command to install some or all of the unsupported software subsets included with your ULTRIX system. See Chapter 6 and the _s_e_t_l_d(8) for more information. Table C-1: _U_n_s_u_p_p_o_r_t_e_d _S_o_f_t_w_a_r_e _S_u_b_s_e_t _D_e_s_c_r_i_p_t_i_o_n_s _a_n_d _D_e_p_e_n_d_e_n_c_i_e_s _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXMUNDEMO440 OSF/MOTIF Demos (RISC) UDTPGMR440 RISC demonstration programs for the OSF/Motif interface. _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ DXVUNDEMO440 OSF/MOTIF Demos (VAX) ULTPGMR440 VAX demonstration programs for the OSF/Motif interface. ULXAPL440* APL Development Package APL language interpreter and associated utilities. ULXBASE440* Base Extension UDXBASE440* Programs and data files that can be useful in some environments. These include obsolete boot programs, drivers for unsupported devices, the _t_r_o_f_f package with fonts, and miscellaneous software. ULXBIB440*, Bibliographic ULTDCMT440 or Utilities UDTDCMT440 UDXBIB440* Programs and data useful in maintaining bibliographic information. ULXCOURIER440*, Remote Procedure Call Compiler UDXCOURIER440* Modules for producing software using the COURIER remote procedure call protocol. C-2 Unsupported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULXCPM440* CP/M 8in Diskette Utility Utilities for reading and writing 8-inch diskettes used with the CP/M operating system. ULXDCMT440, Document Preparation UDXDCMT440 Software Additional documentation preparation utilities and fonts. ULXDOC440, Supplementary ULTDCMT440 or UDXDOC440 Documentation UDTDCMT440 Online copies of Supplementary Documentation. ULXEDIT440*, GNU Emacs UDXEDIT440* The public-domain GNU Emacs editor and edit-macro files. ULXF77440 Unsupported FORTRAN Utilities Utilities for developing programs using the UNIX _f_7_7 dialect of FORTRAN. ULXGAMES440*, Games and Diversions UDXGAMES440* Programs used for entertainment. Unsupported Software Subsets C-3 _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULXHYPER440* Hyperchannel Utilities The Hyperchannel driver and associated daemons and utilities. ULXICON440* ICON (Language) Development Package Translator and linker for the ICON programming language. ULXINGRES440 University INGRES QUEL DBMS (database management system). ULXINET440 TCP/IP Networking Util Extension UDXINET440 Networking utilities: _t_r_a_c_e_r_o_u_t_e, _s_l_i_p. ULXLEARN440, Computer-Aided System Tutor UDXLEARN440 Software for the _l_e_a_r_n program, which provides lessons in aspects of the computing environment. This subset is useful for persons new to the UNIX environment. C-4 Unsupported Software Subsets _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULXLISP440 Franz Lisp Development Package Programs that make up the Franz Lisp program development environment, including interpreter, libraries, and compiler. ULXMAN440, Unsupported Online UDTDCMT440 or UDXMAN440 Manuals ULTDCMT440 Online reference pages for programs found in the Base Extension subset. ULXMOD2440, Modula-2 Development Package Modula-2 compiler and libraries. ULXNEWS440, USENET News Interface ULTCOMM440 and UDXNEWS440 Software ULTUUCP440, or Software needed to UDTCOMM440 and participate in the UDTUUCP440 USENET news network. ULXNOTES440, Notesfiles Package UDXNOTES440 Software that lets you establish _n_o_t_e_s_f_i_l_e_s on your ULTRIX system. Unsupported Software Subsets C-5 _____________________________________________________ Subset Name Contents Dependencies _____________________________________________________ ULXRCS440, Revision Control UDXRCS440 System Programs that make up a package similar to the SCCS facility provided with the supported software subsets. _____________________________________________________ C-6 Unsupported Software Subsets ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULXSHELLS440, Aux. Command Line Interpreters UDXSHELLS440 The "distributed" shell and a version of the C shell that features command completion. ULXSPMS440 Software Project Management System A package useful for managing large software development efforts. ULXTERM440 Additional Terminal UDXTERM440 Drivers Additional _t_e_r_m_i_n_f_o Optional files and terminal drivers ULXTOOLS440*, Misc. User-Contributed UDXTOOLS440* Utilities Small utilities contributed by the user community. ULXUNEXAMP440 Unsupported DECwindows UDTPGMR440, or Examples ULTPGMR440 UDXUNEXAMP440 DECwindows programming examples. ULXUNFONTS440 Unsupported MIT fonts UDXUNFONTS440 MIT fonts Unsupported Software Subsets C-7 ________________________________________________________ Subset Name Contents Dependencies ________________________________________________________ ULXUNMAN440, Unsupported X11 ULTDCMT440 or Reference Pages UDTDCMT440 UDXUNMAN440 Online reference pages for unsupported X11 R4 features that are in the UDXUNMIT440 and ULXUNMIT440 subsets. ULXUNMIT440 Unsupported X11 Components UDXUNMIT440 Programs and fonts for the X Window System protocol level 11, Release 4. Contains applications such as _x_t_e_r_m, _x_l_o_a_d, and _x_e_d_i_t. ULXVARIAN440 Raster Plotter Package Software used to typeset documents on the VARIAN typesetter. ________________________________________________________ C-8 Unsupported Software Subsets Sample Advanced Installation Procedure D Example D-1 is a sample log of an advanced installation performed on a DECstation 5000 Model 150. 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. _D._1 _S_a_m_p_l_e _A_d_v_a_n_c_e_d _I_n_s_t_a_l_l_a_t_i_o_n _P_r_o_c_e_d_u_r_e. Example D-1: _S_a_m_p_l_e _A_d_v_a_n_c_e_d _I_n_s_t_a_l_l_a_t_i_o_n *** 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 ULTRIX Device Controller Controller Name Name Number Name Number Example D-1: (continued) ---------------------------------------------------------------------- 1 RZ57 rz0 0 SCSI 0 2 RZ25 rz2 2 SCSI 0 3 RZ24 rz3 3 SCSI 0 ---------------------------------------------------------------------- Enter your choice: 1 You selected RZ57, device number 0. Make sure this disk drive is on line and write-enabled (if applicable to your disk drive), then confirm your choice. Use RZ57, rz0, for your system disk? (y/n) []: y The installation procedure now allocates the root file system on partition 'a' of the system disk, rz0 RZ57. Making the root file system on rz0 RZ57. The installation procedure is now restoring the root file system to partition 'a' of the system disk, rz0 RZ57. *** BOOTSTRAP COMMAND SEQUENCE *** Issue the following console commands to set your default bootpath variable and to boot your system disk: >> setenv boot "3/rz0/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: rain You selected rain as the name of your system. Is this correct? (y/n) [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, 02:54 p.m. on Feb 2, 1993 would be entered as: D-2 Sample Advanced Installation Procedure Example D-1: (continued) 9302021454 Enter the date and time: 9310051015 *** 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 Eastern c Central m Mountain p Pacific g Greenwich --------------------------------- Enter your choice: e Does your area alternate between Daylight Savings and Standard time? (y/n) [y]: Select your geographic area for Daylight Savings Time, using the options in the table below. Selection Geographic Area -------------------------------- u USA a Australia e Eastern Europe c Central Europe w Western Europe -------------------------------- Enter your choice [u]: The current date and time is Tue Oct 5 10:15:04 EDT 1993 *** FILE SYSTEM DEFAULT OPTION *** The following table shows the default file system layout on RZ57, rz0: partition bottom top size overlap default a 0 32767 32768 c root b 32768 217087 184320 c swap, dump g 217088 831487 614400 c /usr If you choose the defaults, the var area will be allocated to /usr/var. Sample Advanced Installation Procedure D-3 Example D-1: (continued) Do you want to choose the default file system layout? (y/n): n *** /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 Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ57 rz0 0 SCSI 0 2 RZ25 rz2 2 SCSI 0 3 RZ24 rz3 3 SCSI 0 ---------------------------------------------------------------------- Enter your choice: 1 You selected RZ57, device number 0. Make sure this disk is on line and write-enabled (if applicable to this drive) and then confirm your choice. Use RZ57, rz0 for /usr file system? (y/n) []: y The disk rz0 you selected from the previous table has the following partitions available, on which you can allocate the /usr file system: partition size (Kbytes) overlap ------------------------------------------------ d --- 149504 c,h e --- 149504 c,h f --- 262273 c,h g --- 307200 c h --- 561281 c,d,e,f ------------------------------------------------ Type the letter of the partition on which you want to allocate the /usr file system [g]: h Making the new file system for /usr on /dev/rrz0h RZ57 *** 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 D-4 Sample Advanced Installation Procedure Example D-1: (continued) Selection Device ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ57 rz0 0 SCSI 0 2 RZ25 rz2 2 SCSI 0 3 RZ24 rz3 3 SCSI 0 ---------------------------------------------------------------------- Enter your choice: 1 You selected RZ57, device number 0. Make sure this disk is on line and write-enabled (if applicable to this drive) and then confirm your choice. Use RZ57, rz0 for swap1 space? (y/n) []: y The disk rz0 you selected from the previous table has the following partitions available, on which you can allocate the swap1 space: partition size (Kbytes) overlap ------------------------------------------------ b --- 92160 c g --- 307200 c ------------------------------------------------ Type the letter of the partition on which you want to allocate the swap1 space [b]: *** ALLOCATE THE SWAP2 SPACE *** Do you want to allocate a second swap space? (y/n) [n]: n *** 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 ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ57 rz0 0 SCSI 0 2 RZ25 rz2 2 SCSI 0 3 RZ24 rz3 3 SCSI 0 ---------------------------------------------------------------------- Enter your choice: 1 You selected RZ57, device number 0. Make sure this disk is Sample Advanced Installation Procedure D-5 Example D-1: (continued) on line and write-enabled (if applicable to this drive) and then confirm your choice. Use RZ57, rz0 for crash dump space? (y/n) []: y The disk rz0 you selected from the previous table has the following partitions available, on which you can allocate the crash dump space: partition size (Kbytes) overlap ------------------------------------------------ g --- 307200 c b --- 92160 c ------------------------------------------------ Type the letter of the partition on which you want to allocate the crash dump space [b]: *** 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 ULTRIX Device Controller Controller Name Name Number Name Number ---------------------------------------------------------------------- 1 RZ57 rz0 0 SCSI 0 2 RZ25 rz2 2 SCSI 0 3 RZ24 rz3 3 SCSI 0 ---------------------------------------------------------------------- Enter your choice: 1 You selected RZ57, device number 0. Make sure this disk is on line and write-enabled (if applicable to this drive) and then confirm your choice. Use RZ57, rz0 for var file system? (y/n) []: y The disk rz0 you selected from the previous table has the following partitions available, on which you can allocate the var file system: partition size (Kbytes) overlap ------------------------------------------------ g --- 307200 c h --- 561281 c,d,e,f ------------------------------------------------ Type the letter of the partition on which you want D-6 Sample Advanced Installation Procedure Example D-1: (continued) to allocate the var file system [g]: Making the new file system for var on /dev/rrz0g RZ57 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: 1 *** 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 *** Select the DECwindows User Interface *** 1) DECwindows for OSF/Motif 2) X11/DECwindows (XUI) Enter your choice [1]: 1 *** 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 * OSF/Motif User Environment * X11/DECwindows 75dpi Fonts The subsets listed below are optional: 1) Truecolor Server 2) X11R4 PXG Server 3) X11/DECwindows 100dpi Fonts 4) X11/DECwindows PEX Fonts 5) Printer Support Environment 6) RAND Mail Handler 7) Sys. Config. Mgmt. Program (SCAMP) 8) Communications Utilities 9) Unix-to-Unix Copy Facility 10) Maintenance Operations Protocol 11) Accounting Software 12) Kerberos Network Authentication 13) Enhanced Security Features 14) Prestoserve Utilities 15) System Exerciser Package 16) Doc. Preparation for Ref. Pages 17) Doc. Preparation Extensions 18) Adobe Font Metric Files 19) Software Development Utilities 20) Source Code Control System Sample Advanced Installation Procedure D-7 Example D-1: (continued) 21) Internationalization Runtime Env. 22) Internationalization Dev. Env. 23) CDA Base System 24) CDA Software Dev Libraries 25) RPC Runtime Environment 26) RPC Development Environment 27) Ref. Pages for Sys. Admin. & Users 28) Reference Pages for Programers 29) Programming Examples 30) Additional OSF/Motif Apps. 31) DECwindows OSF/Motif Mail 32) OSF/Motif Development Env. 33) OSF/Motif Reference Pages 34) System Management Tools 35) Worksystem Dev. G0 Libraries 36) Mips 3 Libraries 37) Symbolic Links for 2.10 Compiler 38) All mandatory and all optional subsets 39) Mandatory subsets only 40) Exit without installing subsets Enter your choice(s): 38 Working....Tue Oct 5 10:27:46 EDT 1993 You are installing the following subsets: Base System Kernel Config Files TCP/IP Networking Utilities Network File System Utilities Extended (Berkeley) Mailer B&W, Color, or PX Server OSF/Motif User Environment X11/DECwindows 75dpi Fonts Truecolor Server X11R4 PXG Server X11/DECwindows 100dpi Fonts X11/DECwindows PEX Fonts Printer Support Environment RAND Mail Handler Sys. Config. Mgmt. Program (SCAMP) Communications Utilities Unix-to-Unix Copy Facility Maintenance Operations Protocol Accounting Software Kerberos Network Authentication Enhanced Security Features Prestoserve Utilities System Exerciser Package Doc. Preparation for Ref. Pages Doc. Preparation Extensions Adobe Font Metric Files Software Development Utilities Source Code Control System Internationalization Runtime Env. Internationalization Dev. Env. CDA Base System CDA Software Dev Libraries RPC Runtime Environment RPC Development Environment Ref. Pages for Sys. Admin. & Users Reference Pages for Programers Programming Examples Additional OSF/Motif Apps. DECwindows OSF/Motif Mail OSF/Motif Development Env. OSF/Motif Reference Pages System Management Tools Worksystem Dev. G0 Libraries Mips 3 Libraries Symbolic Links for 2.10 Compiler Is this correct? (y/n): y Base System (UDTBASE440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:28:20 EDT 1993 Working....Tue Oct 5 10:30:36 EDT 1993 Working....Tue Oct 5 10:32:52 EDT 1993 Working....Tue Oct 5 10:34:55 EDT 1993 Verifying Working....Tue Oct 5 10:35:49 EDT 1993 D-8 Sample Advanced Installation Procedure Example D-1: (continued) Kernel Config Files (UDTBIN440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:37:06 EDT 1993 Working....Tue Oct 5 10:39:15 EDT 1993 Working....Tue Oct 5 10:41:26 EDT 1993 Working....Tue Oct 5 10:43:36 EDT 1993 Verifying Working....Tue Oct 5 10:45:27 EDT 1993 TCP/IP Networking Utilities (UDTINET440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:47:01 EDT 1993 Verifying Network File System Utilities (UDTNFS440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:48:58 EDT 1993 Verifying Extended (Berkeley) Mailer (UDTUMAIL440) Copying from /dev/nrmt0h (tape) Verifying B&W, Color, or PX Server (UDWSER440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:50:32 EDT 1993 Working....Tue Oct 5 10:51:17 EDT 1993 Working....Tue Oct 5 10:53:21 EDT 1993 Verifying Working....Tue Oct 5 10:54:30 EDT 1993 OSF/Motif User Environment (DXMX11440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 10:55:03 EDT 1993 Working....Tue Oct 5 10:57:08 EDT 1993 Working....Tue Oct 5 10:59:11 EDT 1993 Working....Tue Oct 5 11:01:13 EDT 1993 Verifying Working....Tue Oct 5 11:01:56 EDT 1993 X11/DECwindows 75dpi Fonts (UDWFONT440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:02:39 EDT 1993 Working....Tue Oct 5 11:03:56 EDT 1993 Verifying Truecolor Server (UDWXTXSER440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:05:12 EDT 1993 Working....Tue Oct 5 11:07:05 EDT 1993 Verifying Sample Advanced Installation Procedure D-9 Example D-1: (continued) X11R4 PXG Server (UDWWSTSER440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:08:49 EDT 1993 Verifying X11/DECwindows 100dpi Fonts (UDWFONT15440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:10:02 EDT 1993 Working....Tue Oct 5 11:12:04 EDT 1993 Working....Tue Oct 5 11:14:05 EDT 1993 Working....Tue Oct 5 11:16:22 EDT 1993 Verifying X11/DECwindows PEX Fonts (UDWFONTSTR440) Copying from /dev/nrmt0h (tape) Verifying Printer Support Environment (UDTPRINT440) Copying from /dev/nrmt0h (tape) Volume change. Rewinding tape... Working....Tue Oct 5 11:18:32 EDT 1993 Please remove tape volume 1 and replace it with volume 2. Are you ready (y/n)? y Working....Tue Oct 5 11:21:06 EDT 1993 Verifying RAND Mail Handler (UDTMH440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:22:12 EDT 1993 Verifying Sys. Config. Mgmt. Program (SCAMP) (UDTSMSCAMP440) Copying from /dev/nrmt0h (tape) Verifying Communications Utilities (UDTCOMM440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:25:00 EDT 1993 Verifying Unix-to-Unix Copy Facility (UDTUUCP440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:25:42 EDT 1993 Verifying Maintenance Operations Protocol (UDTMOP440) Copying from /dev/nrmt0h (tape) Verifying Accounting Software (UDTACCT440) Copying from /dev/nrmt0h (tape) D-10 Sample Advanced Installation Procedure Example D-1: (continued) Verifying Kerberos Network Authentication (UDTKERB440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:27:42 EDT 1993 Verifying Enhanced Security Features (UDTSEC440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:28:43 EDT 1993 Verifying Prestoserve Utilities (UDTPRESTO440) Copying from /dev/nrmt0h (tape) Verifying System Exerciser Package (UDTEXER440) Copying from /dev/nrmt0h (tape) Verifying Doc. Preparation for Ref. Pages (UDTDCMT440) Copying from /dev/nrmt0h (tape) Verifying Doc. Preparation Extensions (UDTDCMTEXT440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:31:08 EDT 1993 Verifying Adobe Font Metric Files (UDTAFM440) Copying from /dev/nrmt0h (tape) Verifying Software Development Utilities (UDTPGMR440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:32:28 EDT 1993 Verifying Working....Tue Oct 5 11:34:26 EDT 1993 Source Code Control System (UDTSCCS440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:34:50 EDT 1993 Verifying Internationalization Runtime Env. (UDTINTLRT440) Copying from /dev/nrmt0h (tape) Verifying Internationalization Dev. Env. (UDTINTLPGMR440) Copying from /dev/nrmt0h (tape) Verifying Sample Advanced Installation Procedure D-11 Example D-1: (continued) CDA Base System (UDTCDABASE440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:36:43 EDT 1993 Verifying CDA Software Dev Libraries (UDTCDAPGMR440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:38:46 EDT 1993 Verifying RPC Runtime Environment (UDTRPCRT440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:39:36 EDT 1993 Verifying RPC Development Environment (UDTRPCDEV440) Copying from /dev/nrmt0h (tape) Verifying Ref. Pages for Sys. Admin. & Users (UDTMAN440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:41:00 EDT 1993 Verifying Reference Pages for Programers (UDTMANPGMR440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:42:44 EDT 1993 Verifying Programming Examples (UDTEXAMPLES440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:44:30 EDT 1993 Verifying Additional OSF/Motif Apps. (DXMDECW440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:45:22 EDT 1993 Working....Tue Oct 5 11:47:24 EDT 1993 Verifying Working....Tue Oct 5 11:48:17 EDT 1993 DECwindows OSF/Motif Mail (DXMMAIL440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:48:48 EDT 1993 Verifying OSF/Motif Development Env. (DXMXM440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:50:22 EDT 1993 Working....Tue Oct 5 11:52:29 EDT 1993 Verifying Working....Tue Oct 5 11:53:51 EDT 1993 D-12 Sample Advanced Installation Procedure Example D-1: (continued) OSF/Motif Reference Pages (DXMMAN440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:54:33 EDT 1993 Verifying Working....Tue Oct 5 11:56:49 EDT 1993 System Management Tools (UDWSYSMGNT440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 11:57:20 EDT 1993 Working....Tue Oct 5 11:59:22 EDT 1993 Working....Tue Oct 5 12:01:24 EDT 1993 Working....Tue Oct 5 12:01:45 EDT 1993 Verifying Worksystem Dev. G0 Libraries (DXMXDEVG0440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 12:02:53 EDT 1993 Working....Tue Oct 5 12:03:15 EDT 1993 Verifying Mips 3 Libraries (UDTMIPS3PGMR440) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 12:05:10 EDT 1993 Verifying Symbolic Links for 2.10 Compiler (UDT210PGMR440) Copying from /dev/nrmt0h (tape) Verifying Rewinding Tape... Working....Tue Oct 5 12:08:55 EDT 1993 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 Oct 5 12:25:35 EDT 1993 Working....Tue Oct 5 12:27:36 EDT 1993 Working....Tue Oct 5 12:29:37 EDT 1993 Working....Tue Oct 5 12:31:39 EDT 1993 The following subsets will be installed: * Generic Kernel Do you wish to continue? (y/n): y Generic Kernel (UDTGENVMUNIX441) Copying from /dev/nrmt0h (tape) Working....Tue Oct 5 12:34:22 EDT 1993 Sample Advanced Installation Procedure D-13 Example D-1: (continued) Verifying Rewinding Tape... Working....Tue Oct 5 12:35:41 EDT 1993 The installation procedure has successfully installed the Upgrade subsets *** CONFIGURATION FILE KERNEL OPTION SELECTION *** Selection Kernel Option --------------------------------------------------------------- 1 Local Area Transport (LAT) 2 Bisynchronous Communication protocol (VAX only) 3 Computer Interconnect (CI) network 4 Diagnostic/Utilities Protocol (DUP) 5 ISO9660 File System Support (CDFS) 6 Ethernet Packet Filter 7 Enhanced Security Features 8 All of the above 9 None of the above ---------------------------------------------------------------- Enter the selection number for each kernel option you want. For example, 1 3 : 1 2 3 4 5 6 You specified the following kernel options: Local Area Transport (LAT) Computer Interconnect (CI) network Diagnostic/Utilities Protocol (DUP) ISO9660 File System Support (CDFS) Ethernet Packet Filter Is this correct? (y/n) [n]: y *** SYSTEM CONFIGURATION PROCEDURE *** Configuration file complete. Do you want to edit the configuration file? (y/n) [n]: n *** PERFORMING SYSTEM CONFIGURATION *** working ..... Tue Oct 5 12:37:34 EDT 1993 working ..... Tue Oct 5 12:39:35 EDT 1993 working ..... Tue Oct 5 12:41:35 EDT 1993 *** DEVICE SPECIAL FILE CREATION *** working ..... Tue Oct 5 12:43:03 EDT 1993 *** SOFTWARE INSTALLATION PROCEDURE COMPLETE *** D-14 Sample Advanced Installation Procedure Example D-1: (continued) The following files were created during the installation procedure: /vmunix - customized kernel /genvmunix - generic kernel /usr/adm/install.log - installation log file /usr/adm/install.FS.log - file systems log file /usr/adm/install.DEV.log - special device log file Sample Advanced Installation Procedure D-15 Installation Notes E This chapter discusses issues and known problems about the installation and upgrade of ULTRIX and UWS software. Read this appendix to see if the issues here pertain to your configuration. _E._1 _H_a_r_d_w_a_r_e _E._1._1 _T_Z_8_5 _T_a_p_e _D_r_i_v_e _C_a_p_a_c_i_t_y The blocking factor of the TZ85 tape drive is 4 Kbytes. This means that the data is managed internally in units of 4 Kbytes. This does not affect or limit the block size used by host systems. However, data is stored in units of 4 Kbytes on the media, and blocks that are not an integral multiple of 4 Kbytes cause capacity and throughput reductions. Capacity reductions occur for the following utilities if the default parameters are used: +o _d_u_m_p (20%) +o _c_p_i_o (75%) +o _d_d (85%) +o _t_a_r (20%) +o _l_t_f (50%) The following examples show how to use the commands when specifying a different default block size: # _t_a_r _c_h_v_b_f _6_4 /_d_e_v/_r_m_t_0_h . # _d_d _i_f=/_d_e_v/_r_r_z_1_g _o_f=/_d_e_v/_r_m_t_0_h _b_s=_3_2_7_6_8 # _l_t_f -_c_f_B /_d_e_v/_r_m_t_0_h _3_2_7_6_8 _t_z_8_5__t_2-_2__d_e_c._t_z__i_m_a_g_e # _f_i_n_d . -_c_p_i_o -_o_v_B > /_d_e_v/_r_m_t_0_h The following sections discuss hardware and peripheral devices. _E._1._2 _P_r_o_c_e_d_u_r_e _t_o _C_h_a_n_g_e _I_D _S_t_r_i_n_g_s _f_o_r _T_S_Z_0_7 _U_n_i_t_s A vendor identity string change in the TSZ07 may cause some early units not to be recognized by the ULTRIX operating system. This section describes how to reset the Vendor ID and the Device ID strings associated with the earlier versions of the TSZ07. To reset the Vendor ID, use the following steps. Note that you must take no longer than three seconds to perform each step from 3 through 7. If you do not perform these steps in the allotted time, you must begin the procedure from step 1. 1. Turn on both the AC Power Switch (rear panel) and the DC Power Switch (front panel). 2. If the ONLINE indicator is on, press the ONLINE switch (3) to turn the indicator off. 3. Press the WRT EN / TEST switch (4). 4. Press the DENSITY SELECT switch (5) and release, and then press the DENSITY SELECT switch (5) again. 5. Press the WRT EN / TEST switch (4). 6. Press the UNLOAD switch (2). 7. Press the DENSITY SELECT switch (5). The service aid now starts with the current vendor ID being displayed on the alphanumeric display and a cursor is placed on the left character space. The front panel switches function as follows: - 1 - Increments the selected character up the ASCII character set. - 2 - Decrements the selected character down the ASCII character set. - 3 - Moves the cursor one position to the right to select a character. - 4 - Exits service aid without saving changed characters. - 4 and 5 - Pressing both switches simultaneously saves new characters and exits the service aid; the message SAVING appears. - 5 - No function. E-2 Installation Notes 8. If the Vendor ID is DEC, exit the service aid. If the Vendor ID is CIPHER, change it to DEC, and save the change before you exit the service aid. To reset the Device ID, use the following steps. Note that you must take no longer than three seconds to perform each step from 3 through 7. If you do not perform these steps in the allotted time, you must begin the procedure from step 1. 1. Turn on both the AC Power Switch (rear of panel) and the DC Power Switch (front panel). 2. If the ONLINE indicator is on, press the ONLINE switch (3) to turn the indicator off. 3. Press the WRT EN / TEST switch (4). 4. Press the DENSITY SELECT switch (5) and release, and then press the DENSITY SELECT switch (5) again. 5. Press the WRT EN / TEST switch (4). 6. Press the ONLINE switch (3). 7. Press the DENSITY SELECT switch (5). The service aid now starts with the current device ID being displayed on the alphanumeric display and a cursor is placed on the left character space. The front panel switches function as follows: - 1 - Increments the selected character up the ASCII character set. - 2 - Decrements the selected character down the ASCII character set. - 3 - Moves the cursor one position to the right to select a character. - 4 - Exits service aid without saving changed characters. - 4 and 5 - Pressing both switches simultaneously saves new characters and exits the service aid; the message SAVING appears. - 5 - No function. 8. If the Device ID is TSZ07, exit the service aid. If the Device ID is M995, change it to DEC, and save the change before you exit the service aid. Installation Notes E-3 _E._1._3 _G_r_a_p_h_i_c_s _D_r_i_v_e_r_s If you set the ROM to use the serial line as the console, and there is a graphics board in the TURBOchannel option, the X server will not start up because the driver has not been initiated. This is because the graphics driver assumes it has been set up for the graphics console by the time it attempts to attach. To avoid this, do not use the serial line console when you have a graphics device. Use the graphics console. _E._1._4 _R_Q_D_X _Q-_b_u_s _C_o_n_t_r_o_l_l_e_r _J_u_m_p_e_r _S_e_t_t_i_n_g_s If there are multiple RQDX controllers and the RQDX2 is the last controller on the bus, ignore the jumper configuration stated in the hardware manual. The jumper setting should be 1, not 4 as stated in the hardware manual. _E._1._5 _T_K_5_0 _a_n_d _T_K_7_0 _T_a_p_e _U_s_a_g_e When a blank TK50 or TK70 tape is inserted into the drive, calibration marks are written on the tape. These calibration marks determine the tape format. The tape format can only be changed by a bulk tape eraser. When using TK50 and TK70 tapes, the following rules apply: +o A TK50 formatted tape can be written and read on a TK50 drive. +o A TK50 formatted tape can be read but not written on a TK70 drive. The TK70 drive considers TK50 tapes to be hardware write-protected. +o A TK70 formatted tape can be written or read on a TK70 drive. +o A TK70 tape is completely unusable on a TK50 drive. Violation of these rules may result in command failure and drive error log messages. E-4 Installation Notes _E._1._6 _D_a_t_a _C_o_r_r_u_p_t_i_o_n _f_r_o_m _P_r_o_g_r_a_m_s _A_c_c_e_s_s_i_n_g _T_a_p_e _U_n_i_t_s The TK70, TS11, and TU81 tape units require the data buffers to be aligned on a machine word boundary. Data corruption can occur if the data buffer boundaries are not aligned properly. When the buffer is declared as a local variable, the buffer will be on the user's program stack; alignment is therefore not ensured and may cause data corruption. To ensure that the data buffer is correctly aligned, all programs that access tapes must declare the data buffer as a type static or as a global variable. The compilers then assure proper alignment of the data buffer and data. _E._1._7 _R_e_q_u_i_r_e_d _S_w_i_t_c_h _S_e_t_t_i_n_g_s _f_o_r _T_S_V_0_5 _T_a_p_e _D_r_i_v_e The switch settings for the TSV05 controller (M7196 and M7206) as described in the manuals _T_S_V_0_5 _T_a_p_e _T_r_a_n_s_p_o_r_t - _P_o_c_k_e_t _S_e_r_v_i_c_e _G_u_i_d_e (EK-TSV05-PS-005) and _T_S_V_0_5 _T_a_p_e _T_r_a_n_s_p_o_r_t _S_u_b_s_y_s_t_e_m - _T_e_c_h_n_i_c_a_l _M_a_n_u_a_l (EK-TSV05-TM-004) are incorrect. The factory switch setting information for the M7206-PA module in the manuals lists switch E61-9 OFF. This factory switch setting does not work on ULTRIX systems running Version 3.0 and higher. The tape device always appears off line to the operating system if the switch is set to OFF. _E._1._8 _I_n_s_t_a_l_l_i_n_g _f_r_o_m _a _T_E_1_6 _T_a_p_e _D_r_i_v_e During installation, you are asked to identify the software distribution device. If you are using a TE16 tape drive, choose the TU77 tape drive option. When your system is booted, the TE16 will be identified correctly. _E._1._9 _P_o_w_e_r_i_n_g _D_o_w_n _a _T_U_8_1 _T_a_p_e _D_r_i_v_e On the ULTRIX operating system, you cannot power down a controller while it is on line. If you attempt to power down or pull a controller while it is on line, problems may occur. Problems have been encountered because TU81 and TU81+ tape drives contain the TMSCP server logic. If you must power down a TU81 drive, use the following steps: Installation Notes E-5 1. Disconnect the TU81+ white cable, which connects the drive unit to the back plane of the host. 2. Power down the tape drive. 3. Attend to the tape unit as needed. 4. Power up the tape device. 5. Reconnect the TU81+ white cable. _E._1._1_0 _T_U_8_1 _T_a_p_e _D_r_i_v_e _D_i_s_p_l_a_y_i_n_g _F_a_u_l_t _L_i_g_h_t A problem in the TU81 tape unit can cause data transfers to fail. All users who have TU81 tape units should contact a customer service representative to ensure that FCO number TU81 R-005 is applied and that the revision level is up to at least D1. Units that do not have this FCO applied will experience hard errors logged and the unit's controller fault light will light. _E._1._1_1 _M_S_C_P _D_i_s_k_s _R_e_m_a_i_n _O_f_f _L_i_n_e _I_f _S_w_i_t_c_h_e_d _O_f_f _L_i_n_e _W_h_i_l_e _i_n _U_s_e If a disk unit served by the MSCP driver (any RA disk) is switched off line while operations are in progress, the disk cannot be brought back on line. If this happens, in-progress and subsequent data transfer operations to the unit will fail. The system call that failed will return an EIO error. This condition can be cleared only by setting the unit back on line and rebooting the system. _E._1._1_2 _E_i_g_h_t-_B_i_t _T_e_r_m_i_n_a_l _D_r_i_v_e_r _S_u_p_p_o_r_t You must set up your hardware and software properly if you intend to use a terminal in full eight-bit mode. Refer to the _g_e_t_t_y_t_a_b(5) reference page for instructions on how to enable logins on terminal lines that require eight-bit characters. The _p_8 and _p_d flags have been added to _g_e_t_t_y_t_a_b to facilitate the use of eight-bit characters. Digital's VT100 series terminals are capable of displaying only the lower half of the DEC Multinational Character Set. Standard seven-bit ASCII characters are included in the lower half of the Multinational Character Set and ISO-8859/2. E-6 Installation Notes Digital's VT200 and VT300 series terminals are capable of displaying the full DEC Multinational Character Set and ISO-8859/2. However, they do not display eight-bit characters when they are in VT100 mode. To determine the current terminal mode, call up the terminal's Set-Up Directory menu and select the _G_e_n_e_r_a_l setup option. For example, to change your VT220 terminal set up into eight-bit mode, follow these steps: 1. Call up the terminal's setup menu by pressing the Set-Up (F3) key. Select the _G_e_n_e_r_a_l menu option. 2. Move to the field that allows you to select the terminal mode. Select the option _V_T_2_0_0 _M_o_d_e, _7 _B_i_t _C_o_n_t_r_o_l_s. 3. Select the _T_o _D_i_r_e_c_t_o_r_y option to return you to top level. 4. Call up the _C_o_m_m menu. Select the _8 _B_i_t_s, _N_o _P_a_r_i_t_y option. 5. Exit from setup mode by pressing the Set-Up key again. Note that when you change a VT200 or VT300 series terminal from VT100 mode, the F11 key no longer represents the escape key. Refer to your terminal's installation guide for a complete description of terminal setup. The DECwindows terminal emulator, _d_x_t_e_r_m can also be set up for use with eight-bit characters. In this case, the terminal mode must be set to _V_T_3_0_0 _M_o_d_e, _7-_b_i_t _C_o_n_t_r_o_l. Select the _C_u_s_t_o_m_i_z_e menu, then the _G_e_n_e_r_a_l menu. _E._2 _B_o_o_t_i_n_g _E._2._1 _B_o_o_t_i_n_g _M_S_C_P-_t_y_p_e _D_i_s_k _D_r_i_v_e_s For MSCP-type disk drives, the wait for critical system devices such as _r_o_o_t, _s_w_a_p, and _d_u_m_p to become available may take up to 2 minutes. After waiting for 1 minute, a status message appears on the console that indicates that you must wait for a specified device. Installation Notes E-7 _E._3 _C_o_n_f_i_g_u_r_a_t_i_o_n _E._3._1 _U_n_s_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s To install the unsupported subsets from tape, load the unsupported tape. To install subsets from your CD-ROM distribution, mount the _c partition of the CD-ROM on /_m_n_t and load subsets from /_m_n_t/_R_I_S_C/_U_N_S_U_P_P_O_R_T_E_D or /_m_n_t/_V_A_X/_U_N_S_U_P_P_O_R_T_E_D, as is appropriate. _E._3._2 _T_h_e _s_e_t_l_d _C_o_m_m_a_n_d _w_i_t_h _t_h_e -_v _F_u_n_c_t_i_o_n The _s_e_t_l_d command with the -_v function does not invoke _f_v_e_r_i_f_y. This function checks to see if the subset is installed. If the subset is installed and it contains an Installation Verification Procedure (IVP), the IVP is executed. _E._3._3 _L_a_y_e_r_e_d _P_r_o_d_u_c_t_s _a_n_d _t_h_e _s_e_t_l_d _C_o_m_m_a_n_d Some layered products will not install because of an incompatibility with the _s_e_t_l_d command. When you try to install them, these products will issue an error message and exit before the _s_e_t_l_d menu is presented. To install these products, set the _S_T_L__N_O_A_C_T_M environment variable to 1. On VAX and RISC systems, _c_s_h users should enter the following command as _r_o_o_t: # _s_e_t_e_n_v _S_T_L__N_O_A_C_T_M _1 Users of all other shells should enter this command: # _S_T_L__N_O_A_C_T_M=_1; _e_x_p_o_r_t _S_T_L__N_O_A_C_T_M Once you have set this variable, the product will be installed correctly. Before installing any more products, unset the variable. On VAX and RISC systems, _c_s_h users should enter the following command as _r_o_o_t: # _u_n_s_e_t_e_n_v _S_T_L__N_O_A_C_T_M Users of all other shells should log out of the system and log back in before installing more software. E-8 Installation Notes _E._3._4 _O_p_t_i_o_n_a_l _R_e_m_o_v_a_l _o_f _t_h_e _K_e_r_n_e_l _O_b_j_e_c_t _S_u_b_s_e_t The ULTRIX operating system contains a kernel object subset, which allows full debug capabilities using the _d_b_x debugger. In order to save space, you can remove your kernel object subset from your installed system. On RISC processors, enter the following command: # /_e_t_c/_s_e_t_l_d -_d _U_D_T_B_I_N_4_4_0 On VAX processors, enter the following command: # /_e_t_c/_s_e_t_l_d -_d _U_L_T_B_I_N_4_4_0 It is important that you understand some of the trade-offs you make by removing this subset. If you need to apply a kernel patch to your environment, you will need to reinstall the kernel object subset. This might require that you remove other system or user environments to make room for its installation. (This assumes that the space made available after removing the subset was used for another purpose.) In general, any time you need to build a kernel for your system, the subset will need to be reinstalled. This could be for a simple need to modify some hardware or software configuration parameter in the system's configuration file. We recommend that this procedure not be followed routinely. Rather, it is intended to solve space problems on smaller systems with smaller system disks. If you choose to remove the kernel object subset, wait until the system is properly configured and proven for some reasonable period of time. _E._3._5 _I_n_s_t_a_l_l_i_n_g _t_h_e _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n _S_u_b_s_e_t_s Internationalization software has been divided into two subsets: +o UDTINTLPGMR440 and UDTINTLRT440 (RISC) +o ULTINTLPGMR440 and ULTINTLRT440 (VAX) If you plan to use the Internationalization software, you must install both subsets. Installation Notes E-9 _E._3._6 _I_n_i_t_i_a_l _S_y_s_t_e_m _L_o_a_d _U_s_i_n_g _R_I_S During a base system installation using RIS, if a problem occurs when contacting the RIS server or with network traffic, an error in the _s_e_t_l_d utility causes the installation procedure to state that all mandatory subsets have been installed successfully and the following message is displayed: The installation software successfully installed the mandatory software subsets. However, it failed to install other parts of the supported software subsets. You can continue with the installation and install the other supported software subsets at a later time using the setld utility or, you can request that the installation software again try to install these supported software subsets. Select one of the following options: 1) Continue with the installation 2) Try to re-install supported software subsets Enter your choice [1]: In order to complete the installation, check the network/RIS server status with the system administrator. If the problems are corrected, type 2 in response to the query and the installation process will continue. _E._3._7 _D_i_s_p_l_a_y _S_e_r_v_e_r _I_n_s_t_a_l_l_a_t_i_o_n _S_c_r_i_p_t The server installation script loads all servers but then removes all servers not relevant to the hardware you are installing on. _E._3._8 _U_L_T_R_I_X _W_o_r_k_s_y_s_t_e_m _F_o_n_t_s _O_p_t_i_o_n_a_l _i_n _D_M_S _I_n_s_t_a_l_l_a_t_i_o_n_s ULTRIX Worksystem Software fonts are not automatically installed on a diskless RISC or VAX workstation when the Diskless Management Services (DMS) utility is used for installation. Because all fonts are contained in optional subsets, when you install only the mandatory subsets, the X server will not come up because no fonts are available to it. Therefore, when doing a DMS installation, you must install a font for the server to use. _E._3._9 _R_e_b_u_i_l_d_i_n_g /_g_e_n_v_m_u_n_i_x _A_f_t_e_r _a_n _U_p_g_r_a_d_e _I_n_s_t_a_l_l_a_t_i_o_n The generic kernel image created by the installation process as /_g_e_n_v_m_u_n_i_x can be useful at a later time. E-10 Installation Notes For example, it can be useful when you add new hardware such as a backup kernel image, and also for Prestoserve crash recovery when the system disk is lost. To save the generic kernel image for later use, rebuild the generic kernel image after you perform the upgrade installation, but before you install any layered product. See the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S for information on how to perform this upgrade. To rebuild the generic kernel on a RISC system: # /_e_t_c/_d_o_c_o_n_f_i_g -_c _G_E_N_E_R_I_C # _c_p /_s_y_s/_M_I_P_S/_G_E_N_E_R_I_C/_v_m_u_n_i_x /_g_e_n_v_m_u_n_i_x # _r_m -_r_f /_s_y_s/_M_I_P_S/_G_E_N_E_R_I_C To rebuild the generic kernel on a VAX system: # /_e_t_c/_d_o_c_o_n_f_i_g -_c _G_E_N_E_R_I_C # _c_p /_s_y_s/_V_A_X/_G_E_N_E_R_I_C/_v_m_u_n_i_x /_g_e_n_v_m_u_n_i_x # _r_m -_r_f /_s_y_s/_V_A_X/_G_E_N_E_R_I_C _E._3._1_0 _B_I_N_A_R_Y _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e _a_n_d _s_l_i_p The BINARY configuration file in /_s_y_s/_c_o_n_f/_m_i_p_s contains the pseudodevice definition for _s_l_i_p. However, the files necessary to build a kernel with _s_l_i_p are in the UDXINET430 subset, Unsupported TCP/IP Networking Util Extension. If you want the _s_l_i_p program, you must install the UDXINET430 subset from the Unsupported Kit. If you do not want the program, you must delete its pseudodevice definition from the configuration file. The line to delete is: pseudo-device sl _E._3._1_1 _V_e_c_t_o_r_s To use vector processors on a system that supports vector processors, 6000-4xx, 6000-5xx, or 9000, you must add the following lines to the configuration Installation Notes E-11 file: options VECTORS pseudo-device vectors Use the following syntax format for the options line: options VECTORS = In the previous example, is the maximum number of vector processes allowed. If a number is not specified, the maximum defaults to the MAXUPROC divided by 10. _E._3._1_2 _U_s_e _o_f _t_h_e _h_s_c? _T_o_k_e_n _i_n _t_h_e _S_y_s_t_e_m _C_o_n_f_i_g_u_r_a_t_i_o_n _F_i_l_e The _c_o_n_f_i_g utility incorrectly handles the hsc? token in the system configuration file. Use the mscp token in place of the hsc? token to indicate a wildcard connection or, completely specify the hsc controller. For example: ra0 at hsc? drive 0 The preceding line can be replaced with the following to match any hsc: ra0 at mscp drive 0 Or, if connected to hsc0, the line can be replaced with the following: ra0 at hsc0 drive 0 E-12 Installation Notes