This chapter describes how to use the
ris
utility
to configure a RIS server.
This chapter includes the following topics:
Establishing a new RIS area with the
ris
utility (Section 4.2)
Installing software kits in an existing RIS area (Section 4.3)
Setting up a RIS area for NHD (Section 4.4)
Using a RIS area mounted on NFS (Section 4.5)
Modifying the
/etc/exports
file, if necessary,
to export RIS areas (Section 4.6)
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
ris
utility's
menu-driven interface.
Chapter 6
describes how
to use individual
ris
commands.
See
ris(8)4.2 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.3 describes how to install additional software into an existing RIS environment.
Follow these steps to create a new
risN
.alpha
environment and install the operating system:
Log in as
root
or use the
su
command to gain superuser privileges.
Insert the Operating System Volume 1 CD-ROM into the drive, then mount the CD-ROM.
If your server is running the current version of the operating system, use a command similar to the following example:
# mount -rd /dev/disk/cdrom0c /mnt
The previous
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.
See Section 1.3 if you do not know the CD-ROM drive's device name.
If your server is running an earlier version of the operating system, use a command similar to the following example:
# mount -rd /dev/rz4c /mnt
The previous 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.
See Section 1.3 if you do not know the CD-ROM drive's device name.
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.
Enter
/usr/sbin/ris
to start the
ris
utility.
You see the RIS Utility Main Menu:
*** 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 ) UPDATE hostkeys between RIS Server and Clients 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 become available.
Enter
i
to select
Install
software products.
You see the following 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:
Enter
1
to select
Install
software into a new area.
You see the following prompt:
You have chosen to establish a new remote installation environment. Enter the device special file name or the path of the directory where the software is located (for example, /mnt/ALPHA/BASE):
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.
You see the following prompt:
Select the type of operating system 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:
Select one of the available options.
Select
Boot-Link method
if you are adding
a hardware product kit to this RIS area.
If you select
Standard boot method, you
see the following prompt:
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 select
Create symbolic link, the
ris
utility creates symbolic links from the RIS area to the subset
directories on the specified source.
Disk space planning is not required because
the subsets do not reside in the RIS area.
The source must be on line and
mounted for clients to access the subsets.
Unlike subset extraction, no subset
selection is required.
Clients registered for symbolically linked RIS product
areas can access all subsets.
Caution
If you unmount, delete, or switch the source where the RIS area is linked, the RIS area is corrupted. Remount the source to restore the RIS area.
If you select
Extract software, the
ris
utility copies the selected subsets from the source into the
RIS area.
You must know the specific subsets to extract and whether there
is sufficient disk space.
See
Section 3.2
for information
about planning disk space for RIS.
Clients can install only the subsets that are extracted into RIS product areas where they are registered. Using extracted subsets improves RIS environment performance.
The
ris
utility lists the mandatory
and optional software subsets you can install.
Select the subsets that you
want to extract; the
ris
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}
.
.
.
The following choices override your previous selections:
74) ALL mandatory and all optional subsets
75) MANDATORY subsets only
76) CANCEL selections and redisplay menus
Choices (for example, 1 2 4-6): 74
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
ris
utility
loads the subsets.
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.
If you are installing a product that is not part of the base operating
system in the RIS environment, the
ris
utility tries to
determine the system architecture.
If it cannot, you see a prompt similar
to the following example:
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.
After you set up the RIS areas and register clients in those areas,
the clients can access the areas they need.
See
Chapter 6
for a discussion of client registration.
4.3 Installing Software into an Existing RIS Area
Follow these steps to install software subsets into an existing RIS
environment.
The subsets must be compatible with the
setld
utility.
This means that the kit was produced in accordance with the instructions
in the
Guide to Preparing Product Kits.
Log in as
root
or use the
su
command to gain superuser privileges.
Enter
/usr/sbin/ris
to start the
ris
utility.
You see the RIS Utility Main Menu:
*** 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 u) UPDATE hostkeys between RIS Server and Clients x) EXIT Enter your choice:
Enter
i
to select
INSTALL
software products.
You see 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:
Enter
2
to select
Add software
into an existing area.
You see a list of the existing RIS areas,
similar to the following example:
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 nnn)'
'DEC Ada Support Library'
Enter your choice or press RETURN to quit:
Enter a number to select the corresponding RIS area.
Continue to mount distribution media and choose subsets as described in Section 4.2 . 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.4 Setting Up a RIS Area for NHD
Follow these steps to create a RIS area for NHD on your RIS server:
Use the
ris
utility to install the base
operating system into a new RIS area.
Caution
Use the standard method to create the RIS area, not the bootlink method.
Extract the base operating system; do not use symbolic links.
You optionally may install TruCluster Server and Worldwide Language Support in the same RIS area.
Load the NHD CD into the RIS server's CD-ROM drive.
Mount the NHD CD. For example:
# mount /dev/disk/cdrom0a /mnt
Run the
update_ris
script to install the
NHD kit into the RIS area.
For example:
# /mnt/tools/update_ris
You see messages similar to the following:
Please select one of the following products to add NHD support to
1) /usr/var/adm/ris/ris9.alpha
'Tru64 UNIX V5.1A Operating System (Rev 1885)'
2) /usr/var/adm/ris/ris8.alpha
'Tru64 UNIX V5.1 Operating System (Rev 732)'
3) /usr/var/adm/ris/ris6.alpha
'Tru64 UNIX V5.1A Operating System ( Rev 1885 )'
Enter your selection or press <return> to quit:
Note
The number of RIS areas depends upon your RIS server.
In this example, enter
3
and press
[Return].
You see messages similar to the following:
You are updating ris area /usr/var/adm/ris/ris6.alpha for: V5.1A Operating System ( Rev 1885 ) with NHD support. Is this correct? (y/n):
In this example, enter
y
and press
[Return].
You see messages similar to the following:
'Tru64 UNIX New Hardware for V5.1A' 3 'Tru64 UNIX New Hardware for V5.1A' Building new network bootable kernel /usr/var/adm/ris/ris6.alpha/kit has been updated with NHD4 support
4.5 Using a RIS Area Mounted on NFS
You can use an NFS mount point to install software from an extracted RIS area on another system or from an operating system distribution CD-ROM mounted on another system. You can use this method to create an extracted RIS area with the base operating system subsets.
Caution
The information in this section can be used only if you are installing software on a client after you install the operating system software.
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 use mount that CD-ROM with a command
similar to the following example:
NYroot# mount chicago:/mnt/ALPHA/BASE /mnt
After
chicago
is mounted, the
newyork
system administrator can use the
ris
utility to install software from the CD-ROM as if it were local to the
newyork
system.
If another system exports an extracted RIS area with the subsets you
need on a local system, you can create an extracted 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:
NYroot# 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.6 Modifying the /etc/exports File
RIS client installations of the base operating system prior to this
version rely on files located in the server's
/var/adm/ris/risN.arch/kit
directories.
The RIS server must export
these directories.
For this version 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
risN.arch
RIS area, 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 also must 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 look
similar to the following:
/var/adm/ris/ris0.alpha/kit -root=0 -ro /var/adm/ris/ris1.alpha/kit -root=0 -ro /ris/r2p1 -root=0 -ro
The previous example shows a
/ris/r2p1
entry in
/etc/exports.
This entry is created by RIS and is a symbolic link
from
/ris/r2p1
to
/var/adm/ris/ris2.alpha/product_1.
This link shortens the path sent to the client during the boot
process.
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, as shown in the following example:
/var/adm/ris/dsk1/ris0.alpha/kit -root=0 -ro
If you do not edit the
/etc/exports
file in this
case, you will have a kit directory mount failure when you attempt a client
installation.