11    Setting Up a DMS Environment

This chapter describes how to use the dmu utility to add software to a DMS environment and how to configure the environment. The following topics are discussed:

11.1    Ensuring DMS Server and Client Compatibility

If you are installing this version of the operating system into a DMS environment and the DMS server is running a previous version of the operating system, you must perform the following procedure:

  1. Log in to the DMS server as root or use the su command to gain superuser privileges.

  2. Insert the Operating System Volume 1 CD-ROM into the drive, then mount the CD-ROM.

    If your drive is a different unit, substitute the correct device name. The mount point does not have to be /mnt.

    See Section 1.3 if you do not know the CD-ROM drive's unit number.

  3. Use the mount command to update DMS on the server, as in the following example (using /mnt as the mount point): 

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

    This procedure copies files in the /usr/sbin directory to files with a *.pre-V5.1B suffix, for example: /usr/sbin/setld is copied to /usr/sbin/setld.pre-V5.1B.

When the utilupdate script completes, this RIS server can serve the current version of the operating system to a DMU client. See Appendix C for more information about 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. Section 11.3 describes how to install additional software into an existing DMS environment.

Follow these steps to install software into a new dmsN .alpha environment. Repeat the installation procedures for each dmsN .alpha environment you plan to set up.

  1. Log in as root or use the su command to gain superuser privileges.

  2. Insert the Operating System Volume 1 CD-ROM into the drive, then mount the CD-ROM.

    If your drive is a different unit, substitute the correct device name. The mount point does not have to be /mnt.

    See Section 1.3 if you do not know the CD-ROM drive's unit number.

    Note

    You can use a Network File System (NFS) mount point to install software from a Remote Installation Services (RIS) area or Operating System Volume 1 CD-ROM from another processor.

    See Section 4.5 for more information about using an NFS mounted RIS area.

  3. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu: 

    *** 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
 
Enter your choice:

    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.

  4. Enter i to select INSTALL software environments. You see the DMS Software Installation Menu: 

    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:

  5. Enter 1 to select Install software into a new area. You see the following prompt: 

    You have chosen to establish a new remote dataless environment.
 
Enter the device special file name or the path of the directory where
the software is located (for example, /mnt/ALPHA/BASE):

  6. Enter the software location, for example: /mnt/ALPHA/BASE.

    The dmu utility lists the mandatory and optional software subsets you can install.

    The following subsets must be installed in the DMS environment:

  7. Select the subsets that you want to extract; the dmu utility displays your list for confirmation. For example: 

    The following subsets are mandatory and will be installed
automatically unless you choose to exit without installing
any subsets:
               
    .
    .
    .
    {mandatory subset list}
               
    .
    .
    .
    Optional subsets are listed below.  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.
               
    .
    .
    .
    {optional subset list}
               
    .
    .
    .
    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): 94
 
The following subsets will be loaded:
               
    .
    .
    .
    {selected subset list - all mandatory & optional in this
example}
               
    .
    .
    .
    Are these the subsets that should be loaded (y/n) ?

    If you enter y, the dmu utility loads the subsets. If you enter n, the list of subsets is displayed again and you can restart your selection process.

The new DMS environment is located in the /usr/v ar/dms/dmsN.alpha directory.

If there is not enough disk space to perform the installation, you see a prompt similar to the following: 

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]:

After the installation of software subsets is complete, the dmu utility displays the name of the new DMS environment. If this is the first DMS environment, it automatically is named dms0.alpha. Subsequent DMS environments are numbered sequentially: 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. See Section 11.4.2 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, see Section 11.3.

11.3    Adding Software to an Existing DMS Environment

Perform the following steps to add software to an existing DMS environment:

  1. Log in as root to each DMS client registered to the DMS environment or use the su command to gain superuser privileges.

  2. Use the shutdown command to shut down the DMS client.

    Caution

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

    Repeat this step for each DMS client registered to the DMS environment where you are adding software.

  3. Log in as root to the DMS server or use the su command to gain superuser privileges.

  4. 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.

  5. Enter /usr/sbin/dmu to start the dmu utility. You see the DMS Main Menu: 

    *** DMU Main Menu ***
 
Choices without key letters are not available.
 
    a) ADD a client
    c) CONFIGURE software environments
    d) DELETE software environments
    i) INSTALL software environments
    l) LIST registered clients
    m) MODIFY a client
    r) REMOVE a client
    s) SHOW software environments
    x) EXIT
 
Enter your choice:

  6. Enter i to select INSTALL software environments. You see the DMS Software Installation Menu: 

    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:

  7. Enter 2 to select Add software to an existing area. You see a prompt similar to the following: 

    You have chosen to add a product to an existing environment.
 
The existing environment is /var/adm/dms/dms0.alpha.

    Note

    In the previous example, only one environment, dms0.alpha, exists. If you have more than one DMS environment, you see a prompt similar to the following: 

    Select the remote dataless environment:
 
1) /var/adm/dms/dms0.alpha
   'Tru64 UNIX VAAA Operating System (Rev nnn)'
 
2) /var/adm/dms/dms1.alpha
   'Tru64 UNIX VBBB Operating System (Rev nnn)'
 
Enter your choice:

    Enter the number corresponding to the DMS environment where you want to install the software.

    You see the following prompt: 

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

  8. Enter the software location, for example: /mnt/ALPHA/BASE.

    The dmu utility lists the mandatory and optional software subsets you can install.

  9. Select the subsets that you want to extract; the dmu utility displays your list for confirmation. For example: 

    The following subsets are mandatory and will be installed
