4 Setting Up a RIS Area on the Server

This chapter describes how to use the ris utility to configure a RIS server. After completing this chapter, you will be able to:

The ris utility can be invoked in two ways:

Interactively through a menu-driven interface

From the command line by issuing commands to perform the various tasks one at a time

This chapter describes how to use the utility's menu-driven interface. Chapter 6 describes how to use individual ris commands. For additional information on the ris utility, see the ris(8) reference page.

4.1 Installing Software into a New RIS Area

After you create a RIS area and install the first software kit there, you can install more kits into that area or create other areas as you need them. (Section 4.2 describes how to install additional software into an existing RIS environment.)

Use the following procedure to create a new risN .alpha environment and install the first software kit into it:

Enter a mount command similar to the following before starting the utility if your distribution media is a CD-ROM:
```
# mount -rd /dev/rz4c /mnt
```
This example uses rz4c and specifies /mnt as the mount point; if your drive or mount point is different, make the appropriate substitutions.
If you are uncertain of your CD-ROM'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 RRD43 disk# 32 (SCSI ID # 4)
```
The CD-ROM device corresponds to the RRD device, in this example RRD43.

Enter the following command to invoke the ris utility from the root system prompt:
```
# /usr/sbin/ris
```
The RIS Utility Main Menu is displayed. Each available menu item is preceded by a letter. The first time you invoke the utility, the display looks similar to the following:
```
Checking accessibility of RIS areas.... done
 
*** RIS Utility Main Menu ***
 
Choices without key letters are not available.
 
  ) ADD a client
  ) DELETE software products
 i) INSTALL software products
  ) LIST registered clients
  ) MODIFY a client
  ) REMOVE a client
  ) SHOW software products in remote installation environments
 x) EXIT
 
Enter your choice:
```
The RIS Utility Main Menu does not display option letters for menu items that cannot be accessed. As you add environments, software, and clients to the system, other menu options will become available on the menu.

Choose the Install software products option by entering i at the prompt:


Enter your choice:  i

The RIS Installation menu displays the installation options. Choose option 1, the Install software into a new area option.

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:  1
 
You have chosen to establish a new remote installation
environment.

Enter the full pathname or the device special file name for the distribution media. If your distribution media is CD-ROM mounted on /mnt, the directory where the software is located is /mnt/ALPHA/BASE. Enter a device specific file name only for magnetic tape media.
```
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
```

The utility requests whether you want to use the standard boot method or the boot-link method. Select the boot-link method if you intend to add software, which will provide supplemental hardware support, to this RIS area.

Select the type of DIGITAL UNIX base product to create.  If the software you
are offering supports add-on hardware that is needed to boot the client
system, select "boot-link" as the type of RIS area to create.  Otherwise,
select "standard".  If you select "boot-link", the software will be extracted
(or copied) to the RIS area because symbolically linked RIS areas do not
support this feature.
 
Choose one of the following options:
 
    1)  Standard boot method
    2)  Boot-Link method
 
Enter your choice: 1

The next step is available only when the Standard boot method is chosen. Here, the utility lets you choose whether you want to create symbolic links to the software or to extract the software into the RIS area.
```
Choose one of the following options:
 
    1)  Extract software from /mnt/ALPHA/BASE
    2)  Create symbolic link to /mnt/ALPHA/BASE
 
Enter your choice:
```
- If you choose to extract subsets (by choosing option 1), the subsets you select are copied from the device or directory specified into the RIS area. You must know which specific subsets to extract and the amount of disk space required. See Section 3.2 for information about planning disk space for RIS. Clients can install only the subsets that were extracted into RIS product areas for which they are registered. Using extracted subsets improves the performance of the RIS environment. This is because copying software from magnetic media as opposed to optical media is faster. You must provide an extracted RIS area if you want to install a hardware product kit for a device not currently supported by the operating system. See Section 4.3 for additional information.
- If you choose to link to the device or directory specified (option 2), symbolic links are created in the RIS area that point to the subset directories on the device or directory specified. Disk space planning is not required because the subsets reside on the device or directory specified. However, the device or directory specified must be on line and mounted for clients to access the subsets. Unlike subset extraction, no subset selection is required. Clients registered for RIS product areas that are links to the device or directory specified can access all subsets.
  
  Caution
  
  Unmounting, deleting, or switching the device or directory where the RIS area is linked corrupts the RIS area. To restore the RIS area, remount the area pointed to by the RIS area.
  You are prompted to enter the client architecture for products that are not part of base operating system that the RIS environment will serve:
```
Choose the architecture of the clients that the environment
will serve:
 
    1) alpha
    2) custom
    3) mips
 
