11    Creating DMS Environments on the DMS Server

This chapter describes how to use the dmu utility to add software to a DMS environment and how to configure the environment. The information in this chapter describes how to:

11.1    Compatibility Between the DMS Server and the DMS Client

If you are installing Tru64 UNIX Version 4.0F or higher into a DMS environment and the DMS server is running a previous version of the operating system, you must perform the following procedure as superuser on the DMS server:

  1. If your distribution media is CD-ROM, enter a mount command similar to the following: 

    
# mount -rd /dev/rz4c/mnt

    This example uses a CD-ROM drive that is unit 4 and specifies /mnt as the mount point; if your drive is a different unit, substitute the device special file name for that unit. If you are uncertain of your CD-ROM's unit number, use the file command, specifying the raw device, as follows: 

    # file /dev/rrz*c
 
/dev/rrz1c: char special (8/1026) SCSI #0 RZ25  disk #8  (SCSI ID #1)
/dev/rrz2c: char special (8/2050) SCSI #0 RZ25  disk #16 (SCSI ID #2)
/dev/rrz3c: char special (8/3074) SCSI #0 RZ25  disk #32 (SCSI ID #3)
/dev/rrz4c: char special (8/4098) SCSI #0 RRD43 disk #64 (SCSI ID #4)
 

    The CD-ROM device corresponds to an RRD device, in this example RRD43.

  2. To update DMS on the server, assuming the distribution media is mounted at /mnt, enter the following: 

    
# /mnt/isl/utilupdate -d -m /mnt

This command copies any files in /usr/sbin that would be overwritten to files with a *.pre-V4.0F suffix, for example: /usr/sbin/setld is copied to /usr/sbin/setld.pre-V4.0F.

When the utilupdate script completes, this RIS server can serve a DMU client. Appendix C describes the utilupdate utility.

If the utility finds existing *.pre-V operating system files on your system, no copies are made. If the server is already running the current version of the operating system (or higher), a confirmation is displayed and no copies are made.

11.2    Installing Software in a New DMS Environment

You must install and configure all the software you plan to use in a DMS environment before you can add clients to share the environment.

Perform the procedures described in this section to install the software into a new dmsN .alpha environment. Repeat the installation procedures for each dmsN .alpha environment you plan to set up.

  1. Insert the operating system distribution CD-ROM into the drive, then execute a command similar to the following to mount the CD-ROM: 

    # mount -rd /dev/rz4c /mnt

    This example mounts a CD-ROM drive that is device 0 on the mount point /mnt. If your drive is a different device, substitute the correct device name. The mount point does not have to be /mnt.

    If you are uncertain of your CD-ROM drive's unit number, use the file command as follows: 

    # file /dev/rrz*c
/dev/rrz1c: char special (8/1026) SCSI #0 RZ25 disk #8  (SCSI ID #1)
/dev/rrz2c: char special (8/2050) SCSI #0 RZ25 disk #16 (SCSI ID #2)
/dev/rrz3c: char special (8/3074) SCSI #0 RZ25 disk #24 (SCSI ID #3)
/dev/rrz4c: char special (8/4098) SCSI #0 RZ25 disk #32 (SCSI ID #4)
#

    Note

    Additionally, you can use a Network File System (NFS) mount point to install software from a Remote Installation Services (RIS) area or operating system distribution CD-ROM from another processor. See Section 4.4 for more information about using an NFS mounted RIS area.

  2. Invoke the dmu utility by entering the following command at the root system prompt: 

    
# /usr/sbin/dmu

    The DMU Main Menu is displayed: 

    *** DMU Main Menu ***
 
Choices without key letters are not available.
 
     ) ADD a client
     ) CONFIGURE software environments
     ) DELETE software environments
    i) INSTALL software environments
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
     ) SHOW software environments
    x) EXIT
 

    If this is the first time you have accessed dmu, there are no DMS software environments installed. The only option you have is to install software into an environment or to exit from the utility.

  3. Choose the INSTALL software environments option by entering i at the prompt. 

    
Enter your choice: i

  4. The INSTALL software environments option displays an installation menu which lists the installation options that are available. Choose option 1, Install software into a new area: 

    DMU Software Installation Menu:
 
        1) Install software into a new area
        2) Add software to an existing area
        3) Perform configuration phase on an existing area
        4) Return to previous menu
 
