Filter
Top Products
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.
Setting Up a RIS Area 4–11