Enter your choice: 1
 
The new environment is in /usr/var/adm/ris/ris0.alpha.
```

If you chose to extract subsets, the utility lists the mandatory and optional software subsets you can install. Choose the subsets that you want from the list. The utility displays your list for confirmation. In the following example, only the mandatory software subsets are chosen. Your screen will look similar to this:

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

If you enter y, the subset extraction process begins. If you enter n, the list of subsets is displayed again and you can restart your selection process.

When you confirm your selections, the ris utility extracts the subsets and displays the name of the new RIS environment. The RIS Utility main menu is then displayed.

Once you set up the RIS areas and register clients in those areas, the clients can access the areas they need. Client registration is discussed in Chapter 6.

4.2 Installing Software into an Existing RIS Area

To install software subsets that are compatible with the setld utility into an existing RIS environment, enter the following command as superuser and follow the procedures as they appear on the screen:

# /usr/sbin/ris

Next the RIS Utility Main Menu is displayed. Choose the option INSTALL software products by entering i at the prompt:

Checking accessibility of RIS areas... done
 
*** RIS Utility Main Menu ***
 
Choices without key letters are not available.
 
    a) ADD a client
    d) DELETE software products
    i) INSTALL software products
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software products in remote installation environments
    x) EXIT
 
Enter your choice: i

The RIS Software Installation Menu is displayed. Choose the option to Add software into an existing area by entering 2 at the prompt:

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

The utility displays a list of the existing RIS areas:

You have chosen to add a product to an existing environment.
 
Select the remote installation environment:
 
1) /usr/var/adm/ris/ris0.alpha
      'POLYCENTER advanced File System'
      'DECsafe Available Server Environment  (ASE)'
      'System V Environment'
 
2) /usr/var/adm/ris/ris1.alpha
      'Sort Runtime Library'
      'Free Software Foundation GNU Source (Rev xxx)'
      'DEC Ada Support Library'
 
Enter your choice or press RETURN to quit:

Choose the area that you want to use, and then proceed as before to mount the distribution media and choose subsets. Press the Return key if you want to return to the RIS Utility Main Menu.

Repeat this procedure for each additional group of subsets you want to install.

4.3 Including Hardware Product Kits into a RIS Area

You may need to install hardware product kits, as well as the operating system base product kit, onto client systems; such a hardware product kit could be a third-party driver for a device not supported under Tru64 UNIX. The ris utility lets you include hardware product kits into a RIS area for subsequent installation on a client system.

This section describes how to set up the RIS area to include a hardware product kit, so that it can be used to perform a subsequent installation on a client.

The following is a list of the installation requirements:

The installation of hardware product kits can be done only on an extracted RIS area. An error message is displayed if you attempt to include a hardware product kit into a new RIS area or a RIS area which contains a symbolically linked base operating system.

The hardware product kit must be setld compatible to be included on an existing RIS environment.

The extracted RIS area should contain at least all the mandatory subsets as well as the following:

All Mandatory Subsets
 
 
Windowing Environment:
 
-  Adobe Fonts
-  DECwindows 100dpi Fonts
-  DECwindows 75dpi Fonts
-  LK201 Keyboard Support
-  LK401 Keyboard Support
-  LK411 Keyboard Support
-  LK421 Keyboard Support
-  LK444 Keyboard Support
-  PCXAL Keyboard Support
-  X Customizations for OEM
-  X Fonts
-  X Servers Base
-  X Servers for Open3D
-  X Servers for PCbus
-  X Servers for TurboChannel
-  X/Motif 1.1

To create the new hardware product kit area, hard links are made between the operating system base product and the new product that will contain the hardware support device kit. This permits the operating system base product and hardware product kit to coexist in the same RIS area using minimum additional magnetic disk space.

Execute the following procedures as superuser to install a hardware product kit into an existing environment. In the following example, the hardware product kit being installed is named ESA100.

Enter the following command to invoke the ris utility from the root system prompt:

# /usr/sbin/ris

The RIS Utility Main Menu is displayed. Chose the option INSTALL software products by entering i at the prompt:

Checking accessibility of RIS areas... done
 
*** RIS Utility Main Menu ***
 
Choices without key letters are not available.
 
    a) ADD a client
    d) DELETE software products
    i) INSTALL software products
     ) LIST registered clients
     ) MODIFY a client
     ) REMOVE a client
    s) SHOW software products in remote installation environments
    x) EXIT
 
Enter your choice: i

The RIS Software Installation Menu is displayed. Choose the option Add software into an existing area by entering 2 at the prompt:

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

The following appears as a response to your entry.

You have chosen to add a product to an existing environment.

The utility asks you to specify the remote installation environment.

Select the remote installation environment:
 
    1)  /var/adm/ris/ris1.alpha
          'DIGITAL UNIX V4.0F Operating System ( Rev nnn.n )'
 
Enter your choice or press RETURN to quit: 1

Enter the location of the software:

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

You will now need to specify whether the software should be integrated with the base product or included as a separate product. Select 1 to integrate the software with the base product.

The kit you have specified has been identified as a DIGITAL UNIX kernel kit.
This type of kit may contain software which is needed during the booting of
the kernel for the installation due to required hardware support. If you need
to add this kit to the base, select the option to integrate the kit. You may
otherwise choose to add this kit to the RIS area as a separate product.
 
1) Integrate with Base product and include product
2) Include as separate product
3) Return to Main Menu
 
Enter your choice:  [1]: 1

Specify the product to add to the kit.

Please select one of the following products to add the kit to.
 
     1   'DIGITAL UNIX V4.0F Operating System ( Rev nnn.n)'
 
Enter your selection or <return> to quit: 1

Choose whether to extract the software or provide a symbolic link. In this example, extract the software by selecting 1.
```
Choose one of the following options:
 
    1)  Extract software from /HWKIT/MYVGA/kit
    2)  Create symbolic link to /HWKIT/MYVGA/kit
 