automatically unless you choose to exit without installing
any subsets:
               
    .
    .
    .
    {mandatory subset list}
               
    .
    .
    .
    Optional subsets are listed below.  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.
               
    .
    .
    .
    {optional subset list}
               
    .
    .
    .
    Or you may choose one of the following options:
 
    24) ALL mandatory and all optional subsets
    25) MANDATORY subsets only
    26) CANCEL selections and redisplay menus
    27) EXIT without extracting any subsets
 
Enter your choices or press RETURN to redisplay menus.
 
Choices (for example, 1 2 4-6): 24
 
The following subsets will be loaded:
               
    .
    .
    .
    {selected subset list - all mandatory & optional in this
example}
               
    .
    .
    .
    Are these the subsets that should be loaded (y/n) ?

    If you enter y, the dmu utility loads the subsets. If you enter n, the list of subsets is displayed again and you can restart your selection process.

    The dmu utility installs the software subsets that you selected. This can take an hour or more.

    After the dmu utility installs the software, you see the DMU Main Menu.

  10. Follow the instructions in Section 12.4 to delete the DMS clients registered to the DMS area where you installed the software.

  11. Follow the instructions in Section 11.4.2 to reconfigure the DMS area where you installed the software.

  12. Follow the instructions in Section 12.2 to add the DMS clients deleted in the previous step to the DMS area where you installed the software. When you remove and add clients to the reconfigured environment, customized information in the root ( / ) directory is lost.

11.4    Configuring DMS Environments

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

  1. Customizing the .proto.. system files (Section 11.4.1). 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 (Section 11.4.2). This step is mandatory and is performed through the CONFIGURE software environments option of the DMU Main Menu.

11.4.1    Customizing /etc/.proto..* Files

If you already have configured the DMS environment and later decide to modify .proto.. files, you must delete the files created by the configuration process. Follow these steps to modify the fstab file to include a server name:

  1. Log in to the DMS server as root or use the su command to gain superuser privileges.

  2. Define the DMS_ROOT environment variable to point to the affected DMS area, for example: 

    # DMS_ROOT=/var/adm/dms/dmsN.alpha/root

  3. Delete the $DMS_ROOT/hosts file.

  4. Modify the $DMS_ROOT/.proto..hosts file.

  5. Use the dmu utility to configure the DMS area as described in Section 11.4.2.

Modify the .proto.. files to customize each environment for the clients that you will add to a DMS environment. If you do this customization before you configure and build the kernel and before you add clients to the DMS environment, you reduce the amount of customization required at each client.

You may want to modify several of the .proto.. files located in the DMS environment /var/adm/dms/dmsN .alpha in the /etc, /bin, /var/adm/X11, and root directories. As an example, the /etc/.proto..hosts file is a file that you could modify in advance. Table 11-1 lists the .proto.. files in the /etc directory that you can customize.

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

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

For example, the /etc/.proto..hosts file contains no host names. Edit this file to include the network addresses, names, and aliases of well-known systems in your environment. Enter server information so that you do not have to enter this information for each client when setting up network services. See hosts(4) for more information about the layout of this file.

You should list commonly mounted NFS file systems, as well as the /proc file system if it will be used by clients. 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 modify the .proto.. files in the DMS environment, configure the DMS environment by following the steps in Section 11.4.2.

11.4.2    Configuring the DMS Environment

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

  1. Log in to the DMS server as root or use the su command to gain superuser privileges.

  2. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu: 

    *** 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:

  3. Enter c to select CONFIGURE software environments. You see a prompt similar to the following example, which contains two DMS areas: 

    You have chosen to configure an existing dataless 
environment.
 
Select the remote dataless environment:
 
1)  /var/adm/dms/dms0.alpha
    'Tru64 UNIX VAAA Operating System (Rev nnn)'
 
2)  /var/adm/dms/dms1.alpha
    'Tru64 UNIX VBBB Operating System (Rev nnn)'
 
Enter your choice:

  4. Enter the number corresponding with the DMS environment you want to configure. You see the following prompt: 

    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]:

After you have created at least one DMS environment, installed software, customized the .proto.. files, and configured the DMS environment, you can add clients to the environment as discussed in Chapter 12.

11.5    Installing WLS Support in DMS

The following sections describe how to install Worldwide Language Support (WLS) support in DMS, and includes the following topics:

11.5.1    Setting Up a DMS Server for WLS

Follow these steps to create a new dmsN .alpha environment and install WLS software from a base operating system CD-ROM:

  1. Log in to the DMS server as root or use the su command to gain superuser privileges.

  2. Install the operating system into a DMS area before installing the WLS software.

  3. Load the CD-ROM containing the WLS subsets into your CD-ROM drive and enter a mount command similar to the following: 

    mount -dr -t cdfs -o rrip /dev/disk/cdrom0c /mnt

  4. Enter /usr/sbin/dmu to start the dmu utility. You see the DMU Main Menu.

  5. Select INSTALL software environments. You see the DMU Software Installation Menu.

  6. Select Add software to an existing area.

    If you have more than one DMS environment, you see a list of available DMS environments and you are prompted to select the environment for adding software.

  7. Select the DMS area where the operating system is installed. You are prompted for the location of the software.

  8. Enter the full pathname of the device special file or mount points for the distribution media. Enter /mnt/ALPHA/WORLDWIDE to install WLS subsets. You see a menu listing the countries for which you can install worldwide language support.

  9. Select the software to support the countries that you want to install. You see a list of available subsets.

    See Section 11.3 for instructions on installing subsets.

    After installing the subsets, you see the DMU Main Menu.

  10. Select CONFIGURE software environments to configure newly installed subsets into the DMS environment.

    See Section 11.4.2 for instructions on configuring DMS environments.

11.5.2    Setting Up a DMS Client for WLS

After 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 the client to use the Asian kernel functionality.

11.5.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: 

# /usr/sbin/wwconfig -a

See the Installation Guide — Advanced Topics manual and wwconfig(8) for more information about using the wwconfig command.