Release Notes: SCO UnixWare ESP Driver
Release notes for version 3.14 of the ESP software for SCO UnixWare.
Supported UnixWare Releases
The ESP driver and associated software is only supported on UnixWare releases 7.0.1a, 7.1.0 and 7.1.1 and later. This driver may also be used on OpenServer 6 systems.
Installation
The driver package can be installed using the standard procedure for installing UnixWare packages:
- pkgadd –d diskette1
- pkgadd –d <datastream file location>
The pkgadd utility will fail if the espx package already exists. It must be removed using pkgrm before the pkdadd will succeed.
Components
The following are provided on the installation diskette:
- version 3.14 of the espx device driver
- versions 3.14 of the diagnostic utilities (esp, espcfg, espdiag and esptty)
- system man pages.
Installation From Equinox FTP Site
The following steps should be followed to update and configure the ESP driver on the UnixWare system.
1. Transfer the driver image to the UnixWare system.
This step is required only if you downloaded the file to a DOS system. You may skip this step if you downloaded directly to the UnixWare system.
a. Copy the archive file onto a high density DOS diskette.
"copy esp_unixware_314.Z a:"
b. Remove the DOS diskette and insert into the UnixWare system.
c. Copy the file into the /tmp directory:
if you are using Unixware 2.0.0 or above:
"doscp a:esp_unixware_314.Z /tmp/esp_unixware_314.Z"
if you are using Unixware 7.0.0 or above:
“mount –F dosfs /dev/dsk/f03ht /mnt”
"cp /mnt/esp_unixware_314.Z /tmp/esp_unixware_314.Z"
“umount /mnt”
2. Uncompress the driver file from the download file .
a. Change directory to /tmp:
"cd /tmp"
b. Uncompress the driver file in the /tmp directory:
"uncompress esp_unixware_314.Z"
This will create a file with the same name as the download file without the extension .Z, i.e. “ esp_unixware_313"
This file is a media image of an installable floppy.
3. Build installation media .
There are two installation options: install directly from datastream file or install from floppy.
a. Installation from Datastream file
Proceed to step 4.
b. Installation from Floppy
b1. Insert a blank UNIX formatted 3.5" HIGH DENSITY diskette into the first drive on your UnixWare system.
b2. Copy the uncompressed file from the /tmp directory to the floppy using "dd" " dd if=/tmp/esp_unixware_314 of=/dev/rdsk/f03ht bs=1024 "
NOTE: Check your operating system documentation for the correct syntax to use for your floppy drives.
4. Install the Driver
a. Remove existing driver
“ pkgrm esp”
b. Install the driver using pkgadd utility.
To install from datastream file:
“pkgadd –d <datastream file location>”
Note that the full path to the datastream file must be specified.
To install from diskette:
5. Configure the ESPs
Configure and enable the ESPs using the "espcfg" program. A man page is provided with the installation. You can check the status of the ESPs after they are configured using either the "esptty" utility or the "espdiag" utility. Man pages are provided for these utilities as well. There is also an overview man page named "esp".
The "espcfg" program will be invoked automatically during the installation of the package. If this is an upgrade and there is an existing configuration file (/etc/eqnx/esp.conf) you will be asked if you want topreserve the existing configuration.
Please refer to the SCO UnixWare documentation for information on how to configure ports for login, printing, and other serial capabilities (i.e., cu).
The device names in the file system space follow UnixWare conventions.
For example, ESP 1 will have names like /dev/term/01e0t (the direct connect device) or /dev/term/01e0m (modem device). The generic name /dev/term/01e0 maps to the modem device.
The "01" in the name reflects the ESP number assigned by espcfg and the ports range from 0 (zero) to f (Hexadecimal for 15). On ESPs with less than 16 ports the range of port numbers will match that of the ESP (e.g., 0 to 8 on an 8 port ESP, 0 to 1 on a 2 port ESP).
Differences between release 3.13 and 3.14:
- Added support for ESP-8 MI and ESP-16 MI models.
- Changes to support "Avocent" branding.
- Fix to espcfg to eliminate problem with clearing ARP cache after removing an ESP.
Differences between release 3.12 and 3.13:
- Added support for ESP-4 MI models.
|
