This document provides installation instructions and release notes for the OpenServer Kernel Personality (OKP) for UnixWare 7.1.3. After you read this document and install OKP, go to the UnixWare online documentation, served by DocView on http://hostname:8458, where hostname is the network name or IP address of your UnixWare system. Select OpenServer Kernel Personality to view the OKP documentation.
OpenServer applications run in an OpenServer execution environment. Key OpenServer runtime utilities, libraries, system calls, internationalization and localization facilities, as well as terminal and console definitions are available in this environment.
OKP requires a UnixWare 7.1.3 system with one of the following software configurations:
For good OKP performance, we recommend a minimum of 128MB RAM, 400MB free disk space for OKP and the OpenServer image, and additional disk space for applications and application data. While OKP will run on any processor on which UnixWare will run, a faster processor will yield better overall system performance.
OKP is designed to work with OpenServer 5 Release 5.0.4 through 5.0.7 system images; see OpenServer System Image.
The general process for installing and setting up OKP to run your OpenServer applications is to:
If you have an existing OpenServer system, install and configure required applications on the OpenServer system.
Install the osrcompat set.
Copy an OpenServer system image either from an existing OpenServer system or the OKP Full CD product.
If you used the OKP Full CD product, log in to OKP to install and configure applications.
Log in to UnixWare to create the required users and groups for your OpenServer applications.
Log in to OKP and start your OpenServer applications.
The remainder of this document explains these steps in detail.
Before you can use OKP, you must populate the OpenServer compatibility directory, /openserver, with the files and directories from an OpenServer 5 system.
This can be done during installation or afterwards from the command line, as summarized in the following figure.
If you have the CD-ROM version of the product and the appropriate license (see OKP Licensing), you can use the generic OpenServer 5.0.7 image provided on the CD. Using OKP with this image means that you will need to install your OpenServer application under OKP, after populating /openserver. Be aware that some restrictions on installing applications directly under OKP exist; see the section OKP Notes and Limitations in the online documentation on http://hostname:8458 under OpenServer Kernel Personality. for more information.
The recommended method for using OKP is to set up your applications on an existing OpenServer system and then copy the OpenServer system over to the UnixWare/OKP system. Migrating your application from a running OpenServer system has the advantage of preserving the application execution environment, eliminating the need to configure the application under OKP.
In some cases, this will be the only way to migrate an application to OKP. One example is any software that requires a license on installation; since OpenServer licensing is not supported by the UnixWare licensing software, such an application cannot be installed directly under OKP. Instead, it must be migrated from an OpenServer system.
Migration from an existing OpenServer system is accomplished in one of two ways:
Since the system image is large (at least 200MB, plus your applications and data), we recommend using osragent(1M) if you don't want to tie up your network transferring the system image. You can copy the image to tape or recordable CD on OpenServer for installation on UnixWare/OKP. This is also a useful way of keeping a backup copy of the OpenServer system for OKP.
Note that osragent(1M) must be copied from the UnixWare system to the OpenServer system, and then run on OpenServer to create the image.
The procedure in the section ``Installation and Getting Started'' includes instructions for performing these tasks.
There are two versions of the OKP product:
Includes all the features of OKP except for the ability to load the OpenServer 5.0.7 image from the CD-ROM version of the OKP product. This license requires that you have an existing OpenServer system available to migrate to OKP.
OKP Lite consists of the OKP Package Set, osrcompat_060303_Lite.image, and the OKP Lite license, which is available free of charge. The OKP Package Set is approximately 140kb in size, and contains:
To use OKP Lite, download the OKP Package Set and install using the instructions under Installation and Getting Started. You will need to provide OKP license activation information. When prompted, use the following OKP license activation data:
License Number: UWOKPLITE License Code: dvxwknwt
If you want to use the Full version of OKP, you need to purchase a separately orderable license. This license permits the use of the complete OpenServer 5.0.7 product contained on the OKP CD ISO image.
The OKP CD ISO image, osrcompat_060303_Full.iso, contains the OKP Package Set and the OpenServer 5.0.7 product image. The OKP CD ISO image is approximately 280Mb in size.
To use OKP Full, download the OKP CD ISO image and install using the instructions under Installation and Getting Started. Enter the OKP license information for the license you purchased when prompted.
Follow this procedure to install and begin using OKP:
If you want to copy an OpenServer system image over the network from an existing OpenServer system, you must:
chmod 600 /.rhosts /etc/hosts.equiv
# rsh sysname uname -s SCO_SV
pkgadd -d device osrcompat
Where device gives the location of the package. Use cdrom1, for example, for the first CD-ROM drive. If you have a package image (a file named osrcompat.image), use path/osrcompat.image for the device, where path is the full pathname to the file.
shutdown -i6 -g0 -yor the scoadmin shutdown manager.
/usr/lib/okp/bin/migrate -h <system_name>
If there is a problem accessing the OpenServer system, make sure you enabled root access as outlined in Step 1. The migrate command can take significant time and network errors can occur during the transfer.
/usr/lib/okp/bin/import
/tmp/osragent >/tmp/bigfile
/usr/lib/okp/bin/migrate -i /var/pkg/spool/bigfile
/usr/lib/okp/bin/import
mount /dev/cdrom/cdrom1 /mnt ls -l /mnt/okp_images /usr/lib/okp/bin/migrate -v -i /mnt/okp_images/<filename>
Where <filename> is the name of the image file on the CD.
/usr/lib/okp/bin/import
After you run migrate and import, you can begin using OKP.
If you are moving a large number of accounts from an existing OpenServer system, you can use the ap utility to automate the transfer. There is a version of ap on both OpenServer and UnixWare. The basic process for using ap is to run it on OpenServer, copy the output to the UnixWare system, and run ap on UnixWare using the OpenServer account information as input. See the ap(1M) manual page on UnixWare, and the ap(ADM) manual page on OpenServer.
Once installed, use the following command to confirm that the osrcompat set has completely installed. The system should respond with output similar to that shown in the example below:
# pkginfo -lc set osrcompat PKGINST: osrcompat NAME: OpenServer and Xenix Personality CATEGORY: set ARCH: IA32 VERSION: 1.0.0 VENDOR: SCO DESC: OpenServer and Xenix Personality for UnixWare PSTAMP: scowl20030326194332 INSTDATE: May 30 2003 09:22 AM STATUS: completely installed
If the STATUS field indicates anything other than completely installed, there was some problem during installation of the set. Re-install the set and record any error messages displayed.
Follow these instructions to remove an already imported /openserver directory from the system and repopulate it using the import command. Be sure that you no longer need any of the data currently under /openserver, or save a copy to backup media, before beginning.
/usr/lib/okp/bin/unimport
shutdown -i6 -g0 -y
rm -fr /openserver
To completely remove OKP, the OpenServer system image, and all OpenServer applications and data from your system, enter the following commands, logged in as root.
shutdown -i6 -g0 -y
INITSTATE=S boot
pkgrm osrcompat
/usr/lib/okp/bin/unimport
rm -fr /openserver
This section lists the known problems that affect installation, or that were discovered too late to be included in the online documentation. See the OKP Notes and Limitations section in the online documentation on http://hostname:8458 under OpenServer Kernel Personality.
Errors have been observed when an rsh command is used in a pipe, as is done internally by the import(1M) command. While import does not return an error, executing the openserver(1) command returns:
UX: openserver: WARNING: unable to change directory into /unixware/ UX: openserver: ERROR: Exec error: Exec format error
To work around this error, run the import(1M) command again.
527265
If you choose to cancel installation of the osrcompat set, or if the installation is aborted because a license was not found or entered, the okpdoc or xemul (or both) packages may still be installed, depending on when the install was cancelled. If xemul is installed, the kernel will be rebuilt on the next reboot. If you intend to re-install osrcompat, there is no need to remove these packages. If you do want to remove them, enter one or both of the following commands as root:
pkgrm -n okpdoc pkgrm -n xemul
527924
When starting the OpenServer version of Netscape under OKP, one or more of the following errors may be displayed:
/opt/netscape/netscape: too big /dev/rroot: not found
These error messages are harmless and can be ignored.
527927/527913
The unimport process performs a number of cleanup tasks, including attempting to remove any lingering mounted file systems whose content might be deleted unintentionally when the /openserver directory is removed. Some mounts may be left behind by the unimport command, however, if there are OpenServer processes running when unimport is executed. This can lead to data loss. To prevent this, the system should be rebooted into single user mode before running unimport, as shown in the section Removing OKP.