Introduction: Pre-setting up information
based on freeware sco unix
Installation hardware requirements
Before installing SCO OpenServer Release 5, make sure your system has at least the
minimum required system memory and hard disk space.
All SCO OpenServer products are provided on a single CD-ROM. In addition to the
CD-ROM, separate media packages are available for customers who need a 150MB
cartridge tape or 3.5-inch floppy disks.
See the SCO OpenServer Development System Release and Installation Notes for SCO
OpenServer Development System installation requirements.
System memory
SCO OpenServer Release 5 installation requires a minimum of 8MB RAM for the Host
System and 12MB RAM for the Desktop or Enterprise Systems. We recommend at least
32MB RAM for optimal system performance.
Disk space
These sizes are representative and might not be the same on all systems.
Fresh installation type
For a default Fresh installation, the SCO OpenServer=D4 Host System requires 215MB, the
Desktop System requires 230MB, and the Enterprise System requires at least 240MB of
hard disk space. In each case, 15MB is reserved for /stand, and swap space is an additional
requirement. French and German language support require 17MB per language.
To accommodate more than one graphical user, we strongly recommend that you specify
swap space that is 150% to 200% as large as the RAM in your system. For non-graphical
systems, we recommend swap space that is 150% as large as the system's RAM. The default
minimum swap space presented during installation is 24MB.
You can make the root filesystem much larger than 200MB, as the new DTFS and HTFS
filesystem types do not require that you keep your root filesystem small. The /stand (boot)
filesystem must be large enough to hold three kernels, plus some extra software. It defaults to
15MB; we strongly recommend at least 10MB.
Using the ATAPI (EIDE CD-ROM) driver
The ATAPI driver provides support for Extended IDE (EIDE) CD-ROM drives by
representing the drive as a SCSI device to the operating system.
In order to present a consistent interface, the following restrictions apply:
A maximum of two IDE controllers can be present on any system.
No more than two IDE devices may be present on any one IDE controller.
If there is only one IDE device on a controller, it must be configured as a Master
device. If there are two devices on the controller, one must be configured as a Master
device and the other as a Slave device.
If only one IDE controller is present, it must be configured as the Primary controller. If
there are two controllers, one must be configured as Primary and the other as
Secondary.
NOTE: The procedure you need to apply to install and configure EIDE- or IDE-interface
hardware (controllers, disk drives, and ATAPI CD-ROM drives) for your system is
described in the documentation provided by your hardware supplier. Any information
provided by your hardware supplier might invalidate the information here.
ATAPI (EIDE CD-ROM) installation procedure
To install your system using an Extended IDE CD-ROM drive:
1.Boot from the boot disk.
2.Enter restart or press at the Boot: prompt.
If your system has a primary SCSI hard disk drive attached to a SCSI controller, you
must alter the bootstring to define this configuration. For example, if the primary hard
disk drive has a SCSI ID of 0, a LUN of 0, and it is attached to the primary bus
controlled by an Adaptec 2940 host adapter (which uses the alad driver), use the
following bootstring:
Boot: defbootstr Sdsk=alad(0,0,0,0)
If you have a different SCSI host adapter, use the appropriate driver name from the
following table instead of alad:
------------------------------------------------------------------
Host adapter Driver name
------------------------------------------------------------------
Adaptec 152x spad
Adaptec 154x, 154x emulation, 164x ad
Adaptec 174x eiad
Adaptec 274x (7770 chip) arad
Adaptec 2940x (7870 chip) alad
Future Domain 1650, 1670, 1680, 600, 700 (1800 chip) fdha
Future Domain 7000 wdha
Future Domain 7000ex wdex
Future Domain 845, 850, 860, 885 (950 chip) tmcha
Olivetti ESC-1, ESC-2, and EFP efp
Storage Plus SCSI-AT (SUMO) sumo
See Using bootstrings in the SCO OpenServer Handbook for more information.
3.When the Identifying the installation media device screen is displayed, choose SCSI
CD-ROM as the media device type.
Some machines may experience hardware driver conflicts which will not allow the user
to choose any SCSI media devices for installation. One way to work around this
problem is to insert a supported SCSI host adapter into the system. There is no need
to add any SCSI devices to this host adapter.
4.Select wd for the SCSI host adapter type.
5.If the CD-ROM drive is attached to the Primary IDE controller in a system with one or
two IDE controllers, select 0 for the host adapter number.
If the CD-ROM drive is attached to the Secondary IDE controller in a system with two
IDE controllers, select 1 for the host adapter number.
6.If the CD-ROM drive is configured as a Master device, select 0 for its SCSI ID.
If the CD-ROM drive is configured as a Slave device, select 1 for its SCSI ID.
NOTE: A hard disk and a CD-ROM drive present on the same IDE controller are
usually configured as Master and Slave devices respectively. If no hard disk drive is
present on the same controller, the CD-ROM drive will usually have been configured
as a Master device.
7.Select 0 for the SCSI LUN of the CD-ROM drive.
8.Select 0 for the SCSI bus number.
>From this point, continue with the installation as described in the SCO OpenServer
Handbook.
Determining your system configuration for ATAPI (EIDE CD-ROM)
If you are uncertain of the hardware configuration of your system, but you know that the
primary hard disk is attached to an IDE controller, the following information will allow you to
determine the most likely configuration.
Entries for the ATAPI CD-ROM will take one of the following forms as indicated by the
presence of the string type=3Dwd:
%adapter 0x01f0-0x01f7 14 - type=3Dwd ha=3D0 id=3D7 bus=3D0 fts=3Dd
Here, ha=3D0 indicates that the ATAPI CD-ROM drive is attached to the Primary IDE
controller.
%adapter 0x0170-0x0177 15 - type=3Dwd ha=3D1 id=3D7 bus=3D0 fts=3Dd
Here, ha=3D1 indicates that the ATAPI CD-ROM drive is attached to the Secondary IDE
controller.
If there is another device attached to the IDE controler, the effective SCSI ID of the
CD-ROM drive is 0 if it is configured as a Master device or 1 if it is configured as a Slave
device. If the other device is the primary hard disk drive, the CD-ROM drive will normally be
configured as a Slave device. If your system has a primary SCSI hard disk, the CD-ROM
drive may be configured as a Master device.
If there is no other device attached to the IDE controller, the CD-ROM drive should have
been configured as a Master device with an effective SCSI ID of 0.
NOTE: The base I/O addresses and interrupt vectors shown on your system might differ
from the examples shown above.
If you are in doubt as to your system configuration, check the documentation that was
supplied with your hardware.
Configuring the system for additional users and CPUs
When you add users to your SCO OpenServer system, the demand on various system resources
increases. When you license additional users with the License Manager, it prompts you, just before
exiting, to tune kernel resources to accommodate the higher demand. We strongly recommend that
you choose to allow the License Manager to tune the resources for you. Once the resources are
tuned, the License Manager prompts you to relink the kernel. Relinking the kernel at this point
ensures that the modifications are saved. To activate the modified kernel, reboot the system.
NOTE: When you add SCO User Licenses, the License Manager tunes a basic set of kernel
resources. Refer to the Performance Guide for detailed information on tuning the kernel to match the
needs of your particular system configuration.
When you remove SCO User Licenses, the License Manager does not tune the kernel to reflect the
change in demand on system resources.
When you license or unlicense one or more additional CPUs, the License Manager modifies the
MAXACPUS kernel parameter automatically. Therefore, before exiting, the License Manager
prompts you to relink the kernel. Relinking the kernel at this point ensures that the required
modification is saved. To activate the modified kernel, reboot the system.
WARNING: If you have installed SCO Symmetrical Multiprocessing Support, and any additional
CPUs are licensed, then all additional CPUs must be licensed at the same time. Failure to do so might
cause some systems to hang when you reboot.
License Manager and kernel parameters
When new user licenses are added to the system, the License Manager adjusts the following kernel
parameters according to the number of users:
serial I/O parameters: NCLIST, TTHOG
Streams memory parameters: NSTREAM, NMUXLINK, NSTREVENT, NSTRPAGES
number of Stream pipe connections: NUMSP
number of pseudo-ttys: NSPTTYS
number of TCP/IP and UNIX domain sockets: NSOCKET, NUSOCOTS
If your system is licensed for more than 5 users and you did not use the License Manager to add the
user licenses, you may need to modify these parameters manually. See Configuration tools in the
Performance Guide for more information.
The License Manager also increments the MAXACPUS kernel parameter when additional CPUs are
added, so you might need to modify this parameter if you failed to run the License Manager. (The
base processor is not included in the count of CPUs.)
SETTINGS MANAGER
The International Settings Manager allows you to specify both the codeset used internally by the
system (in other words, the way in which data is represented when it is written to disk and
manipulated by various programs) and the codeset used on the system console.
NOTE: The information here updates the procedure for setting codesets in Setting the internal
system codeset in the SCO OpenServer Handbook.
The single-byte codesets supported by SCO OpenServer systems can represent a maximum of 256
characters. For this reason, you might benefit by setting the internal system and console codesets
differently for different uses. For example, the IBM codesets (codepage 437 and codepage 850)
contain better line-drawing characters and are useful as console codesets. The ASCII and
ISO8859-1 codesets, however, contain all the characters necessary to represent the American
English and Western European languages, respectively. Selecting a console codeset which is different
from the internal system codeset will set up mappings to ensure that data continues to be interpreted
correctly.
To set the system console codeset:
1.Log in as root.
2.Start the International Settings Manager by entering scoadmin i at the prompt, or selecting:
System Administration -> System -> International Settings Manager
from the desktop.
3.Select Codeset from the Settings menu.
4.Select Console from the Codeset submenu.
5.Select the name of the codeset you want to use and click on OK.
6.Select Save from the File menu.
7.Exit the International Settings Manager.
8.Reboot the system.
The system console is not actually a single device, but rather a combination of both the console
keyboard and the console monitor. Selecting the console codeset will install a console font (see the
vidi© manual page), establish the list of available system keyboard mapping files, and establish any
additional mapping required if the console codeset is not the same as the internal system codeset.
To set the internal system codeset, follow the procedure for setting the console codeset, but select
Internal from the Codeset submenu.
NOTE: Changing the internal system codeset will dynamically change the list of the console codesets.
The internal codeset is used as a primary selection upon which the secondary codeset depends.
Therefore, the default console codeset might change if you change the internal system codeset
selection.
Changing the internal system codeset also changes the list of available locales. It might also change the
way that data previously in use on the system is interpreted. After selecting the internal system
codeset you should review the device mappings and user locales under the Settings menu to ensure
that the mappings set up for each device are still appropriate and that the language each user has
selected is still supported by the system.
Installing and configuring PC-Interface
See also the PC-Interface Guide, which contains detailed information on administering and using
PC-Interface™.
System requirements
To install and run the PC-Interface server, you need:
Any appropriate computer running the SCO OpenServer Enterprise System. TCP/IP
networking software is required if you plan to provide LAN services to PC-Interface clients.
A minimum of 2.8MB of disk space in /usr.
Cabling to the LAN (if you plan to offer LAN services).
Cabling to each computer that is to be connected for RS-232 service. Each computer requires
its own serial port on the server.
If you are using routers on your network, see Modifying routers to handle PC-Interface
broadcasts in the PC-Interface Guide.
Installing the PC-Interface server
The PC-Interface server is automatically installed during a full SCO OpenServer installation. If you
did not initially perform a full installation and want to install PC-Interface, use the custom command to
install PC-Interface from the SCO OpenServer Connectivity package.
NOTE: If a previous version of the PC-Interface server exists on your system, remove it with custom
before installing a new version.
See Installing software in the SCO OpenServer Handbook for more information on using the
custom interface.
Configuration and tuning
You can configure and tune your SCO OpenServer system for the PC-Interface server using the
configure program as root. The program leads you through the steps of altering your system
configuration, including automatically updating the configuration files and rebuilding the kernel. For
complete information on how to use this program, see the configure(ADM) manual page and the
Performance Guide.
NOTE: After modifying any of the values shown in the following tables, you must relink the kernel
and reboot the system to implement the changes or the modified configuration will not properly reflect
the actual system.
Two sets of values are given in the tables, one for RS-232-only systems and one for RS-232 and
LAN systems. The values given should be added to your current values; they should not replace
them.
When using configure, you are first provided with a menu that divides the configurable parameters
into different sections. Within each of these sections, you are asked for new values for each
parameter. The parameters that you should change for the PC-Interface server are outlined below,
along with the sections in which they are kept.
For servers providing RS-232 services only:
-----------------------------------------------------------------------
Section Variable 1-16 User 17-32 User 33-64 User
-----------------------------------------------------------------------
Semaphores SEMMNI + 20 + 40 + 80
Semaphores SEMMNU + 40 + 80 + 160
Shared Data SHMMNI + 20 + 40 + 80
For servers providing LAN and RS-232 service:
------------------------------------------------------------------------
Section Variable 1-16 User 17-32 User 33-64 User
------------------------------------------------------------------------
Semaphores SEMMNI + 20 + 40 + 80
Semaphores SEMMNU + 40 + 80 + 160
Shared Data SHMMNI + 20 + 40 + 80
Streams Data NSTREAM + 20 + 40 + 80
Streams Data NUMTIM + 20 + 40 + 80
Local configuration using environ
You can perform configuration that is specific to the PC-Interface server by modifying the environ file
in /usr/pci/bin/environ. This file is a Bourne shell script that is invoked when the pcistart script is run
and whenever an RS-232 user logs in for file service. See Configuring the server environment in
the PC-Interface Guide for a description of the environment variables that you can set in this file.
Network configuration
PC-Interface makes use of whatever name resolution procedure is in use on your system. For
information on setting up the Domain Name Service (DNS) on your PC-Interface server, see
Chapter 6, Configuring the Domain Name Service in the Networking Guide.
Configuring pseudo-tty ports
By default, the LAN version of the PC-Interface server is configured with six terminal emulation
ports. Two RS-232 ports are configured. To add or delete terminal emulation ports for PC-Interface
users, see Procedure for enabling and disabling ports in the PC-Interface Guide.
Starting and stopping the server
When the SCO OpenServer system enters multiuser mode, it runs the script /etc/rc2.d/S95pci. This
program verifies some aspects of your SCO OpenServer system and invokes pcistart. For more
information, see the pcistart(PCI) manual page.
When an SCO OpenServer system is shut down, it runs the script /etc/rc0.d/K95pci. This script
shuts down the PC-Interface server in an orderly fashion.
The pcistop script is also available to root at any time, so root can manually stop the PC-Interface
server. However, because of system-required security, it is not possible to restart the PC-Interface
server without rebooting the system.
Installing and configuring SCO Gateway for NetWare
See also the Guide to Gateways for LAN Servers, which contains detailed information on
administering and using SCO® Gateway for NetWare®.
System requirements
To install and run SCO Gateway for NetWare, you need:
One or more NetWare file servers (and, optionally, print servers) to connect to. Each must run
NetWare Version 2.2, 3.11, 3.12, 4.01, 4.02, or 4.1, and should have the NetWare
Loadable Module (NLM) installed and running where appropriate. See Installing and
configuring the NetWare component of SCO Gateway for NetWare for more information.
An SCO OpenServer system on which IPX/SPX is configured.
Networking cards and cabling to connect the SCO OpenServer system to a LAN.
Configuring the UNIX component of SCO Gateway for NetWare
SCO Gateway for NetWare is automatically configured over IPX/SPX during a Fresh installation
when both IPX/SPX and SCO Gateway for NetWare are being installed and IPX/SPX configuration
information is supplied. For all other scenarios, follow the instructions below.
Use the Network Configuration Manager to configure SCO Gateway for NetWare over IPX/SPX:
1.As root, enter scoadmin Network Configuration Manager.
2.Select the adapter already configured for use with IPX/SPX, to which you want to add SCO
Gateway for NetWare.
3.Select Add protocol from the Protocol menu.
4.Select SCO Gateway for NetWare and click on Add.
5.When prompted, click on Yes to relink the kernel. Answer Yes to the following two kernel
questions.
6.Reboot your system.
(c)1998 David A Dalby WEBMASTER: dadalby@yahoo.com