Enter your choice: 1
You have chosen to establish a new remote dataless environment.

  5. A prompt asks for the full pathname of the device special file name or the path of the directory where the software is located. 

    Enter the device special file name or the path of the directory where
the software is located (for example, /mnt/ALPHA/BASE): 
/mnt/ALPHA/BASE

  6. The dmu utility lists the mandatory software subsets that are installed automatically (the mandatory subsets displayed vary depending upon the type of hardware you are using): 

    *** Enter subset selections ***
 
The following subsets are mandatory and will be extracted automatically
unless you choose to exit without extracting any subsets:
 
      * Base System
      * Base System - Hardware Support
      * Java V1.1.5 Environment
      * Tcl Commands
      * Tk Toolkit Commands
      * Hardware Kernel Header and Common Files
      * Hardware Kernel Modules
      * Kernel Header and Common Files
      * Standard Kernel Modules
      * CDE Mail Interface
      * Basic Networking Services
      * NFS(tm) Utilities
      * Local Printer Support
      * Compiler Back End
      * Base System Management Applications and Utilities
      * Basic Networking Configuration Applications
      * Graphical Base System Management Utilities
      * Graphical Print Configuration Application
      * Graphical System Administration Utilities
      * NFS(tm) Configuration Application
      * Basic X Environment
      * CDE Desktop Environment
      * CDE Minimum Runtime Environment
      * Old X Environment
      * Netscape Navigator Gold V3.0
 

  7. The system then displays the first screen of optional software subsets. The optional subsets displayed vary depending upon the type of hardware you are using. At each screen of subsets you can enter the number that corresponds to the subset you want or you can press the Return key to display the next screen of subsets. At the bottom of each subset screen, you will see the following prompt: 

    ---MORE TO FOLLOW---
Enter your choices or press RETURN to display the next screen.

    The utility is flexible; it lets you enter your subset selections at the bottom of each screen or all at once at the end of the subset list (which may be several screens later).

    You can enter subset numbers separately (separated by a space) or in ranges (with a hyphen between the first number in the range and the last number in the range).

    The following subsets must be installed in the DMS environment:

    The first screen of optional subsets is displayed along with the following instructions: 

    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 extracted.
 
 - General Applications :
     1) Additional Terminfo databases
 
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
 
Choices (for example, 1 2 4-6):
 
     2) Computer Aided System Tutor
     3) DOS tools
     4) Local Area Transport (LAT)
     5) Perl Runtime
     6) UNIX(tm) SVID2 Compatibility
     7) UNIX(tm) to UNIX(tm) Copy Facility
     8) Xemacs Runtime
 
 - Kernel Build Environment :
     9) ATM Kernel Header and Common Files
    10) ATM Kernel Modules
    11) Logical Storage Manager Kernel Modules
    12) POLYCTR advfs Kernel Modules
 
 - Kernel Software Development :
    13) ATM Kernel Objects
    14) Hardware Kernel Objects
    15) POLYCTR advfs Kernel Objects
    16) Standard Kernel Objects
 
 - Mail Applications :
    17) DECwindows Mail Interface
    18) RAND Corp. Mail Handler (MH)
 
 - Network-Server/Communications :
    19) ATM Commands
    20) Additional Networking Services
    21) Dataless Management Services
    22) Remote Installation Service
 
 - Obsolete Components :
    23) Obsolete Commands and Utilities
    24) Obsolete Locale databases
 
 - Printing Environment :
    25) Adobe Font Metric Files
 
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
 
Choices (for example, 1 2 4-6):
 
 
 - Reference Pages :
    26) Ref Pages: Admin/User
    27) Ref Pages: CDE Admin/User
    28) Ref Pages: CDE Development
    29) Ref Pages: Programming
    30) Ref Pages: Windows Admin/User
    31) Ref Pages: Windows Programming
 
 - Software Development :
    32) CDA(tm) Software Development
    33) CDA(tm) for X/Motif Development
    34) CDE Software Development and Programming Examples
    35) DMI Software Development and Programming Examples
    36) GNU Revision Control System
    37) Java V1.1.5 Development Environment
    38) Ladebug Debugger Version 4.0-44
    39) Ladebug Debugger Version 4.0-44 Release Notes
    40) Ladebug Debugger graphical user interface
    41) Ladebug Debugger remote server
    42) Programming Examples
    43) Software Development Desktop Environment
    44) Software Development Tools and Utilities
    45) Source Code Control System
    46) Standard Header Files
    47) Standard Programmer Commands
    48) Static Libraries
    49) X Window and X/Motif Header Files
    50) X Window and X/Motif Programming Examples
    51) X Window and X/Motif Software Development
    52) X Window and X/Motif Static Libraries
 
 - Supplemental Documentation :
    53) Java V1.1.5
    54) XIE Version 5 Online Documentation
 
 - System Administration :
    55) Advanced File System Daemon
 
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
 
