Installation Instructions: DEC FUSE Version 4.0 for Digital UNIX Systems Order Number: AV-PX06H-TE This installation document contains the information you need to install DEC FUSE Version 4.0 on a Digital UNIX system. Please read this document before installing FUSE. FUSE Kit Summary Product name: DEC FUSE Version 4.0 for Digital UNIX Operating system: Digital UNIX Version 4.0 or for Alpha Systems or higher Required Hardware Alpha system, workstation monitor or terminal, and the following media drives depending on your distribution kit: Required Hardware Drives If your distribution kit is on... You need this hardware drive... TLZ04 tape TLZ04 or TLZ06 tape drive CD-ROM optical disk RRD42 or RRD43 optical disk drive Required Software Required Subsets Contents Subset Name Digital UNIX Base System OSFBASE400 or higher Digital UNIX Networking Utilities OSFCLINET400 or higher Document Preparation Software OSFDCMT400 or higher Reference Pages: Programming OSFMANOP400 or higher Software Development Tools and Utilities OSFSDE400 or higher Standard Header Files OSFINCLUDE400 or higher Standard Programmer Commands OSFPGMR400 or higher (Software Development) The following table lists the FUSE subsets and the optional Japanese Language Support subsets along with sizes: Size of FUSE Subsets Contents Subset Name Disk Space FUSE V4.0 System FUSBASE400 67,600 KB in /usr/opt Online Manual Pages FUSMAN400 80 KB in /usr/opt FUSE V4.0 System FUSBASEJPN400 7,900 KB in /usr/opt (Japanese Support) FUSE Online Manual Pages FUSMANJPN400 150 KB in /usr/opt (Japanese Support) If you installed FUSE on a version of Digital UNIX that preceded V4.0D, you will need to reinstall FUSE after installing Digital UNIX V4.0D to take full advantage of FUSE features. Optional Software You can install all the necessary Ladebug subsets as part of the Digital UNIX operating system installation. The Code Manager requires either the GNU Revision Control System subset or the Source Code Control System subset. The Example files and the Online Tutorial require the GNU Revision Control System subset. Platform-Specific Optional Subsets Contents Name CDE Desktop Environment OSFCDEDT 400 or higher GNU Emacs OSFEMACS400 or higher GNU Revision Control System OSFRCS400 or higher Ladebug Debugger OSFLDBBASE400 or higher Ladebug Debugger Window Interface OSFLDBGUI400 or higher Ladebug Debugger Release Notes OSFLDBDOC400 or higher Source Code Control System OSFSCCS400 or higher Worldwide Mule IOSWWMULE400 or higher FUSE Base V4.0 System (Japanese support) FUSBASEJPN400 Japanese Base System (Japanese IOSJPBASE400 or higher support - Operating System) Online Manual Pages (Japanese support) FUSMANJPN400 Printer Support FUSPRNT400 Digital Extended Math Library (DXML) XMDMAN Reference Pages** ** The Digital Extended Math Library (DXML) Reference Pages subset is useful only if you are porting a mathematically intensive application to Digital UNIX. It allows you to use the DXML Lookup functions in the Porting Assistant to identify functions (subroutines for Basic Linear Algebra, Linear and Eigen System Solvers, Sparse Linear System Solvers, and Signal Processing) in the Library by keyword. The functions in the library constitute a set of mathematical subroutines optimized for the Alpha platform. To install the DXML Reference Pages, select the optional DXML Reference (man)Page subset during an installation of the Digital Extended Math Library kit. FUSE Installation Summary The following steps provide a summary of the steps for installing FUSE: 1. Back up your system disk before installing any software. Use the backup procedures established at your site. For details on performing a system disk backup, refer to your system's documentation. 2. Determine the type of installation you are doing. If you are performing a local installation of FUSE, mount the CD-ROM containing the FUSE kit. If you are installing the FUSE subsets from a Remote Installation Services (RIS) server area of a remote system to your local system, first check with your site system administrator to make sure that: o A FUSE kit is installed in the RIS server area and is available for use. o Your system is registered as a RIS client. If FUSE subsets are available on a RIS server system, you need the name of that system to start the installation procedure. See "Installing into a RIS Server Area." 3. Log in as superuser (login name root) to the system where you are installing FUSE. 4. Set your path to include /usr/sbin: # PATH=/usr/sbin:$PATH # export PATH 5. Determine if you have enough available disk space for the installation and add more if necessary. (See "Increasing Disk Space for FUSE Installation" for details on how to do this.) 6. Register the software licenses. (You can register the software licenses either during or after FUSE installation.) The FUSE software installation includes the following products: DEC FUSE Version 4.0, DEC FUSE C++ Support Version 4.0. You need to purchase and register a license for each FUSE product that you will use. When you purchase a license for a FUSE product, you receive a License Product Authorization Key (PAK) that you must register in the License Database before you can use FUSE, including the C++ support, on your system. At the superuser prompt, edit an empty PAK template with the lmf register command and include all of the information on your PAK: # lmf register The PAK template is displayed on your screen with the default editor (set by the EDITOR environment variable) activated. Use the editor commands to move to each field in the template and enter the PAK data. After you complete PAK templates for all FUSE products, use the lmf reset command to update the License Database (LDB): # lmf reset For more information on FUSE licenses and PAKs, see "Registering a FUSE License." 7. Make sure /usr/tmp and /tmp have read and write permissions for all FUSE users. Without read and write permissions on these directories, FUSE will not start. 8. Determine whether your compiler requirements have been met. (See "Determining Language Compiler Requirements.") 9. If necessary, delete old FUSE kits. Use the setld -i command to list the subsets installed on your system and check for the presence of any subset with a name that starts with FUS (or LDB in the case of Ladebug). For example: # /usr/sbin/setld -i | grep FUS If any of these subsets exist, they are old versions that must be deleted. To delete a subset, use the setld -d command. For example, to delete the Version 3.1 base subset, enter the following command: # /usr/sbin/setld -d FUSBASE310 10. Enter the setld command to specify the -l (load) option and one of the following: o The full pathname of the directory on the CD-ROM containing the FUSE software: # setld -l `/dev/directory-name' o The full pathname of the tape drive containing the FUSE software: # setld -l `/dev/tape-drive-name' 11. (This step applies only to tape devices) The installation procedure displays the following information and prompt: Please make sure your installation media is mounted and on-line. Are you ready (y/n)? After the tape drive indicates online status, enter y. 12. The installation script lists the subset choices: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) DEC FUSE V4.0.0 Man Pages Japanese support 2) DEC FUSE V4.0-0 Man Pages 3) DEC FUSE V4.0-0 for Digital UNIX Japanese support 4) DEC FUSE V4.0-0 for Digital UNIX --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): Enter the numbers of the subsets to install and press Return. 13. The installation script prompts you to confirm your subset selections. Enter y and press Return to confirm. The installation script installs the software and displays messages describing the installation. 14. The installation procedure searches for emacs, XEmacs, and the Mule Editor. You can change the specified location or provide one if the installation procedure fails to find an editor, for example: Found /usr/local/bin/xemacs Enter `carriage return' to accept this specification, or specify a new one: /usr/local/bin/editors/xemacs To change or provide a location for an editor after installation, edit the file /usr/bin/fuse. Modify the definitions of the FUSE_EMACS, FUSE_XEMACS, or FUSE_MULE environment variables or set the evironment variable definitions directly. 15. If necessary, delete any files in ~'home'/.fuse-defaults. This is necessary if you are upgrading from a previously installed version of FUSE and had customized options. Verifying FUSE Installation After you install FUSE, you can run the installation verification script by entering the following command: # setld -v FUSBASE400 The script displays the FUSE Control Panel. To exit, click on the Projects menu and choose the Exit FUSE menu item. The script exits FUSE and displays a message stating that the installation has been verified. .Xdefaults Modifications for Monochrome Displays Users with monochrome displays must edit the .Xdefaults file in their home directories to include the MonochromeDefaults resource file. Follow these steps: 1. Login into the host system where FUSE is installed. 2. Enter the following csh command to get the FUSE pathname on that system (the value of the environment variable FUSE_TOP): % grep FUSE_TOP= /usr/bin/fuse The system will display the following output, where `fuse-path' is the FUSE pathname: FUSE_TOP='fuse-path' For example: FUSE_TOP=/usr/opt/FUS400 3. Insert the following lines in the .Xdefaults file in your home directory: #ifndef COLOR #include "`fuse-path'/rundata/resources/MonochromeDefaults" #endif These settings must be in effect for the FUSE Call Graph Browser, Builder, and C++ Class Browser tools to start correctly. Upgrading Versions of FUSE Preceding V3.0 As part of your installation of Digital UNIX Version 4.0, you may have installed the Ladebug Debugger (Ladebug Window Interface subset). If you are installing FUSE Version 4.0 to replace an existing version of FUSE that precedes V3.0, you need to take some steps to ensure that both the existing installation of the Ladebug Debugger and FUSE Version 4.0 interact properly. There are several Ladebug files that you need to save before deleting your installed version of FUSE. You can then copy the files back after you delete your installed version of FUSE. Alternatively, you can deinstall and reinstall Ladebug after deleting FUSE. These are the Ladebug files: /usr/lib/X11/help/decladebug/DEBUG /usr/lib/X11/help/decladebug/DEBUGUI /usr/lib/X11/uid/decladebuguil /usr/lib/X11/uid/decladebugcustuil /usr/lib/X11/app-defaults/decladebugresource /usr/bin/X11/dxdecladebug Note that this is not necessary when you upgrade from versions later than FUSE Version 2.1A. Registering a FUSE License All FUSE products, including optional support products, are shipped on the same media and all are installed when you run the FUSE installation. You need to purchase a license for the FUSE base product and each optional FUSE product that you will use. The FUSE software includes the following: o DEC FUSE Version 4.0 (base system) o DEC FUSE C++ Support Version 4.0 (option) DEC FUSE supports the License Management Facility (LMF). A License Product Authorization Key (PAK) must be registered in the License Database (LDB) for you to use FUSE on a newly licensed node. A PAK must also be registered for each optional FUSE product that you will enable, for example, DEC FUSE C++ Support. The PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. To register a license under a Digital UNIX system, first log in as superuser. You can register your PAK using the command line or a graphical interface. To invoke the Configuration Checklist from the command line (provides access to the graphical interface), enter the following command: # checklist If you use the command line, you have a choice of two ways to perform the PAK registration in the License Database (LDB): o Before installing FUSE: At the superuser prompt, edit an empty PAK template with the lmf register command and include all of the information on your PAK: # lmf register o After installing FUSE: At the superuser prompt, edit the partially completed PAK template in /usr/var/adm/lmf/PRODUCT_NAME with the lmf register command to add your unique PAK information. Substitute as needed the left-angle bracket character below: # lmf register - `left-angle bracket'/usr/var/adm/lmf/PRODUCT_NAME After you register your license, enter the lmf reset command to copy the license details from the License Database (LDB) to the kernel cache: # lmf reset For complete information on using the License Management Facility, see the Software Licensing Management manual in the Digital UNIX documentation set or the lmf(8) manual page. Determining Language Compiler Requirements FUSE provides a software development environment for Ada, C, C++, FORTRAN and Pascal. The FUSE Builder and (for applications written in Ada, C, or C++) the Cross Referencer, Call Graph Browser, and optional C++ Class Browser require that the appropriate language compiler be installed on the system where FUSE is installed. This is because each of these tools may invoke the appropriate compiler to do some level of processing. For example, when the Cross Referencer is invoked, the Cross Reference Database Manager automatically creates a database by scanning the files associated with the specified target. However, prior to scanning for cross-reference information, the Cross-Reference Database Manager invokes the C preprocessor. For C programs, by default, FUSE uses the C compiler and the cc compiler command for preprocessing. You can install compilers either before or after you install DEC FUSE. To use DEC Ada with FUSE, you must install DEC Ada for Digital UNIX To use C with FUSE, by default, you must have a C compiler installed. Also, the cc compiler command must be found in your PATH environment variable. A C language compiler is installed by default with the Digital UNIX operating system; however, to use DEC C++, you must install DEC C++. To use DEC C++ with FUSE, you must do the following: o Register the PAK for the optional DEC FUSE Support for DEC C++ o Install DEC C++ for Digital UNIX By default, the cxx compiler command must be found in your PATH environment variable. To use FORTRAN with FUSE, by default, you must have a FORTRAN compiler installed. Also, the f77 or f90 compiler command must be found in your PATH environment variable. To use DEC FORTRAN you must install DEC FORTRAN. To use Pascal with FUSE, by default, you must have a Pascal compiler installed. Also, the pc compiler command must be found in your PATH environment variable. To use DEC PASCAL you must install DEC PASCAL. You do not need additional PAKs to use FUSE with DEC FORTRAN, DEC PASCAL, or DEC Ada. Increasing Disk Space for FUSE Installation To determine the current amount of free space for a directory path: 1. Log in to the system where you plan to install FUSE. 2. Check which file systems are mounted and where they are by displaying the /etc/fstab file. For example: # more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: In this example, /usr (mounted to /dev/rd0g) is the only mount point that affects where FUSE files will reside; the system has only one local disk drive and the /usr file system resides in the g partition of the disk on that drive. 3. Enter the df command to determine total space and free space for the file system where FUSE files will reside. Based on the preceding display of the /etc/fstab file, which shows that only /usr is a mount point, you will only need to inspect free space in the /usr file system. # df -k /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted On /dev/rd0g 122598 54447 55892 49% /usr This display indicates that there are 55,892 KB free. The FUSE installation procedure creates the directory /usr/opt/FUSE400, if it does not already exist, and loads files into subordinate directories. If you have insufficient disk space for the FUSE subsets and know that you have additional space on alternative disks or disk partitions for your system, you can take the following steps before installing FUSE: 1. Log in as superuser (login name of root). 2. Create the directory /usr/opt/FUS400. 3. Specify in the /etc/fstab file that the newly created directory is a mount point to new disk partitions where there is additional space. 4. Enter the mount /usr/opt/FUS400 command to have the new mount point take effect. Stopping the Installation You can stop the installation procedure at any time by pressing Ctrl+C. However, files created up to that point are not deleted. You must delete these files interactively. Error Recovery If errors occur during the installation, the system displays error messages. If the installation fails due to insufficient disk (file system) space, the installation procedure displays the following message: fitset: filesystem /usr needs xxx kbytes more to install the software specified An error can also occur during the installation if: 1. The operating system version is incorrect. 2. The Networking Utilities subset is not installed. For more information about error messages generated during installation, see your system's documentation on system messages, recovery procedures, and software installation. If you are notified that any errors occurred, take the appropriate action as described in that documentation. Installing into a RIS Server Area You can install FUSE with the Remote Installation Services (RIS) utility into a RIS server area on a Digital UNIX system. You do not use the setld command for this operation. To install FUSE from a RIS server to a RIS client, you must first install FUSE in your RIS server environment. See your RIS manager if FUSE is not already installed on the RIS server. To install FUSE subsets that reside in a /var/adm/ris distribution area on a remote system, start the installation procedure as follows: 1. Log in as superuser (login name root) to the system where you are installing FUSE. 2. Enter the following command to ensure that you are at the root (/) directory: # cd / 3. Enter a setld command that requests the load function and identifies the system where the FUSE subsets are located. For example, if you are loading the FUSE subsets from a RIS distribution area on node bigsys, enter the following command: # setld -l bigsys: RIS then displays a menu that lists all the software subsets available to you and prompts you to enter the numbers of the ones you want to load. Note that the numbers of the FUSE subsets vary from system to system, depending on what products are available in the RIS area and how many subsets each has. 4. Enter the numbers of the FUSE subsets that you want to install and press Return. The setld utility installs FUSE on the client machine. RIS Disk Space Requirements The disk space requirements in the Installation Instruction Sheet do not apply if you are installing FUSE into a RIS server area. In this case, you do not create FUSE file systems but use the RIS utility to extract files from media. Furthermore, the FUSE files are compressed during the extraction process and require the following amounts of disk space to be available in the RIS server area: FUSE Version 4.0 - 27,500 KB Sample RIS Installation The following sample session describes how to add the FUSE product to the ris0.alpha area: 1. Log in as the superuser (login name of root). 2. Enter the following command to invoke the RIS utility: # /usr/sbin/ris 3. Select the Install Software option from the RIS main menu by entering i at the prompt: *** RIS Utility Main Menu *** a) ADD a client d) DELETE software products i) INSTALL software products l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software products in remote installation environments x) EXIT Enter your choice: i 4. Choose option 2 from the RIS Software Installation Menu: RIS Software Installation Menu: 1) Install software into a new area 2) Add software into an existing area 3) Return to previous menu Enter your choice: 2 5. A list of available environments appears from which you might select ris0.alpha: You have chosen to add a new product into an existing environment. Select the remote installation environment: 1 /usr/var/adm/ris/ris0.alpha (list of available products for environment) . . . 2 /usr/var/adm/ris/ris0.vax (list of available products for environment) . . . Enter your choice: 1 6. The installation procedure then prompts you for an input device name: Enter the device special name or mount point of the distribution media, for example, /dev/rmt0h: /dev/rmt0h 7. If your distribution media is tape, a message appears asking you to confirm that the tape is ready and on line. If it is, enter y. Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? y Positioning Tape The installation procedure installs all subsets on the tape into the RIS area. 8. After the subsets are installed, the following message appears: Media extraction complete. 9. When the RIS main menu appears, choose the menu item (Modify Client) to add FUSE to the list of products that RIS clients can install. Because FUSE Version 4.0 contains multiple subsets, you will see different titles in the RIS product area depending on which subsets you install. When you install into the RIS area, you should install all subsets in the Version 4.0 kit. Copyright Digital Equipment Corporation 1997. All rights reserved.