Enter your choice: 1
```
The new hardware kit is now added to the area you selected.

During this phase the new product is created and the hard links between the products are made. Messages similar to the following are displayed at your terminal.

 Preparing new product area...
	Working....Tue Jul  6 13:47:48 EDT 1999
	Working....Tue Jul  6 13:49:49 EDT 1999
	Working....Tue Jul  6 13:51:50 EDT 1999
	Working....Tue Jul  6 13:53:51 EDT 1999
	Working....Tue Jul  6 13:55:52 EDT 1999
	Working....Tue Jul  6 13:57:53 EDT 1999
	Working....Tue Jul  6 13:59:54 EDT 1999
	Working....Tue Jul  6 14:01:55 EDT 1999
	Working....Tue Jul  6 14:03:55 EDT 1999
	Working....Tue Jul  6 14:05:56 EDT 1999
	Working....Tue Jul  6 14:07:57 EDT 1999
	Working....Tue Jul  6 14:09:58 EDT 1999
	Working....Tue Jul  6 14:11:59 EDT 1999
	Working....Tue Jul  6 14:14:00 EDT 1999
 
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.
 
     1) MYVGA Test kit
 
Or you may choose one of the following options:
 
     2) ALL of the above
     3) CANCEL selections and redisplay menus
     4) EXIT without extracting any subsets
 
Enter your choices or press RETURN to redisplay menus.
Choices (for example, 1 2 4-6): 1
 
You are extracting the following optional subsets:
 
        MYVGA Test kit
Is this correct? (y/n): y
 
Checking file system space required to extract selected subsets:
 
File system space checked OK.
Extracting MYGASTATIC100...
Media extraction complete.
 
 
The following software now exists in RIS product area
/var/adm/ris/ris1.alpha:
   1    'DIGITAL UNIX V4.0F Operating System ( Rev nnn.n )' 
               with 'MYVGASTATIC software version 1' 
   2    'MYVGASTATIC software version 1'

At this point, the new product area has been created and the hardware product kit installed into it.

4.4 Using a RIS Area Mounted on NFS

The information in this section can be used only if you are serving a version of the operating system prior to Version 4.0F.

You can use an NFS mount point to install software from a RIS area or an operating system distribution CD-ROM that you import from another machine. For example, if a system named chicago has a CD-ROM containing the operating system subsets mounted on /mnt and listed in its /etc/exports file, the system administrator on newyork can NFS mount that CD-ROM with the following command:


newyork_root# mount chicago:/mnt/ALPHA/BASE /mnt

After the CD-ROM is mounted, the system administrator on newyork can use the ris utility to install software from it as if it were local to newyork.

If another system has a RIS area with the needed subsets for a RIS area on the local system and exports that area, you can create a RIS area from the remote RIS area.

For example, if a system named seattle has the operating system subsets in its ris0.alpha product environment, the system administrator on newyork can NFS mount that product environment with the following command:


newyork_root# mount seattle:/var/adm/ris/ris0.alpha  /mnt

After the remote product environment is mounted, the system administrator for newyork can use the ris utility to install software from it as if it were local to newyork.

4.5 Modifying the /etc/exports File

RIS client installations of the base operating system prior to Version 4.0F rely on files located in the server's /var/adm/ris/risN.arch /kit directories. The RIS server must export these directories..

For the Version 4.0F of the operating system base product, the /var/adm/ris/risN.arch /product_1 product directory that is exported contains the distribution image. In this directory path, N is the number of the RIS area and arch is the architecture of the client systems that the area serves. When you create the RIS area, risN.arch, the ris utility supplies you with a name based on the choices you make when you create the RIS area.

The server's /etc/exports file must include an entry for each RIS area that it is exporting. When you create a RIS area, the ris utility automatically edits the /etc/exports file and adds the correct entry for that area. However, if you modify the path to a RIS area, you must also modify the corresponding line in the /etc/exports file.

The RIS area entries in the /etc/exports file of a system that acts as a RIS server for two Alpha environments and one MIPS RISC environment look similar to the following:
```
/var/adm/ris/ris0.alpha/kit  -root=0  -ro
/var/adm/ris/ris1.alpha/kit  -root=0  -ro
/var/adm/ris/ris0.mips/kit  -root=0  -ro
/ris/ris2.a/product_1     -root=0 -ro
```

The previous example shows an entry in /etc/exports of /ris/ris2.a/product_1. This entry is created by RIS and is a symbolic link from /ris/ris2.a/product_1 to /var/adm/ris/ris2.alpha/product_1. This is done to shorten the path that needs to be sent to the client during the boot process.

Note

When you register the first client on your RIS server for Version 2.0 and prior to Tru64 UNIX Version 4.0F, the ris utility creates the kit/isl directory, which contains tools that clients require to install software subsets.

When you create a /risN .alpha area, the path to the kit directory is /var/adm/ris/ris0.alpha/kit and the ris utility places the following line in the /etc/exports file:
/var/adm/ris/ris0.alpha/kit -root=0 -ro
If you create another directory in this RIS area, for example, dsk1, mount another file system there, move the contents of ris0.alpha to that directory and then link it to ris0.alpha, a listing of the RIS area shows the following entry:
ris0.alpha -> ./dsk1/ris0.alpha
The path to the kit directory is now effectively /var/adm/ris/dsk1/ris0.alpha/kit. You must edit the corresponding line in the /etc/exports file to read:
/var/adm/ris/dsk1/ris0.alpha/kit -root=0 -ro
If you fail to edit the /etc/exports file in this case, there will be a mount failure of the kit directory when you attempt a client installation.