Choices (for example, 1 2 4-6):
 
    56) Advanced File System Graphical User Interface
    57) C2-Security
    58) C2-Security GUI
    59) DECevent Base kit (Translation / Analysis)
    60) DMI Runtime Environment
    61) Environmental Monitoring
    62) Kernel Debugging Tools
    63) Logical Storage Manager
    64) Logical Storage Manager GUI
    65) POLYCTR advfs
    66) Single-Byte European Locales
    67) System Accounting Utilities
    68) System Exercisers
 
 - Text Processing :
    69) Doc. Preparation Tools
    70) Doc. Preparation Tools Extensions
 
 - Windowing Environment :
    71) Adobe Fonts
    72) DECwindows 100dpi Fonts
    73) DECwindows 75dpi Fonts
    74) LK201 Keyboard Support
    75) LK401 Keyboard Support
    76) LK411 Keyboard Support
    77) LK421 Keyboard Support
    78) LK444 Keyboard Support
    79) PCXAL Keyboard Support
    80) X Customizations for OEM
    81) X Fonts
    82) X Servers Base
    83) X Servers for Open3D
    84) X Servers for PCbus
    85) X Servers for TurboChannel
    86) X/Motif 1.1
 
 - Windows Applications :
    87) Additional DECwindows Applications
 
--- MORE TO FOLLOW ---
Enter your choices or press RETURN to display the next screen.
 
Choices (for example, 1 2 4-6):
 
    88) Additional X Applications
    89) CDE Additional Applications
    90) Demo X Applications
    91) Nested X Server
    92) Old Additional DECwindows Applications
    93) Virtual X Frame Buffer
 
Or you may choose one of the following options:
 
    94) ALL mandatory and all optional subsets
    95) MANDATORY subsets only
    96) CANCEL selections and redisplay menus
    97) EXIT without extracting any subsets
 
Enter your choices or press RETURN to redisplay menus.
 
Choices (for example, 1 2 4-6): 95
 

    If you choose the option ALL mandatory and all optional subsets, all available software subsets are installed.

    If you choose the option MANDATORY subsets only, only the mandatory software subsets are installed in the environment even if you have entered optional subset numbers on previous screens. If you choose this option, you must go back and install the subsets required for DMS from the optional subset list. Use the instructions in Section 11.3 of this manual to install the subsets required for DMS.

    If you choose the option CANCEL selections and redisplay menus, the utility returns to the first screen of software subsets and you are able to start your subset selection process again.

    If you choose the option EXIT without installing any subsets, the utility prompts you to confirm your choice. If you enter y, the utility returns to the DMU Main Menu. If you enter n, the utility returns to the first screen of software subsets to let you begin your subset selection again.

  8. Once you have entered your subset selections, the screen displays the subsets you have chosen to install and then asks you to confirm your choice: 

    You are extracting the following mandatory subsets:
 
        Base System
        Base System - Hardware Support
        Java V1.1.5 Environment
        Tcl Commands
        Tk Toolkit Commands
        Hardware Kernel Header and Common Files
        Hardware Kernel Modules
        Kernel Header and Common Files
        Standard Kernel Modules
        CDE Mail Interface
        Basic Networking Services
        NFS(tm) Utilities
        Local Printer Support
        Compiler Back End
        Base System Management Applications and Utilities
        Basic Networking Configuration Applications
        Graphical Base System Management Utilities
        Graphical Print Configuration Application
        Graphical System Administration Utilities
        NFS(tm) Configuration Application
        Basic X Environment
        CDE Desktop Environment
        CDE Minimum Runtime Environment
        Old X Environment
        Netscape Navigator Gold V3.0
 
