These Release and Installation Notes contain critical information that you need to know before and after installing SCO OpenServer Release 5.0.7 Update Pack 3. Familiarize yourself with the information that is relevant to your system, then install the Update Pack according to the instructions in this document.
These Release and Installation Notes cover the following topics:
There are two support ``tracks'' that are available to SCO OpenServer Release 5.0.7 customers:
Update Packs supplement the Maintenance Packs. Each Update pack requires the installation of a corresponding Maintenance Pack. Update Packs are cumulative, so you only need to install the latest Maintenance Pack plus the latest Update Pack to bring the system up to date with the latest features and enhancements.
SCO OpenServer Update Packs are available
for download from the SCO OpenServer Release 5.0.7 Update Pack web page:
http://www.sco.com/support/update/download/osr507up.html
A registered SCO Update Service license is required to install SCO OpenServer Update Packs. See ``Registering your SCO Update Service license'' for more information.
Update Pack 3 can only be installed on an SCO OpenServer Release 5.0.7 system. Previously released Update Packs do not need to be removed before proceeding.
Before you can install SCO OpenServer Release 5.0.7 Update Pack 3, you must:
See the SCO OpenServer Release 5.0.7 Maintenance Pack 3 Release and Installation Notes for installation information.
You are now ready to install Update Pack 3.
An SCO Update Service (SUS) Enabler license is required to use any of the Update Packs for SCO OpenServer Release 5.0.7. This license is available in two forms:
To determine if your SCO operating system is
bundled with SCO Update, run:
/etc/brand -L | grep "a120;"
If this command returns output, your operating system license also contains the SUS Enabler license.
To verify that an add-on SUS Enabler license was successfully installed, run the License Manager and check that the SCO Update Service is displayed in the list of currently installed licenses.
See ``Licensing and registering SCO OpenServer products'' in the SCO OpenServer Handbook for information on using the License Manager to install and verify licenses.
Both your SCO OpenServer Release 5.0.7 license and
SCO Update Service Enabler license
must be registered before you can install
an SCO OpenServer Release 5.0.7 Update Pack.
You can do this at the SCO OpenServer Product Registration web page:
http://www.sco.com/support/registration
After you register the SUS Enabler license, you will notice that an additional SCO OpenServer Update Service license automatically appears in the License Manager. This license is generated and installed on your system when you complete the SCO registration process. When you see this license in the License Manager, it means that the SCO Update service has been successfully activated.
See ``Registering SCO OpenServer products'' in the ``About SCO OpenServer systems'' chapter in the SCO OpenServer Getting Started Guide for more information on registering products and licenses.
You can acquire and install SCO OpenServer Release 5.0.7 Update Pack 3:
If there are multiple systems on your TCP/IP network that require Update Pack 3, you can load or install the UP on a software server and use it as a centralized distribution point. See ``Installing Update Packs across the network'' for more information.
Update Pack 3 can be installed directly on top of Update Packs 1 or 2. Should you need to remove any of the Update Packs, however, see ``Removing an Update Pack''.
The SCO Update feature of the Software Manager allows you to install Update Pack 3 directly over the Internet. This approach saves you the time -- and extra hard disk space -- of first downloading installable image files from the SCO web or FTP sites.
To run SCO Update:
The Install Selection window displays all of the SCO OpenServer Release 5.0.7 update packs, maintenance packs, drivers, and so forth that are currently available.
The Update Pack software is automatically installed on your system.
If any Update Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Update Pack as only partially installed. This is normal.
To install Update Pack 3 from media images that you manually download:
If you download the individual files rather than the tar archive, please be sure to carefully verify that all of the sequentially-numbered VOL files are present in your download directory before proceeding.
Click on OK.
If any Update Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Update Pack as only partially installed. This is normal.
To install SCO OpenServer Release 5.0.7 Update Pack 3 from the SCO OpenServer Release 5.0.7 Supplement CD Version 3:
If any Update Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Update Pack as only partially installed. This is normal.
You can install SCO OpenServer Release 5.0.7 Update Packs from one SCO OpenServer Release 5.0.7 system onto another across a TCP/IP network. To do so, you need a software server, which you can create as described in ``Installing and managing software over the network'' in the SCO OpenServer Networking Guide. This server has a user account called swadmin.
Install or load the Update Pack on the software server using one of the installation procedures described in ``Installing the Update Pack''. Also see ``Installing and managing software components'' in the SCO OpenServer Handbook for more information on loading software.
To install an Update Pack onto a local machine once the Update Pack is available from the software server, start the Software Manager and select Install New. In the Begin Installation window, you are prompted for the source location of the Update Pack. Select From Another Host. You need to provide the name of the software server, as well as the password of the swadmin user on the software server.
It is not necessary to remove previous Update Packs prior to installing the latest Update Pack.
To remove an SCO OpenServer Release 5.0.7 Update Pack:
Update Pack 3 comprises Update Packs 1 and 2, plus the following new features:
Update Pack 2 provided the following:
Update Pack 1 provided the following:
The foomatic package contains a generic printer filter and PPD (PostScript Printer Definition) files for over 200 non-PostScript printers. The filter and PPD files are integrated with the CUPS package and cannot be used with the System V LP print system. (Note that the CUPS package also provides its own PPD files. For more information, see the Printing topic in the online documentation.)
Further documentation on the printers supported by foomatic is available at:
http://www.linuxprinting.org/printer_list.cgi
You can search this site for the proper driver name for your printer, then look for the driver in the Make/Model selection list displayed by the CUPS graphical interface.
Foomatic is also a standalone system that creates PPD files from an XML database and includes tools for direct printing. The PPD creation program is called foomatic-rip(1) and the database is called foomatic-db.
The HP-supplied hpijs printer driver is provided in conjunction with Ghostscript to support improved printing on a large number of HP DeskJet and LaserJet printers.
Update Pack 3 includes DVD writing support with the dvdrecord(C) command, a port of the ProDVD utility. The command options for cdrecord (provided in Maintenance Pack 3) and dvdrecord are virtually identical. The dvdrecord(C) manual page is provided (and is maintained) by SCO. It contains basic information on creating CD and DVD data discs and includes key examples. cdrecord(1) is the generic documentation provided with the free software and is not specific to SCO UNIX operating systems. Refer to cdrecord(1) for the complete option set and information on creating specialized disc layouts and formats.
ProDVD has been reported to work with most DVD drives. The following drives have been tested on SCO OpenServer Release 5.0.7:
PostgreSQL is an object-relational database management system (ORDBMS) based on POSTGRES, Version 4.2, developed at UC Berkeley. This is an update to the version provided in Update Pack 2. The online documentation has been updated and the mkdev pgsql menus have been enhanced.
After the package is installed, PostgreSQL must be configured by running
this command:
mkdev pgsql
This script allows you to view or configure
the application defaults and
manage administrative processes. The configuration options include:
1. Enable PostgreSQL
2. Disable PostgreSQL
3. Start PostgreSQL postmaster process
4. Stop PostgreSQL postmaster process
(after all clients have disconnected)
5. Stop PostgreSQL postmaster process NOW
6. Restart PostgreSQL postmaster process
(after all clients have disconnected)
7. Restart PostgreSQL postmaster process NOW
8. Set PostgreSQL database owner
9. Set PostgreSQL database directory
mkdev pgsql fails to start up the postmaster process properly if SSL has been configured to use paraphases. This is because the script does not pause to allow the paraphase to be entered and the prompt scrolls off the screen. The workaround is to run pg_ctl start manually and enter the paraphrase when prompted.
This release of PostgreSQL for SCO OpenServer Release 5.0.7 does not support UNIX domain sockets. It is instead configured to use TCP/IP sockets. The default configuration allows all local users to connect to the server and remote connections are not allowed. To configure the server to allow remote connections and/or restrict local connections, edit the pg_hba.conf configuration file in your PostgreSQL data directory (the default location is /usr/pgsql/data).
For example, to enable client access to the database server from all users at IP address 1.2.3.4, you would add the following line to pg_hba.conf:
host all all 1.2.3.4 255.255.255.255 trustUsers on IP address 1.2.3.4 would need to set the PGHOST environment variable to the name of the PostgreSQL server. For instance, if the server was running on the system foo.bar.spam.com then clients on IP address 1.2.3.4 would set the following in their shell environment:
PGHOST=foo.bar.spam.com
Because the database format has been since version 7.3.4,
databases must be dumped and restored for use under 7.4.2.
Instructions for performing a 7.3.x to 7.4.x upgrade can be
found in
Chapter 14: ``Installation instructions'' under Section 14.4: ``If you are Upgrading''
in the online PostgreSQL documentation, or externally at:
http://www.postgresql.org/docs/7.4/static/install-upgrading.html
The upgrade procedure refers to /usr/local/pgsql and /usr/local/pgsql/data as the default installation and data directories. On SCO OpenServer Release 5.0.7 these locations are /usr/pgsql and /usr/pgsql/data, respectively.
You should also save your previous PostgreSQL configuration files (pg_hba.conf, pg_ident.conf, and postgresql.conf) and make the appropriate configuration changes to the newly installed PostgreSQL configuration files. Remember to stop the daemon before upgrading.
The PostgreSQL package also includes the latest Java JDBC driver,
which provides a standard set of interfaces to SQL-compliant databases.
You can find documentation at:
http://doc.postgresintl.com/jdbc/index.html
To use the pgtclsh and pgtksh utilities, you will need
to install TCL and Tk 8.4. These are available as part of
the GNU Tools version 5.0.7Kj, which can be obtained at:
ftp://ftp.sco.com/pub/openserver5/opensrc/gnutools-5.0.7Kj
First provided in Update Pack 2.
This Update Pack includes support for USB printers. Although the support is general, it depends greatly on the capabilities of the printer. CUPS provides a small set of printer drivers (also called PostScript Printer Definition files, or PPD files). If the printer descriptions supplied with CUPS do not meet your needs, support for various ``Windows-only'' (GDI) printers is available by ESP Ghostscript, GIMP-Print, and foomatic, which are all installed by default. Many ``low-end'' USB printers do not have image processing (rasterizing) capabilities and require the use of GIMP-print and ESP Ghostscript to process images and PostScript output.
Look for the driver in the Make/Model selection lists displayed by the CUPS graphical interface.
The following printers have been tested and appear to work:
Canon BJC-85 (configured with GIMP-print driver)
HP LaserJet 4 with D-Link USB to parallel converter cable
HP Photosmart P1000
The usbprobe command line utility is provided to display the USB devices connected to the system. (Several levels of detailed information are available; run usbprobe -h for a list of options.) The output looks like this:
Path - Address - Description ---------------------------- 0 - 1 - Hub "UHCI Root Hub" 1 - 2 - Hub "General Purpose USB Hub" 1.2 - 3 - HID "Microsoft Basic Optical Mouse" 1.3 - 4 - Printer "Hewlett-Packard PhotoSmart P1000" 1.4 - 5 - HID "QTRONIX USB Keyboard and Mouse" 1.6 - 6 - Mass Storage "Iomega USB CDRW6402EXT-B" 1.7 - 7 - Mass Storage "Iomega USB Zip 100" 1.5 - 8 - Printer "Canon BJC-85"A single run of usbprobe reports on devices attached to a single USB Host Controller Interface (HCI). Each HCI can be thought of as a separate USB bus. Modern systems typically include up to five or more HCIs. A typical configuration has two physical USB connectors associated with each UHCI or OHCI USB 1.x controller, plus one EHCI controller that talks to all of the physical ports.
To see devices on bus number 3 for example, use this command:
usbprobe -I 3
USB 2.0 devices show up on the bus number associated with the EHCI controller. USB 1.x devices show up on different bus numbers depending on the physical hardware connections.
First provided in Update Pack 2.
This Update Pack includes version 1.1.19 of the Common UNIX Printing System
(CUPS). When installed, both the CUPS and standard (SYSV)
print systems are active. Although both systems use the same command
names, the options and behavior differ somewhat (each print system has a
separate set of commands stored in /usr/lib/lp/cups and
/usr/lib/lp/sysv):
accept cancel disable enable lp lpadmin lpmove lpr lpstat reject
Both command sets are supported. To make it easier to use the commands, you can define the default command set (SYSV or CUPS) to be used when a print command (such as lpstat) is entered on the command line. This can be done in any of three ways:
When the pathname is not supplied, the commands from the default print system are executed. You can use the full pathname to run a command belonging to the non-default print system. In a similar way, you can access the man pages for the two printer systems by supplying the relevant section name in the man(C) command (1 or 8 for CUPS man pages, C or ADM for the SYSV man pages):
| Command | CUPS | SYSV |
|---|---|---|
| accept | 8 | ADM |
| cancel | 1 | C |
| disable | 8 | C |
| enable | 8 | C |
| lp | 1 | C |
| lpadmin | 8 | ADM |
| lpmove | 8 | ADM |
| lpr | 1 | C |
| lpstat | 1 | C |
| reject | 8 | ADM |
The CUPS distribution includes a web-based administrative interface that is configured on port 631 (http://localhost:631).
A list of available printers is generated at the time the CUPS
print daemon (cupsd) is started (when the system enters multiuser
mode). To regenerate the list (such as after connecting
a new USB printer), enter the command:
/etc/init.d/cups restart
Although CUPS supports LPD as both a server and a client, the CUPS LPD server implementation does not support access control (based on the settings in the /etc/hosts.equiv and /etc/hosts.lpd files). If your setup requires the use of the standard LPD, or you wish to use access control, do not install CUPS.
To configure CUPS so that jobs can be sent to a remote LPD printer, add a printer via the CUPS administrative interface and use the following settings:
| Attribute | Setting |
|---|---|
| Device | LPD/LPR Host or Printer |
| Prototype device URI | lpd://hostname/printername |
| Model/driver | Raw |
To configure CUPS so that remote hosts can send jobs to the CUPS printing system on the local host using the LPD protocol, follow the instructions found in the ``Printing to LPD Servers'' section of the Software Administrator's Manual in the online CUPS documentation.
The CUPS lpstat(1) always reports the state of devices as having been last modified on January 1st at 00:00. For example:
Obie accepting requests since Jan 01 00:00This is because the CUPS version of lpstat does not capture this information. The default date is generated so that applications that parse lpstat output will not fail.
There is a known problem with the default printer driver displayed in the CUPS administrative interface for the HP LaserJet Series PCL 6. You should instead select one of these drivers that are reported to work:
First provided in Update Pack 2.
The Update Pack also provides the GIMP-Print (4.2.5) printer drivers for use exclusively with the CUPS printing system. GIMP-Print rasterizes bit images for printers that do not have built-in rasterizers (including many of the more inexpensive USB printers on the market).
First provided in Update Pack 2.
This Update Pack includes the 7.07.1 release of ESP Ghostscript. This is installed by default in conjunction with GIMP-Print to provide better printer support with CUPS.
First provided in Update Pack 2.
h2n(ADM) translates /etc/hosts to DNS files and creates a BIND conf file. This tool can be run once or many times. After converting your host table to DNS format, you can maintain the DNS files manually, or you can maintain the host table and run h2n each time you modify /etc/hosts. (h2n automatically increments the serial number in each DNS file when it creates a new file.)
First provided in Update Pack 2.
Several tunable parameters for the System V Inter Process Communications (IPC) shared memory and semaphore facilities were changed in Update Pack 2. The default settings were raised to values which should accommodate most commercial and open source databases without additional tuning. The maximum values of several parameters were also raised. See the Maintenance Pack 3 Release Notes for more information.
First provided in Update Pack 1, this feature has been moved to MP3.
First provided in Update Pack 1.
The GNU Bourne-Again Shell (bash), Z-Shell (zsh), and Extended C-Shell (tcsh) are included in this Update Pack. Documentation for each of the shells, including man pages and texinfo help, is provided when the shells are installed.
First provided in Update Pack 1.
This Update Pack includes the Info-ZIP package, which provides the zip and unzip compressor-archiver utilities. These commands are compatible with the DOS-based PKZIP tools created by PKWARE, Inc.
Manual pages for these commands are also installed on the system.
First provided in Update Pack 1.
This Update Pack adds support for the Intel® Hyper-Threading (HT) Technology. Hyper-Threading allows two series of instructions to run simultaneously and independently on a single Intel Xeon(TM) or HT-enabled Intel Pentium® 4 processor. With Hyper-Threading Technology enabled, the system treats a physical processor as two ``logical'' processors. Each logical processor is allocated a thread on which to work, as well as a share of execution resources such as cache memories, execution units, and buses.
Hyper-Threading Technology can be employed on a PC that is equipped with the following components:
SCO OpenServer supports Hyper-Threading Technology via the SCO OpenServer Release 5.0.7 Symmetrical Multiprocessing (SMP) product. When SMP is installed, Hyper-Threading is enabled by default.
An SMP license is not required to install SMP on a single-CPU system; simply select to Defer licensing during the installation.
See the hyperthread(HW) manual page for details on using Hyper-Threading Technology.
The Update Pack includes additions and enhancements to the SCO OpenServer online guides and manual pages. Guides and manual pages that are distributed with a number of the new products in this Update Pack are also provided.
The complete set of documentation, including manual pages, can be viewed by any browser using the DocView documentation server. Manual pages can also be viewed using the man(C) command.
Update Pack 3 provides the following documentation:
Update Pack 2 provided the following documentation:
Update Pack 1 provided the following documentation:
The DocView search system, based on the htdig search engine, requires that a search index be generated. Because indexing the SCO OpenServer online Documentation Library can take awhile, the index is not re-generated during the update installation.
To generate the search index, run the following
command:
/usr/lib/docview/conf/rundig
For more information, see ``Generating the search index'', which is accessible from the SCO OpenServer online Documentation Library.
SCO OpenServer Release 5.0.7 Update Pack 3 includes the following bug fixes:
The following notes and limitations apply to the SCO OpenServer Release 5.0.7 Update Pack 3: