This appendix provides additional information about software options available when you are installing or removing the Prestoserve software.
The installation shell script is used to install and remove Sun Prestoserve software and files from the filesystem any time after the initial installation. It is an interactive program that prompts you for confirmation or input at each point where files might be changed.
The installation script decides whether you want to install or remove files by
looking for Sun Prestoserve files that are already installed. If there are files
already installed it removes them, or installs files from the Prestoserve
directory. You can force the install mode by using the
During installation, when the script asks for your input, you can stop the
program by pressing Control-C. You can then complete the installation process
later by restarting the installation script
Note - To install Sun Prestoserve on multiple servers, run the installation script on each server. This ensures that all the Sun Prestoserve files are correctly installed.
This walk-through of the installation procedure and script provides information about what is going on at each point in the process. This description only applies to the driver written for SunOS 4.x and Solaris 1.x. A detailed description of the installation script is not available for the Solaris 2.x script.
Note - Removing Prestoserve goes through the process in the same order as an installation, but some of the questions may change.
Begin by moving to the mounted cdrom/Prestoserve/dist directory and starting the presto_chango script:
# cd /cdrom/Prestoserve/dist
# presto_chango
When
The sd and id devices are the standard sun4c and sun4m disk devices. If you
want another disk driver type accelerated, use the "
Do you wish to remove Presto from host instead [no]?
If you answer "
Base path name for system kernel hierarchy [/sys]?
This path name determines which kernel building hierarchy is used to build a
kernel that contains the Sun Prestoserve device. Normally
* * * Making Presto changes to sys/sun/conf.c
* * * Presto-izing sys/sun4c/conf/files
* * * Creating the Presto special file entry /dev/pr0
Now,
* * * Creating sys/sundev/prtabs.c
* * * Adding Presto changes to sys/os/init_sysent.c
* * * Installing new Presto kernel files to sys
The following files are installed into the system build directory from the current directory.
sys/sun4c/OBJ/pr.o
sys/sundev/prtabs.c
sys/sundev/prestoioctl.h
Next,
Install Presto man pages [yes]?
If it could not find
Install Presto man pages [no]?
If you answer "y
Manual page path [/usr/man]?
Your response replaces
man/man1/presto.1
man/man1/prestotool.1
man/man3/prestoctl.3r
man/man4/presto.4
man/man8/prestoctl_svc.8
man/man8/presto_chango.8
If the man
Format new nroff copies of man pages (NOTE - this takes a while) [yes]?
If the man
Format new troff copies of man pages (NOTE - this takes a while) [yes]?
If the man
Update the man page directory (NOTE - this takes a while) [yes]?
Running
* * * Installing new Presto files
These files are installed from the current directory.
/usr/bin/prestotool
/usr/etc/presto
/usr/etc/prestoctl_svc
/usr/include/rpcsvc/prestoctl.x
/usr/include/sundev/prestoioctl.h
/usr/etc/presto_chango
Next
Config and make a Presto-ized kernel [yes]?
If you default,
System name in sys/sun4c/conf to config [sysname]?
If you want to inspect a kernel (for example, /vmunix) to see what
configuration file it was built from, use adb
% adb /vmunix
version? s
_version: SunOS Release XXX A #1: Thu Aug 17 17:08:39
The name of the configuration file is underlined in the example shown above.
* * * Config'ing
* * * Making sys/sun4c/sysname
After output is generated by the kernel make,
/vmunix.
Presto successfully installed on host!
Write down the name of the system that is displayed by
Note - This sections describes the steps for configuring a system using a non- standard disk controller. This section only applies to systems running the SunOS 4.x operating system. Nothing special needs to be done for systems running the Solaris 2.x operating system.
Devices identified as "sd" and "id" are standard Sun disk controllers. If you have a different disk controller that you want accelerated, install the non- standard disk controller's driver according to the manufacturer's instructions. Once you verify that the new kernel boots and that the new device is working correctly, run the Prestoserve installation script using the following syntax:
# presto_chango -i -p prefix
The argument to the
# presto_chango -i -p rf
If you want to Presto-ize additional disk drivers, repeat the previous
Note - This section only applies to systems running SunOS 4.x. The Prestoserve driver for Solaris 2.x no longer supports BOUNCEIO because modern disk controllers and NVRAM devices no longer require this function.
When controllers, drivers, and kernels cannot access SBus memory, Sun Prestoserve copies data buffers from Sun Prestoserve memory back into kernel memory before handing the buffers to the disk driver. This extra copy mode is called BOUNCEIO. BOUNCEIO solves the problem in a general way, but entails a performance penalty of about 5 percent (on heavy write loads, this can be as high as 20 percent). It can also increase the kernel memory usage by up to 128 Kbytes, and increase CPU utilization by about 5 percent.
By default, BOUNCEIO is NOT used for all non-standard disk controllers. To disable BOUNCEIO for a non-standard controller, run the installation script with the -b option and the -p prefix arguments during the installation procedure. If you have already installed Sun Prestoserve, you must remove Sun Prestoserve by running the script with the -p prefix and the -r arguments.
If you want to maximize your NFS server performance, call Sun Customer Service and ask for support. Tell them that you are using a non-standard controller, and ask whether BOUNCEIO is required for your particular environment.