Is this correct? (y/n): y

    If the subsets listed are the subsets that you want to install into the environment, enter y. If you type N, the list of optional software subsets is displayed again, and you can restart your subset selection process.

  9. Before software installation begins, the dmu utility checks to make sure there is enough disk space to accommodate the software subsets you have chosen to install in the environment. The following message appears if there is sufficient disk space available: 

    Checking file system space required to install selected
subsets:
 
File system space checked OK.

    If there is not enough disk space to perform the installation, a message similar to this is displayed: 

    fitset:
file system /usr needs 74683 Kbytes more to install the software specified.
setld:
There is not enough file system space to install the mandatory subsets.
setld failed.
 
Error(s) have occurred during subset load. The subset(s) that failed
are listed above and have not been installed into the environment.
Possible causes for failure include subset dependencies that have
not been met or the lack of disk space.
 
You will now be asked if you wish to keep this environment.
If you elect to keep the environment, you may install the subsets that failed
by choosing INSTALL from the DMS main menu and select an existing environment.
If you elect not to keep the environment, it will be completely removed.
 
Keep this environment (y/n) [y]:

    If you want to keep the new DMU environment, enter y. If not, enter n. The dmu utility terminates the installation and returns to the DMU Main Menu. At this point, you have to resize your disk partitions or choose fewer optional software subsets.

  10. If there was enough disk space to install the subsets, messages will appear as each subset is selected, installed, and verified. Depending on the number of and size of the subsets you have chosen, this process can take an hour or more.

    The new environment is located in /var/adm/dms/dmsN.alpha.

After the installation of software subsets is complete, the utility displays the name of the new DMS environment. If this is the first DMS environment, it is automatically named dms0.alpha. Subsequent DMS environments are numbered sequentially. That is, the next environment is named dms1.alpha, the one after that is named dms2.alpha, and so on.

If you delete an environment, for example dms4.alpha, the next time you install a DMS environment, the dmu utility reuses the number 4 to name the environment. The utility fills the holes left in the numbering sequence by environments that have been deleted.

After you install software into the DMS environments, you must configure and build the kernel for that environment. Refer to Section 11.5 for instructions on how to begin the kernel configuration phase. However, if you want to add additional software to the environment before configuring the kernel, refer to Section 11.3.

11.3    Adding Software to an Existing DMS Environment

Use the setld utility to install any additional software subsets and layered products that are compatible with the operating system into the DMS client area on the server. To install additional software into an existing environment, invoke the dmu utility and choose the INSTALL software environments option from the DMU Main Menu.

Caution

Ensure that DMS clients that mount the usr area of the target /var/adm/dms/dmsN .alpha area are not running when you install an additional software product, or their usr area may change unpredictably and cause destruction of software or data or both.

It is recommended that you shut down the clients registered to the environment (using shutdown) before adding new software. To provide clients access to the new software subsets, delete the clients from the environment and then add them to the environment after it is reconfigured.

When clients are removed and added to the reconfigured environment, customized information in the root directory is lost.

The following sample session illustrates the installation of optional subsets into /var/adm/dms/dms0.alpha.

  1. Mount the CD-ROM that contains the software you want to install as shown in Section 11.2, or mount the file system area that contains the software kits.

  2. Invoke the dmu utility from the root system prompt by entering: 

    # /usr/sbin/dmu

    Choose the INSTALL software environments option from the DMU Main Menu by entering i at the prompt. 

    *** DMU Main Menu ***
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice: i

  3. The DMU Software Installation Menu is displayed. Choose the option, Add software into an existing area. A message confirms that you have chosen to add a product to an existing area. 

    DMU Software Installation Menu:
 
    1)  Install software into a new area
    2)  Add software into an existing area
    3)  Perform configuration phase on an existing area
    4)  Return to previous menu
 
Enter your choice: 2
 
You have chosen to add a product to an existing environment.
 
The existing environment is /var/adm/dms/dms0.alpha.

    In the previous example, only one environment, dms0.alpha, exists. If you have more than one DMS environment, a list of the environments is displayed and a prompt asks you to select the environment to which you want to add software: 

    Select the remote dataless environment:
 
1) /var/adm/dms/dms0.alpha
   'DIGITAL UNIX Operating System (Rev nnn)'
 
2) /var/adm/dms/dms1.alpha
   'DIGITAL UNIX Operating System (Rev nnn)'
   'Sort Runtime Library'
 
