6 Installing a Kit

Digital UNIX provides the system administrator with several options for installing layered product kits. For example:

Using setld, the system administrator may install a kit on a running system, in single-user or multi-user mode.
Using osfboot, the system administrator may install a kit before the initial installation and boot of a system. Foreign devices are installed in this way.
Using RIS support, the system administrator may integrate a foreign kernel kit into a RIS environment. The kit provides information for rebuilding the RIS environment to support RIS installation of foreign devices.

This chapter shows how to install a user product, kernel product, and foreign device product, and how to install a kit in a RIS environment.

6.1 Installing a User Product

To install a user product, the system administrator runs the setld utility. For example, the ODB product could be installed as follows, assuming it is distributed on CD-ROM:

Place the CD-ROM in its caddy and insert it into the driver.
As superuser or root, create a directory to be the mount point for the CD-ROM, such as /mnt:
# mkdir /mnt
Mount the CD-ROM on /mnt. For example, if the CD-ROM device is located on the c partition of rz4, you would enter the following command:
# mount -r /dev/rz4c /mnt

After mounting the CD-ROM, you can change to the /mnt directory and view the directories on the CD-ROM.
Install the user product subsets:
# setld -l /mnt/ALPHA/OAT100

The setld utility displays prompts and messages to guide you through the installation process.
When the installation is complete, unmount the CD-ROM:
# umount /mnt

See the Installation Guide for more information on using the setld utility to install layered products.

6.2 Installing a Kernel Product

To install a kernel product, the system administrator runs the setld utility, then reconfigures the kernel by running the doconfig utility. For example, the /dev/none driver could be installed as follows, assuming the kit is distributed on CD-ROM:

Place the CD-ROM in its caddy and insert it into the driver.
As superuser or root, create a directory to be the mount point for the CD-ROM, such as /mnt:
# mkdir /mnt
Mount the CD-ROM on /mnt. For example, if the CD-ROM device is located on the c partition of rz4, you would enter the following command:
# mount -r /dev/rz4c /mnt
Install the device driver:
# setld -l /mnt/ALPHA/ESA100

The setld utility displays prompts and messages to guide you through the installation process.
When the installation is complete, unmount the CD-ROM:
# umount /mnt

At this point, the kit is installed on the system, but the driver is not configured into the kernel. You must perform steps 5 - 8 to reconfigure the kernel.
Copy the current version of the kernel to another file, in case you need to recover it should the reconfiguration fail:
# mv /vmunix /vmunix.save
Set your default dirctory to /usr/sys/conf and run the doconfig utility to configure the driver into the kernel:
# cd /usr/sys/conf # doconfig
Copy the vmunix kernel from its current location to the / directory. The current location is the directory where the vmunix (the currently configured kernel) resides. This directory has the form /usr/sys/NAME/vmunix.
# cp vmunix /vmunix
Restart the system with the new kernel:
# /usr/sbin/shutdown -r now

When the system starts up, the /dev/none driver is available on the system.

See the Installation Guide for more information on using the setld utility to install layered products. See doconfig(8) for more information on the doconfig utility.

6.3 Installing a Foreign Device Product

The system administrator installs a foreign device kit with the osfboot utility, which runs from the console prompt. To follow this procedure, you need two kits: the CD-ROM containing the Digital UNIX kit and the kit containing the foreign device product.

For example, to install the /dev/edgd driver as a foreign device, run osfboot as follows:

Insert the Digital UNIX kit in the CD-ROM drive.
From the console prompt, invoke the osfboot utility with the fg flags, as follows:
>>> boot -fl fg dka400

The utility reads bootstrap code from the CD-ROM for the system you are installing.
The osfboot utility prompts you for the name of the device from which to install the foreign device. Enter the appropriate device name, for example:
Enter Device Name: dva0
The utility prompts you for the name of the kit containing the foreign device. To install the /dev/edgd driver, you would enter the following:
Enter Kit Name: edgd.kit
Insert the media and press the return key:
Insert media for kit 'dva0:edgd.kit', hit <return> when ready: [Return]
You may want to install more than one foreign device kit. Therefore, osfboot prompts you to enter more kit names. Press the return key to indicate that there are no more kits:
Enter Kit Name: [Return] Insert boot media, hit <return> when ready: [Return]
After you have entered all the kit names, osfboot proceeds to link the modules into the kernel. When the link operation has completed, it prompts you to insert the media containing the foreign device kit, then prompts you to insert the media containing the base system:
Insert media for kit 'dva0:edgd.kit', hit <return> when ready: [Return] Insert boot media, hit <return> when ready: [Return]

6.4 Installing a Product into a RIS Area

A user product or kernel product kit can be installed in a RIS area on a RIS server by running the ris utility. When the product has been installed in the RIS area, RIS clients can install the software from that RIS area using the setld utility.

To install the product in the RIS area on the server, run the ris utility as follows:

Log onto the server as root and invoke the ris utility:
# /usr/sbin/ris

From the RIS main menu, choose the option INSTALL software products by entering i at the prompt:

*** 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. Enter the option 1, Install software into a new area or 2, Add software into an existing area 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:

See Sharing Software on a Local Area Network for more information on installing software on the RIS area.

To install the product kit from the RIS server onto the client system, register the client system with the RIS server, then use the setld utility, as follows:

On the server, run the ris utility to register the client system by choosing option 2, ADD a client from the main menu:

# /usr/sbin/ris #

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

Enter the client information requested by the prompts, as described in Sharing Software on a Local Area Network.
As superuser or root on the client system, install the device driver subset from the RIS area. For example, if the RIS area is on node visier, you would enter the following command:
# setld -l visier:

The setld utility displays prompts and messages to guide you through the installation process. See the Installation Guide for more information on using the setld utility to install layered products.
If the product is a user product, the installation is complete. If the product is a kernel product, you must reconfigure the kernel using steps 4 - 7.
Copy the current version of the kernel to another file, in case you need to recover it should the reconfiguration fail.
# mv /vmunix /vmunix.save
Set your default directory to /usr/sys/conf and run the doconfig utility to configure the driver into the kernel:
# cd /usr/sys/conf # doconfig
Copy the vmunix kernel from its current location to the / directory:
# cp vmunix /vmunix
Restart the system with the new kernel.
# /usr/sbin/shutdown -r now