Enter your choice: 1

  4. Next, a prompt asks for the full pathname of the device special file name or the path of the directory where the software is located: 

    Enter the device special file name or the path of the directory where
the software is located (for example, /mnt/ALPHA/BASE): 
/mnt/ALPHA/COMPILERS

  5. As shown in Section 11.2 the utility lists the subsets that are available. Select the optional subsets that you want from the list. Subsets that are already installed will not display on the list.

  6. The utility lists the subsets that you have chosen to install and asks you to confirm your choice. If the subsets listed are the ones that you want, enter y. If you enter N, the list of optional software subsets is displayed again, and you can reselect the subsets that you want.

Messages appear as each subset that you selected is installed and verified. Depending on the number and size of subsets you have chosen, this process can take an hour or more.

11.4    Installing a Hardware Update Release into a DMS Environment

The procedures in this section assume that the client is running a version of the operating system that is supported.

You can install the new release from a locally mounted CD-ROM, a CD-ROM mounted using NFS from a remote server, or from a RIS area exported using NFS from a RIS server where the new release has been installed. See Section 4.4 for additional information on using this procedure.

If you install from a RIS area, you must know which product areas in your /usr/var/adm/ris/ risN .alpha contain each of the product kits you need to install. On the RIS server, as superuser, enter the following command to identify the RIS area that contains the release subsets: 


# /usr/sbin/ris -s

If you install from an NFS mounted RIS area or from a locally installed RIS area, examine the /usr/var/adm/ris/risN .alpha/ProdNames file to determine which directory in the RIS area contains the operating system software and enter the path of the directory when requested by the system.

If you install from a CD-ROM mounted on the mount point /mnt, the directory that contains the operating system hardware update is /mnt/ALPHA/hUPDATE.

To install the operating system hardware update release, perform the following procedures:

  1. Install the operating system into a new DMS environment using the steps in Section 11.2. Do not configure the DMS environment.

  2. Install the operating system hardware update release into the same environment following the steps in Section 11.3.

After you install the operating system and add the operating system hardware update, you can configure your DMS environment.

Follow the steps in Section 11.5 to configure your DMS environment.

11.5    Configuring DMS Environments

After you install software into a new or existing DMS environment, you must configure the environment. Configuring the environment entails:

  1. Customizing system files (the .proto.. files). This step is optional; you do not have to customize these files for the environment. This step is performed outside of the dmu utility.

  2. Building the environment's kernel. This step is mandatory and is performed through the CONFIGURE software environments option of the DMU Main Menu.

11.5.1    Customizing .proto.. Files

If you have already configured the DMS environment and later decide to modify .proto.. files, you must delete the files created by the configuration process. In the following example the fstab is modified to include a server name: 

1. delete the $DMS_ROOT/hosts file
2. modify the $DMS_ROOT/.proto..hosts file
3. configure the DMS area

Customize each environment to suit the clients that will be added to a DMS environment by modifying the .proto.. files. Performing this customization before you add clients to the environment reduces the amount of customization required at each client. You perform the customization before configuring and building the kernel.

There are many .proto.. files located in the DMS environment /var/adm/dms/dmsN .alpha in the /etc, /bin, /var/adm/X11, and root directories that you may want to modify. As an example, the /etc/.proto..hosts file is a file that you might want to modify in advance. Table 11-1 lists the .proto.. files found in the /etc directory that are available for you to customize.

Table 11-1:  List of .proto.. Files in /etc

.proto..TIMEZONE .proto..acucap .proto..autopush.conf
.proto..binlog.conf .proto..ddr.db .proto.ddr.dbase
.proto..dhcptab .proto.disktab .proto.dvrdevtab
.proto..exports .proto..fstab .proto..ftpusers
.proto..gen_databases .proto..gettydefs .proto..group
.proto..hosts .proto..hosts.equiv .proto..ifaccess.conf
.proto..inet.local .proto..inetd.conf .proto..inittab
.proto..lprsetup.dat .proto..magic .proto..motd
.proto..networks .proto..ntp.conf .proto..passwd
.proto..phones .proto..profile .proto..protocols
.proto..rc.config .proto..remote .proto..rpc
.proto..securettys .proto..services .proto..shells
.proto..slhosts .proto..stresetup.conf .proto..svc.conf
.proto..sysconfigtab .proto..syslog.conf .proto..ultrix_login
.proto..ultrix_path .proto..ultrix_profile  

For example, the /etc/.proto..hosts file contains no host names. At a minimum, edit this file to include the network addresses, names, and aliases of well-known systems in your environment. Server information should be listed, so that you do not have to enter this information for each client when setting up the network services. Entries in this file look similar to the following: 

	127.0.0.1 localhost
	61.96.112.102 dmsserver.myorg.com dmsserver
	61.96.112.157 nfsserver.myorg.com nfsserver

You should list commonly mounted NFS file systems, as well as the /proc file system if the clients will be using it. When you add NFS file systems to the etc/.proto..fstab file you also should add the hosts to the etc/.proto..hosts file. If the NFS mount points are in the client root partition, make the directory mount points in the DMS root area as well. If they are in the shared usr directory structure, make the directory mount points in the DMS usr directory area.

After you have made changes to the .proto.. files in the DMS environment, perform the configuration phase following the steps in Section 11.5.2.

11.5.2    Configuring the DMS Environment

After you have modified the .proto.. files, use the following procedures to configure the DMS environment:

  1. Invoke the dmu utility by entering the following command at the root system prompt: 

    
# /usr/sbin/dmu

    Choose the option CONFIGURE software environments by entering c at the DMU Main Menu prompt. If you want to customize the environment, you already should have modified the .proto.. files. 

    *** DMU Main Menu ***
 
     ) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice: c
 
You have chosen to configure an existing dataless 
environment.

    Note

    You also can configure the DMS environment from the INSTALL software environments option on the DMU Main Menu (by entering i at the Main Menu prompt). When you enter i, the DMU Software Installation Menu is displayed. As shown in this example, the configuration phase is performed by choosing option 3. 

    DMU Software Installation Menu:
 
        1) Install software into a new area
        2) Add software to an existing area
        3) Perform configuration phase on an existing area
        4) Return to previous menu
 
Enter your choice: 3

    The configuration phase proceeds as shown in the following steps.

  2. You are prompted to select the dataless environment that you want to configure: 

    Select the remote dataless environment:
 
1)  /var/adm/dms/dms0.alpha
    'DIGITAL UNIX V.4.0F Operating System (Rev nnn)'
 
2)  /var/adm/dms/dms1.alpha
    'DIGITAL UNIX V.4.0F Operating System (Rev nnn)'
    'DEC Pascal for DEC OSF/1 AXP Runtime Support'
    'DEC Fortran for OSF/1 AXP Runtime Support'
    'DEC Cobol RTL V2.2 for DEC OSF/1 Systems'
    'DEC C++ RTL Version 3.0 for DEC OSF/1 SYSTEMS'
 
Enter your choice: 1

    If there is only one environment with software installed, you will not be prompted to enter the environment to configure. The utility proceeds to the next step automatically.

  3. The utility displays a message that informs you that if you want to customize the environment, you must have modified already the .proto.. files within the DMS environment. If you have not modified already these files, you have a chance to stop the process now and modify the .proto.. files. 

    There are several files prefixed by .proto.. within the
environment area that should be modified before performing
a configuration of the area.  Performing this customization
of the environment before you register clients will reduce the
amount of customization required at each client.
 
You may now choose to continue with the configuration or return
to the main menu and exit to perform customization of the
environment.
Do you want to (c)ontinue or (r)eturn to the main menu? (c/r)
[c]: c

    If you enter r, the utility returns to the DMU Main Menu to give you the opportunity to exit the dmu utility and modify the /etc/.proto.. files.

    If you enter c to continue with the configuration, the utility displays messages as it configures each software subset. Your output will be similar to the following: 

    Configuring "Base System " (OSFBASE440)
 
Configuring "Base System - Hardware Support " (OSFHWBASE440)
 
Configuring "Compiler Back End " (OSFCMPLRS440)
 
Configuring "Kernel Header and Common Files " (OSFBINCOM440)
 
Configuring "Standard Kernel Objects " (OSFBIN440)
 
Configuring "Hardware Kernel Objects " (OSFHWBIN440)
 
Configuring "Hardware Kernel Header and Common Files"
(OSFHWBINCOM440)
 
Configuring "Logical Storage Manager Kernel Header and Common
Files" (OSFLSMBINCOM440)
 
Configuring "Basic Networking Services " (OSFCLINET440)
 
Configuring "X Servers " (OSFSER440)
 
Configuring "Basic X Environment " (OSFX11440)
 
Configuring "X Fonts " (OSFMITFONT440)
 
Configuring "DECwindows 75dpi Fonts " (OSFFONT440)
 
Configuring "DECwindows 100dpi Fonts " (OSFFONT15440)
 
Configuring "Adobe Fonts " (OSFDPSFONT440)
 
Configuring "Additional Networking Services " (OSFINET440)
 
Configuring "NFS(tm) Utilities " (OSFNFS440)
 
Configuring "POLYCTR advfs Kernel Objects " (OSFADVFSBIN440)
 
Configuring "Logical Storage Manager Kernel Objects"
(OSFLSMBIN440)
 
Configuring "Remote Installation Service " (OSFRIS440)
 
Configuring "Dataless Management Services " (OSFDMS440)

After you have created and installed software in at least one DMS environment, performed customization of the .proto.. files, and performed the configuration phase on the DMS environment, you can add clients to the environment. Adding clients to DMS environments is discussed in Chapter 12.

11.6    Setting Up a Worldwide DMS Server

The following sections provide information for setting up a worldwide DMS server.

11.6.1    DMS Server Setup

Use the following procedures to create a new dmsN .alpha environment and install worldwide software into it:

  1. Install the operating system into a DMS area before installing the Worldwide Language Support (WLS) software.

  2. Enter a mount command similar to the following before starting the utility if you are using the operating system CD-ROM as the distribution media: 

    # mount -dr /dev/rz4c /mnt

    This example uses a CD-ROM drive that is unit 0 on the mount point /mnt. If your drive is a different unit, substitute the correct unit number.

  3. Enter the following command to invoke the dmu utility: 

    # /usr/sbin/dmu

  4. Choose the option INSTALL software environments by entering i at the DMS Main Menu prompt.

  5. The DMU Software Installation Menu is displayed. Choose the option, Add software to an existing area. If you have more than one DMS environment, a list of the environments is displayed and a prompt asks you to select the environment to which you want to add software. Select the DMS area on which the operating system is installed.

  6. At the prompt enter the full pathnames of the device special file or mount points for the distribution media. Enter /mnt/ALPHA/WORLDWIDE to install worldwide support subsets.

    The installation procedure then displays: 

    ******************************************************************
*                                                                *
*  Tru64 UNIX WORLDWIDE LANGUAGE SUPPORT INSTALLATION PROCEDURE  *
*                                                                *
******************************************************************
 
Please select the countries for which you want to install
support subsets:
 
   1) Czech Republic           2) France
   3) Germany                  4) Greece
   5) Hong Kong                6) Hungary
   7) Israel                   8) Italy
   9) Japan                   10) Korea
  11) Lithuania               12) Poland
  13) Russia                  14) Slovakia
  15) Slovenia                16) Spain
  17) Sweden                  18) Taiwan
  19) Thailand                20) The People's Republic of China
  21) Turkey
 
  22) All of the above
  23) None of the above
 
Choices (for example, 1 2 3) :

  7. Select the countries for which you want to install worldwide software. A list of subsets is displayed. Worldwide subsets are described in the Installation Guide. The steps for installing subsets are the same as installing subsets from a RIS server. See Section 4.1 for detailed instructions. After installing the subsets, the DMU Main Menu is displayed.

  8. Choose the option CONFIGURE software environments by entering c at the DMU Main Menu prompt, to configure newly installed subsets into the DMS environment. Questions about configuring Wnn appear during the configuration phase.

11.6.2    Worldwide Client Setup

Once you have set up the DMS areas and registered the clients, they can access the configured areas. See Section 10.8 on how to register the client with a network naming service. You must register the client with the full or partial(default) kernel option for them to use the Asian kernel functionality.

11.6.3    Building an Asian Kernel for DMS Clients

When the DMS client boots for the first time from a newly configured DMS area, an Asian kernel is built. Reboot the system if you want to use the Asian terminal driver functions. You also can reconfigure the Asian kernel on the client machine by using the wwconfig command as follows: 

# wwconfig -a

Refer to the wwconfig(8) reference page and the Installation Guide for more information about the wwconfig command.