SCO OpenServer Release 6.0.0
Maintenance Pack 3
Release and Installation Notes

October 2007

SCO OpenServer™ Release 6.0.0 Maintenance Pack 3 (MP3) contains important enhancements and fixes for your SCO OpenServer Release 6.0.0 system and should be applied at your next maintenance period. Note that removal of MP3 is not supported.

These Release and Installation Notes contain critical information that you need to know before and after installing MP3. Please read them entirely, and also check the SCO OpenServer Release 6.0.0 Late News web site, before beginning to install MP3. Late News can be found at: .

Also periodically check (the OpenServer 6 Supplements Web Site) for additional updated drivers and software supplements. In particular, these OpenServer 6.0.0 supplements are provided on the web site and are not included in maintenance packs:

: Dialogic 5.1a
: KDE 3.5.6 i18n Language Support*
: MergePRO 6.3.0f
: Online Data Manager (ODM)**
: Open Sound System Supplement 4.0.1
: Russian Language Support 6.0.0 for MP3
: SCO Office Server 4.2.0

* KDE 3.5.6 English is included in OpenServer 6.0.0 MP3, CD #2. Due to its size KDE 3.5.6 i18n is not included in MP3 but it is available on SCO's public web site.

** ODM was previously provided on the OpenServer 6.0.0 MP2 CD. It is now provided on the public web site. Note that OpenServer 6.0.0 MP3 provides ODM updates to this web-posted ODM product. See the section below for further details.

Contents of this Document

Before installing the Maintenance Pack, please read the following notes carefully:

Superseded OpenServer 6.0.0 Supplements
This Maintenance Pack can only be installed on SCO OpenServer Release 6.0.0 systems. It supersedes and renders obsolete the following Release 6.0.0 supplements:

Maintenance Pack 1 (RS600A)

Maintenance Pack 2 (RS600B)

OSS701A, the OpenServer 6.0.0 Account Manager Supplement

OSS702B, the OpenServer 6.0.0 pkgadd Supplement

OSS703A, the X Server Upgrade for Maintenance Pack 2.

OSS704A, the Perl and PHP Upgrades for MySQL 5.

OSS705A, the Perl Extensions Upgrade for PostgreSQL 8.

OSS706C, the OpenServer 6 Maintenance Pack 2 Supplement (including US 2007 Daylight Saving Time Update).

OSS707A, the OpenServer 6 Platform Support Update

Flash Player Version 7,0,70,0 (now included on MP3 CD #1)

Java 2 SE 1.4.2.16 (now included on MP3 CD #1)

Java 2 SE 5.0, update 9b (now included on MP3 CD #2)

Mozilla 1.7.13Ba (this version is now included on MP3 CD #1)

MPlayer 1.0 (now included on MP3 CD #2)

OpenServer 6.0.0 MP2 USB Supplement

Western Australia DST Timezone Patch (for Java 1.4.2_13b and Java 1.5.0.09)

NOTE #1: If OSS703, OSS704, or OSS705 are installed, either remove them prior to installing OpenServer 6.0.0 MP3 or, during the OpenServer 6.0.0 MP3 installation, when prompted whether to rollback the patches or cancel the component or task, select "Rollback patches". Depending on which patches you have installed, you may be prompted more than once. These patches and the components they modified will then be replaced by updated X, Perl, and PHP components.

NOTE #2: If you installed OSS707A, the OpenServer 6 Platform Support Update, then after installing OpenServer 6.0.0 MP3 please download and install the latest version of OSS707 (version b or later).
Back Up Your System
Perform a full backup of your system and verify the integrity of the backup before you install the Maintenance Pack. It is always important to have a full system backup available before beginning any system update procedure.

OpenServer 6.0.0 MP3 Version Information

Maintenance Pack 3 (MP3) contains updates to base system components (installed with Release Supplement RS600C), as well as separately installable optional components:

SCO OpenServer Release 6.0.0
Software Components and Packages	FCS/MP1 Version	MP2 Version	MP3 Version
MP3 CD #1 (Required custom Components)
SCO OpenServer 600 Release Supplement	RS600A	RS600B	RS600C
Supplemental Graphics, Web and X11 Libraries
Supplemental Graphics, Web and X11 Libraries*	2.0.0	2.1.0	3.0.0
X.org X11R7.2.0 Runtime	6.8.2	6.9.0	7.2.0
X.org X11R7.2.0 Core Fonts	6.8.2	6.9.0	7.2.0
SCO UNIX Perl Interpreter	5.8.6	5.8.7	5.8.8
X-Window System Version 11
X.org X11R7.2.0 Server	6.8.2	6.9.0	7.2.0
X.org X11R7.2.0 Clients	6.8.2	6.9.0	7.2.0
Apache Web Server
Apache Web Server	1.3.33	1.3.34	1.3.37
Secure Sockets Layer (SSL) Support for Apache	2.8.23	2.8.25	n/a
Perl Support for Apache (modperl)	n/a	1.29.2	1.30.0
PHP Hypertext Processor*	4.3.11	4.4.2	5.2.3
ASP Support for Apache/Perl	n/a	2.59.1	2.59.3
AxKit XML Toolkit for Apache/perl	n/a	1.62.1	1.62.3
Secure Shell	OpenSSH_4.0p1	OpenSSH_4.2p1	OpenSSH_4.6p1
VIM - Vi IMproved	6.3	6.4.0	7.1.068
Mozilla Web Browser	1.7.10	1.7.12	1.7.13Ba
OpenServer 6.0.0 Flash Player	n/a	n/a	7,0,70,0
Java 2 Standard Edition 1.4.2
Java 2 Standard Edition (J2SE)	1.4.2_08	1.4.2_10	1.4.2_16
(URW)++ Free X11 Fonts	n/a	2.0	2.0
SCOx language support
SCOx web services demos in 5 languages	1.1.0	1.1.0	1.1.1
gSOAP C and C++ SOAP Web Services	2.2.3	2.2.3	2.2.3
Portable Document Format (PDF) Viewer	3.0.0	3.01pl2	3.0.2
Heimdal Kerberos 5 Implementation	0.6.2	0.6.5	0.6.5
Samba File and Print Server	3.0.13	3.0.20	3.0.20
ESP Ghostscript	7.7.1	8.15.1	8.15.1
Extended Shells	1.3	1.4.0	1.5.0
GNU Bourne Again Shell (bash)	3.0.14	3.1.1	3.2
Z Shell (zsh)	4.2.5	4.2.6	4.3.4
Extended C-Shell (tcsh)	5.13.0	5.14.0	6.14.0
Korn Shell (ksh)	n/a	n/a	93s
Lynx Web Browser	2.8.5dev.8	2.8.5rel5	2.8.5rel5
Qt - Graphical User Interface Library	n/a	n/a	3.3.8
gmp	n/a	n/a	4.2.1
MP3 CD #1 (pkgadd Components)
aacraid - Adaptec AACRAID Family PCI SCSI IHV HBA	8.0.2	n/a	8.0.3
adp94xx - Adaptec SAS HostRaid HBA	n/a	n/a	1.4
ahci - AHCI HBA Driver	1.0	1.1	1.2
ide - Generic IDE/ATAPI Driver	7.1.4a	7.1.4c	7.1.4g
mega - LSI Logic MegaRAID HBA	8.0.3	n/a	8.0.3b
megasas - LSI Logic MegaRAID SAS HBA	n/a	n/a	1.1
mpt - LSI Logic MPT IHV HBA	8.0.2	8.0.2	8.1.0
nd - Network Drivers	n/a	8.0.6b	8.0.6f
MP3 CD #2 (Optional custom Components)
ant - Java based build tool	n/a	1.6.5	1.6.5
Apache Tomcat Servlet Container	4.1.31Pb	4.1.31Na	4.1.31Na
Java 2 Standard Edition 5.0 (J2SE 5.0)	n/a	n/a	1.5.0_09d
KDE	3.3.2	n/a	3.5.6
mod_jk - Apache Tomcat mod_jk Module	n/a	n/a	1.2.25
MPlayer	n/a	n/a	1.0rc1
OSR5 ABI Perl Interpreter (OSR5 ABI)	n/a	n/a	5.8.8
PostgreSQL Database Management System	7.4.7	8.1.2	8.2.3
Squid Proxy Cache	2.5.9	2.5.12	2.6.12

* The Supplemental Graphics libraries and Perl components have many individual libraries and modules. See the for complete lists.

OpenServer 6.0.0 MP3 Release Supplement RS600C
Release Supplement RS600C (see the list above) contains the following components that you must not select individually for installation

SCO OpenServer 600 Release Supplement RS600C:
SCO Online Documentation Utilities and Framework
SCO OpenServer Operating System
SCO OpenServer Operating System German Language Support
SCO OpenServer Operating System French Language Support
SCO UNIX SVR5 Kernel
SCO TCP/IP
SCO TCP/IP Development System
SCO TCP/IP German Language Support
SCO TCP/IP French Language Support
SCO NFS
SCO Network Interface Card Drivers
SCO UNIX Development System
SCO Visual Tcl
SCO Administration Framework Development System
SCO Legacy OSR5 X11R5/Motif Development System
SCO Standard X Clients
SCO NFS Development System
SCO Universal Driver Interface (UDI)
SCO Universal Serial Bus (USB) Support
SCO SendMail
SCO Mail User Agents
Administration Framework
Extended X Clients
SCO PPP from Morning Star
SCO MMDF
VERITAS Online Disk Manager (ODM)

These components contain updates to the versions of the same components originally delivered on the Release 6.0.0 media. The updates for a particular component in RS600C (such as the SCO UNIX Development System or SCO SendMail) will not be installed with RS600C unless the 6.0.0 version of that component is already installed on the system. So, for example, if you plan to install the Development System, you should install it from the Release 6.0.0 media before installing the Maintenance Pack, so that important Development System updates from RS600C are installed. (If you install any component from your original OpenServer 6.0.0 media kit after installing MP3, please reinstall the release supplement (RS600C) so that the update for that component is installed as well.)

The components other than RS600C (e.g.: Perl, Apache, Mozilla, Tomcat, Java, ant, etc.) are complete versions of the software and can be installed whether the version from the Release 6.0.0 media is already installed or not.

Note that removal of Maintenance Pack 3 is not supported. Because MP3 contains important updates to the system, removing it or any of its components may cause unexpected behavior in components that remain installed.
Space Requirements
Before you install the Maintenance Pack, be sure that you have adequate free disk space available for the components you want to install. The amount of space you need depends on what software you have previously installed. For a default installation the following space is needed:
Remember that the above requirements are for the installed software only; free disk space will also be required for temporary space, user data, etc.
As listed in the above showing all Maintenance Pack 3 Software Components, Maintenance Pack 3 CD #1 includes several updated HBA drivers as well as an updated Network Driver (nd) package. We strongly recommend you install these updated driver packages.

The Software Manager does not install these packages automatically during installation of the Maintenance Pack. As described in , you install these driver packages using the pkgadd(ADM) command. A good time to do this is immediately after installing the custom components from CD #1.

Network drivers were delivered in custom format in the original OpenServer 6.0.0 media. In Maintenance Pack 2 and later, network drivers are being delivered in pkgadd format in the nd package. Providing network drivers in pkgadd-format going forward simplifies the maintenance of network drivers and makes it easier to install and maintain third-party drivers on OpenServer 6.0.0 systems. The first time you install the nd package on a system, package installation replaces the previous custom installed files with new pkgadd installed files. This conversion process requires you to perform two additional steps after you install nd for the first time:
1. Install the nd package a second time in order to update configured network drivers in the kernel build tree.
2. Reinstall any third-party network drivers that had been installed prior to installing nd.
If you have previously installed any nd package, version 8.0.6b or later, then it is not necessary to perform these steps.
Due to the PHP4 to PHP5 upgrade, /usr/lib/php/php.ini is significantly different in MP3. Your prior /usr/lib/php/php.ini file is saved as /usr/lib/php/php.ini-old. Any user-configuration changes made to the old version need to be reapplied to the new PHP /usr/lib/php/php.ini version.

PEAR modules for PHP 5 are not included in MP3.
A new Apache /usr/lib/apache/conf/httpd.conf file is included with MP3. This file is installed if Apache was not previously on your system, or if your original httpd.conf had no user modifications. If there were user modifications, then the MP3 install only updates "php4" references to "php5"; your httpd.conf file is otherwise not modified. In this case, the install keeps a copy of your original file called httpd.conf.backup. The MP3 apache installation always includes /usr/lib/apache/conf/httpd.conf.default so you can see what other new configuration changes are available.
PostgreSQL 8.2.3 is included on the Maintenance Pack CD #2. This release of the PostgreSQL Database Server includes many performance and security enhancements. Systems running a prior release of PostgreSQL are encouraged to upgrade in order to take advantage of these features.

However, to provide these features, PostgreSQL 8.2.3 includes a change in internal database format and is a major upgrade from PostgreSQL 7.x and PostgreSQL 8.1.2. For this reason, you must perform a dump and subsequent restore of all PostgreSQL 7.x/8.1.2 databases that you want to preserve across the upgrade. Detailed instructions on this process are provided below.

To preserve data from a PostgreSQL 7.x or PostgreSQL 8.1.2 database and restore the data into a PostgreSQL 8.2.3 database on OpenServer 6, follow this procedure.
1. On the system running PostgreSQL 7.x/8.1.2, log in as the PostgreSQL super-user:
2. Perform a dump of the databases you wish to preserve using either pg_dumpall(1) or pg_dump(1). Backing up all databases using pg_dumpall is the recommended procedure.
  
  For example, to preserve all databases in a cluster, you could enter the shell command:
  To preserve only the database /exampledb/, you could enter the shell command:
3. Move the existing default data directory to your PostgreSQL backups directory:
  or
4. Exit the PostgreSQL super-user account
5. Install PostgreSQL from CD #2 following the instructions in , below.
6. Configure and start the 8.2.3 PostgreSQL server:
7. Log in as the PostgreSQL super-user:
8. Restore the preserved databases from any previous dumps, as in this example for the database we backed up in Step 2:
Detailed documentation on backing up and restoring PostgreSQL databases is available both in the online documentation:

And, online at the PostgreSQL web site:
Tomcat Upgrade Notes
Installing the Tomcat upgrade available on Maintenance Pack 3 CD #2 will remove any previously installed third-party web applications residing under the /usr/lib/apache/jakarta-tomcat-4.1.31 directory structure. If you wish to preserve web applications that have been installed in a prior Tomcat installation, you will need to re-install these after upgrading Tomcat. If you lack installation media for these applications, you will need to back them up prior to, and restore them after, installing the updated Tomcat.

For example, the SCO Hipcheck agent (HcSCOUA) installs such web applications. If you previously installed the Hipcheck Agent, and then install the MP3 Tomcat upgrade, you will need to reinstall the Hipcheck Agent.
OpenLDAP Upgrade Notes
Upgrading OpenLDAP from version 2.2.24 or 2.2.30 to version 2.3.27 will result in any existing OpenLDAP database data no longer being accessible. To make existing data accessible, the database must be backed up before the upgrade and then restored following the upgrade.

Use the following procedure to backup an existing OpenLDAP database:
1. Log in as root.
2. Stop the slapd daemon, if running, to ensure a consistent backup:
3. Create an ldif backup file:
After the OpenLDAP upgrade, the OpenLDAP database backup can be restored using the following procedure:
1. Log in as root.
2. Restore schema file changes.
  As part of the upgrade process, the OpenLDAP schema files will be overwritten by the new default files, requiring that any changes be manually remade to /etc/openldap/schema/*.schema. The previous versions of these files are saved with the appended character "#":
  New default configuration files are installed in /etc/openldap, but the existing slapd.conf and ldap.conf are not overwritten. However, the upgrade edits slapd.conf to change the back-end modules extension from ".la" to ".so":
3. Create an empty database directory:
4. Restore the ldif backup file:
  A warning will display, although it doesn't affect the restoration of the database:
  /etc/openldap/DB_CONFIG.example can be used to create /usr/lib/openldap/openldap-data/DB_CONFIG to avoid this warning.
Squid Notes
Squid 2.6.STABLE12 requires a new configuration file, /etc/squid/squid.conf. Any previously installed Squid configuration file will be backed up as the file /etc/squid/squid.conf.bak. Configuration changes made to a previously installed Squid will need to be reapplied to the updated Squid configuration file.

The OpenServer 6.0.0 MP3 update returns the Squid configuration files back to /etc/squid and the control script is /etc/init.d/squid.

Selected Components	Disk Space Requirements
Release Supplement RS600C	150 MB
Remaining MP3 Components	145 MB
Additional Optional Components	300 MB
All of the above	595 MB

Follow the procedures in this section to obtain and install the Maintenance Pack.

If you want to install the MP on multiple systems on your TCP/IP network, you can load and install the software on one system and use that system as a Software Installation Server. You can then load all your other systems from the Installation Server. See for more information.

Maintenance Pack 3 install media is distributed on two CD images and can be obtained in three formats:

two Supplement CDs
two Supplement CD ISO images
two tar archives containing Media Image Files (VOL files)

Follow this procedure to install SCO OpenServer Release 6.0.0 MP3 from any of the above media.

Log in as root.
Do one of the following:
1. If you are installing from CDs:
2. If you are installing from CD ISO Images:
  1. Download the CD ISO Images osr600mp3_cd1.iso and osr600mp3_cd2.iso from either the SCO web site or the SCO FTP server:
    In what follows, we have chosen to save these images in the directory /osr600mp3.
  2. Make sure nothing is already mounted on /cd-rom, and enter this command to mount the first CD ISO image:
    Note the backquote characters around the marry command above; the backquote key is usually on the upper left side of the keyboard.
3. If you are installing from Media Image Files:
  1. Download the files osr600mp3_cd1.tar and osr600mp3_cd2.tar from either the SCO web site or using FTP:
    NOTE: The Maintenance Pack consists of two tar archives containing a number of media image files with names of the form VOL.000.000, VOL.000.001, and so forth. Because all maintenance packs use this same filename scheme, you should create a master directory with a unique subdirectory in which to store and process each maintenance pack's media files. The master directory could be /usr/mp, /usr/spool/patches, or whatever suits your system layout. The master hierarchy should be writable by root only. The rest of this document assumes that this directory is /usr/spool/patches/osr600mp3, with subdirectories cd1 and cd2 containing the VOL files for the first and second tar archives, respectively.
  2. Enter these commands to extract the media image files from the tar archives corresponding to the Maintenance Pack CDs:
Start the Software Manager by double-clicking on its icon on the desktop, or by entering the following at the command-line prompt:
From the Software menu, select Install New.
When prompted for the host (machine), select the current host and then click on Continue.
Do one of the following:
1. If you are installing from CDs:
2. If you are installing from CD ISO Images or Media Image Files:
  1. Select Media Images as the Media Device, and then select Continue. (You may need to scroll down in the Media Device selection box in order to see the Media Images option.)
  2. When prompted, enter the absolute pathname for the directory that contains the Maintenance Pack media images:
    - If you are installing from CD ISO Images, enter /cd-rom/opt/archives.
    - If you are installing from Media Image Files, enter /usr/spool/patches/osr600mp3/cd1.
  3. Select OK.
In the Install Selection window, you will see the Maintenance Pack highlighted and/or with an asterisk. By default, all the packages on CD #1 are selected for installation. Select Install.
PLEASE NOTE: It is strongly recommended that you install all packages on CD #1 (default for CD #1). Other packages, contained on CD #2, are optional, and may be installed at a later time. (See )
Depending on your pre-existing software configuration, The Software Manager may display any or all of the following messages in dialog boxes:
- "These components selected for installation will be upgraded", if it finds previous versions of the components that are modified or upgraded by the Maintenance Pack.You should select Continue.
- "These patches cannot be installed because the software they modify is not installed", if it finds the Maintenance Pack contains fixes for software features that are not currently installed on your system. This message is also accompanied by "These patches can be installed" followed by the list of fixes in the Maintenance Pack which will be applied. This dialog box is titled "Install Patch Error", but is a typical and normal part of the install process. You should select Continue if you do not plan to install the absent package(s) at any time in the future, However, if you do plan to install one of these packages, you should stop the MP install process now, install the package in question from the appropriate media, and then restart the Maintenance Pack installation. This ensures that fixes in the MP are applied properly and avoids potential problems.
- "Software Already Installed" and "Part of the software selected for installation is already installed. This operation will only install the software not currently on the system." This is usually because the software in question was installed via a previous Maintenance Pack. You can look at the Details screen to see what software components will be installed, and which already exist on the system. Select Continue.
- "OpenLDAP Databases Changed", followed by a WARNING message to back up existing databases before proceeding. You can respond with OK to proceed, or Cancel to perform the relevant backups first. Typically, select OK to continue the installation.
- Other informational dialog messages or warnings concerning other software components that are about to be upgraded, such as PHP. Please read these dialogs carefully if they appear. The typical response is OK to continue the installation.
When the installation is complete, click on OK. The Software Manager lists the newly added component among the installed software.
NOTE: Just prior to completion, the information dialog "During this installation, the kernel was relinked. You must reboot your system to make this kernel effective." appears. We recommend installing the nd package update as well as desired HBA updates, as outlined below, before rebooting, in order to save time.
Exit the Software Manager by selecting the Host menu, then Exit.
It is prudent to install updated HBA drivers and the updated nd package at this time.

Note: If you have any third-party network drivers installed on the system, and if this is the first time you are installing the pkgadd-format nd package, then you will need to reinstall your third-party drivers after installing the nd package.

To install these packages, do the following as root:
1. Do one of the following:
  
  If you are installing from CDs or CD ISO Images:
  
  If you are installing from CDs, make sure that Supplement CD #1 is still in the drive and that nothing is already mounted on /cd-rom, and enter this command to mount the CD:
  
  # mount -F cdfs -r /cd-rom
  where is the block-device name of the drive in which the CD has been inserted.
  
  Enter:
  
  # pkgadd -d /cd-rom
  This will bring up a list of driver packages you can install, including updated HBA drivers and the nd package.
  
  Select one or more desired driver packages to install as a comma-separated list, using either the listed numbers or names.
  Once all the drivers you select are installed, you will be prompted again for additional selections or to quit. Continue the process until all desired drivers are installed, and then enter q at the prompt.
  
  Individual driver packages may have additional prompting; read the prompts carefully as they are displayed. Typically, select the default responses that are offered.
  
  If you are installing from CDs, unmount the CD with this command:
  # umount /cd-rom
  and remove Supplement CD #1 from the CD drive.
  
  If you are installing from Media Image Files:
  
  Download the desired HBA packages as well as the nd package from the SCO ftp site for HBA and network drivers:
  
  ftp://ftp.sco.com/pub/openserver6/600/drivers
  
  Follow the instructions for installing each package as specified in the cover letter or README file accompanying the package. Respond appropriately to the interactive prompts which appear while running these commands, and postpone any suggested reboots, until all drivers have been installed.
2. you installed the nd package, and if this was a first-time install of that package rather than an upgrade from a previous version, then:
  1. Install the nd package a second time. This is necessary to update configured network drivers in the kernel build tree.
  2. Reinstall any third-party network drivers you had installed prior to installing nd.
after you finish installing the driver packages.
Enter the following commands to reboot the machine:
See the section, to install CD #2 of the Maintenance Pack once the system reboots, or to install additional software from CD #2 not originally chosen for installation (at any later time).

You can install the Maintenance Pack from one SCO OpenServer system onto another across a TCP/IP network.

On the server side, to enable:

In the simplest case, install the Maintenance Pack on the system that you want to use as the software server using one of the installation procedures described under .
Use the Account Manager (scoadmin account) to create a login account named swadmin. When a client system attempts to remotely install software from the server system, this password must be supplied by the client to authenticate the connection. If this account already exists and the password has been forgotten, use the Account Manager to define a new password.

On the client side, to install the Maintenance Pack from the server:

Start the Software Manager and select Install New.
In the Begin Installation window, you are prompted for the source location of the Maintenance Pack. Select From Another Host.
Type in the network node name of the software server and the password for the swadmin account on the software server.
Proceed with the installation as shown in the previous section, beginning with .

For more information, see ``Installing and managing software over the network'' in the online documentation under ``Installation and Licensing''.

To install CD #2 of the Maintenance Pack once the system reboots, or to install additional software from CD #2 not originally chosen for installation (at any later time):

Log in as root.
Do one of the following:
1. If you are installing from CDs:
2. If you are installing from CD ISO Images:
3. If you are installing from Media Image Files:
Start the Software Manager by double-clicking its icon on the desktop, or by entering the following at the command-line prompt:
From the Software menu, select Install New.
When prompted for the host (machine), select the current host and then click on Continue.
Do one of the following:
1. If you are installing from CDs:
2. If you are installing from CD ISO Images or Media Image Files:
  1. Select Media Images as the Media Device, and then select Continue. (You may need to scroll down in the Media Device selection box in order to see the Media Images option.)
  2. When prompted, enter the absolute pathname for the directory that contains the Maintenance Pack media images:
    - If you are installing from CD ISO Images, enter /cd-rom/opt/archives.
    - If you are installing from Media Image Files, enter /usr/spool/patches/osr600mp3/cd2.
  3. Select OK.
In the Install Selection window, select the software you want to install.

When installing components from CD #2 of the Maintenance Pack, an expanded list should automatically appear. Use the Space Bar to select and deselect components from the list. (See the section , above, for a list of the components in CD #2 of the Maintenance Pack.)

To select multiple non-adjacent items to install while using the Software Manager in graphical mode, first select one or more adjacent items by clicking and holding your left mouse button. Next release the mouse button; the items just selected will be highlighted. For each additional item that you want to select or de-select, first move the cursor over that item. Then while holding the key click your left mouse button once.

Once you have selected all the software you want, select Install to begin copying the components to your system.
The Software Manager will display a message if it finds previous versions of the components that are modified or upgraded by the Maintenance Pack. Additionally, some components, such as Tomcat, PostgreSQL, and Squid, may display informational dialogs or warnings. Read all these messages carefully and take appropriate action, if necessary. However, typically you should select Continue or OK to progress with the installation.
For more information on upgrading some of these components, refer to the various Upgrade Notes in .
When the installation is complete, click on OK. The Software Manager lists the newly added component among the installed software.
Exit the Software Manager by selecting the Host menu, then Exit.
Do one of the following:
1. If you are installing from CDs::
2. If you are installing from CD ISO Images::
3. If you are installing from Media Image Files:
While there is no need to reboot the system after installing these packages, if your system is running any libraries or commands that are contained in these packages, then these programs will continue to run with the old versions of these libraries or commands until the system is rebooted.

Once all necessary packages and patches have been installed, it is good practice to reboot the system at the earliest opportunity by invoking the following commands as root:
This will ensure that no programs continue to run with the old libraries or commands.

The following notes and limitations apply to SCO OpenServer Release 6.0.0 Maintenance Pack 3:

OpenServer 6.0.0 MP3 removal is not be supported.
Licensing warning when installing MP3

After installing the RS600C Release Supplement from MP3, the following message is displayed on the console (and recorded in /var/adm/messages and /var/adm/syslog):
```
WARNING:
       The SCO Licensing Policy Manager Daemon (sco_pmd) has terminated
       and been restarted.  This usually indicates a serious system problem
       and you are encouraged to contact your SCO service provider for help.
```
This message is expected when the Release Supplement is installed and can be safely ignored. The Release Supplement contains updates to the Policy Manager Daemon (PMD); the PMD is stopped and restarted by the Supplement to configure the updates.
PHP PEAR modules
PEAR modules for the new PHP 5 package are not included in MP3.
Screen corruption after display of OpenLDAP message
If you are installing MP3 via a terminal emulation then you may see a corrupted screen when the OpenLDAP database message is displayed and you choose to continue the install. If you see a corrupt screen and prompt, simply hit to continue with the installation.
(ID: 534538:1)
Mplayer does not zoom the video when resizing the window
To fix this problem, append this line:
to the $HOME/.mplayer/config configuration file.
(ID: 534416:1)
Samba/Squid /usr/bin/ntlm_auth utility

OpenServer 6.0.0 provides both the Samba package /usr/bin/ntlm_auth and the Squid package /usr/bin/squid_ntlm_auth utilities. If configuring Squid for NTLM authentication, we recommend using the Samba package /usr/bin/ntlm_auth utility.
Xenix applications

If you are running Xenix applications, please see additional limitations described in the section.
Java upgrade may remove mysql.jar link

If you installed MySQL before MP3 CD #1 or the Java 1.5.0 product from OpenServer 6.0.0 MP3 CD #2, then the /usr/java/lib/mysql.jar link may have been overwritten. You can recreate this link via:
In a future release we plan to create this link in a location that does not conflict with a Java upgrade.
Insufficient space error during KDE upgrade
After installing OpenServer 6.0.0 MP3 CD #1 you need to reboot your system before installing other products. This includes the additional software on the OpenServer 6.0.0 MP3 CD #2 such as KDE. Failure to reboot leaves your system in an inconsistent state and can have non-obvious ramifications, such as this insufficient space message.

The workaround is to reboot your system and retry the installation. If this error message appears again, then check that you have sufficient space on your system.
(ID: 534305:1)
KDE upgrade notes
Although upgrading to version 3.5.6 while in your current KDE environment will succeed, doing so may cause anomalous behavior for some icons and warnings when exiting the desktop. You may wish to switch to another environment, such as the xdt3 desktop or a console login shell, when upgrading KDE.

If you have previously installed either or both of the French and German language support packages, you'll likely want to download and install the KDE 3.5.6 i18n Language Support () to get matching localized support for the new KDE.

Upgrading to KDE 3.5.6 renders the older KDE 3.3.2 language support packages obsolete. It also removes symlinks to files in these now-obsolete packages, in turn causing custom verify errors. Therefore, we recommend that you remove the KDE French Language Support Release 3.3.2 and KDE German Language Support Release 3.3.2 packages after KDE 3.5.6 has been installed.

You can use custom interactively to remove these packages. The KDE French Language Support Release 3.3.2 package is found below the SCO OpenServer Release 6.0.0 Graphics French Language Support, which in turn is found below SCO OpenServer Release 6.0.0 French Language Support in the custom display. Similarly, the KDE German Language Support Release 3.3.2 package is found below the SCO OpenServer Release 6.0.0 Graphics German Language Support, which in turn is found below SCO OpenServer Release 6.0.0 German Language Support.

Alternatively, use these commands to remove these packages:
KDE sound error

On systems without a sound driver, KDE may display the following message on start-up:
```
Sound server information message:
        Error while initializing the sound driver.
        device /dev/dsp can't be opened (No such file or directory)
        The sound server will continue, using the null output device.
```
To use sound with KDE, install the Open Sound System Supplement 4.0. You can download this supplement from:
Alternatively, to disable the above message, enter the KDE Control Center, select Sound & Multimedia, then select Sound System, and deselect Enable the sound system.
(ID: 534468:1)
Can't login to KDE with /u95/bin/ksh as login shell
If the UNIX 95 compliant Korn Shell, /u95/bin/ksh, is used as a user's login shell, then that user may not be able to access the KDE desktop environment via scologin. In order to access KDE using the Korn Shell, set the user's login shell to /bin/ksh.
(ID: 534593:1)
X server configuration problems seen occasionally
X server configuration problems have been seen occasionally after using xorgcfg or scoadmin video (which is a front end for xorgcfg). To recover, stop the X server if it is running and generate a new X server configuration file:
This will autodetect your hardware configuration and generate a new configuration file in /xorg.conf.new. When you are ready, back up the old configuration file and copy the new one into place:
Restart the X server.

OpenServer 6.0.0 MP3 includes the following notable enhancements to OpenServer 6:

All the features and bug fixes in OpenServer 6.0.0 MP2. See the and sections below for details. This includes important security related fixes and enhancements as described in these sections below:
- Security fixes in MP1
- Security fixes in MP2
Many new features. See the section below for details.
Many additional bug fixes since MP2. See the section below for details.

OpenServer 6.0.0 MP3 includes all the features previously provided in OpenServer 6.0.0 MP2. Description of these OpenServer 6.0.0 MP2 features follows:










: Online documentation updates



: Security Fixes

ANT Version 1.6.5 is provided as an optional component installable separately from the Maintenance Pack; the Maintenance Pack should be installed prior to installing ANT.

ANT is a Java-based build tool that is an alternative to other build tools such as make, and is designed to overcome difficulties inherent in multi-platform development. It is commonly used in open source Java development.

For more information on ANT, please see the ANT web site at . The documentation for ANT 1.6.5 is available at .

The following enhancements and fixes have been made to improve application compatibility for both OSR5 and SVR5 applications.

An SVR5 ABI version of libprot (/usr/lib/libprot.so) is provided, for use by SVR5 mode applications to be compiled and deployed on OpenServer 6. The OSR5 version of libprot is provided under /osr5/usr/lib/libprot.so, and is for use by OSR5 ABI applications only. OSR5 ABI applications executing on Release 6 can expect that all libprot calls will function as in previous releases.
An updated libiaf that's compatible with libprot and its Identification and Authentication implementation is also provided. This allows SVR5 applications coded to use the SVR5 /usr/lib/libiaf.so routines for I&A to run on OpenServer 6.
Compatibility in the libsocket library is improved by including support for the inet_net_pton, inet_net_ntop, inet_neta, inet_cidr_pton, and inet_cidr_ntop interfaces to libnsl.
A reported OSR5 application failure was found to be caused by TCP/IP code in the kernel that was incompatible with OSR5 style socket addresses passed from OSR5 applications. The socket address structure changed from OSR5 to OSR6, with the 16-bit family field used in the OSR5 socket address replaced by eight-bit length and eight-bit family fields. The problem was fixed by a minor modification to the kernel TCP module.
Changes to libc have been made so that the message catalog routines now understand all "X/Open style" message catalog files produced either by the OpenServer 5 mkcatdefs command or the SVR5 gencat command. It is up to applications where they install and thus locate their respective message catalog files.

Installing the Release Supplement changes the default TERM settings for the console and for new users from at386-ie to ansi. Most applications will not notice this change, except for those that were hard-coded with escape sequences or function key strings instead of using terminfo. Display of special characters, such as accents and umlauts, should be improved by this change.

Applications hard-coded to use an at386-ie or similar console, may want to restore the at386-ie settings originally installed with OpenServer 6. To restore all the at386-ie settings, use the scoadmin international settings manager to change the internal codeset to either the ISO8859-15 or the ISO8859-1 code page (Western Europe, with or without the Euro character). The console TERM settings (including font, keyboard, and mappings) will change automatically to the original OpenServer 6 installation settings.

The IDE driver has been updated to correct problems observed with various IDE controller models. The previous version had trouble working with Intel ICH (I/O Controller Hub) IDE controllers in Enhanced/non-AHCI mode. The updated driver supports Enhanced/non-AHCI mode for all Intel ICH chipsets. Note that SATA (Serial ATA) and AHCI (Advanced Host Controller Interface) modes on ICH chipsets are not supported by this version of the IDE driver. (SATA is currently supported only by the ahci driver; see ).

This driver is provided in pkgadd format, and is added using the following command (with the MP CD in the primary drive):

# mount -F cdfs /dev/cd0 /cd-rom
# pkgadd -d /cd-rom ide

Then, rebuild the operating system and reboot the system:

# /etc/conf/bin/idbuild -B
# init 6

Various issues with international keyboard support have been resolved, and a new set of keyboard mapping tables is included. Use the SCOadmin International Settings Manager (scoadmin internat) to select keyboard tables and codesets.

See the MP2 section for additional information on keyboard related fixes and procedures, including Euro character display issues.

The fixes and features in the Java 2 SE 1.4.2.10 contained in MP2 are contained in the Java 2 SE 1.4.2.16 update in MP3 that completely replaces all previous versions of J2SE 1.4.2.

The Java 2 Standard Edition (J2SE) is upgraded from 1.4.2_08 to 1.4.2_10, and includes these fixes:

The NetworkInterface.getNetworkInterfaces() method was not returning a complete list of network interfaces on an SVR5 system.
The server option -XX:+AggressiveHeap would not take effect on SVR5 systems because the total physical memory was incorrectly calculated.
The RandomAccessFile() constructor mode "d" (data synchronization) was incorrectly passed to the system open() function with a BSD O_DSYNC flag. While generally innocuous, it could result in an SVR5 kernel memory corruption when opening some devices and eventually result in a system panic.
Availability of LARGEFILE support may not have been correctly detected in JVM runtime initialization.
The jre/lib/font.properties file has been revised to use Lucida fonts provided with the J2SE release. The previous font.properties file has been renamed font.properties.BKUP.
Sun Alert ID 102003: Three (3) security vulnerabilities with the use of "reflection" APIs in the Java Runtime Environment may (independently) allow an untrusted applet to elevate its privileges. For example, an applet may grant itself permissions to read and write local files or execute local applications that are accessible to the user running the untrusted applet.

: The ftp and scp commands have been enhanced to handle the transfer of files larger than 2GB in size. Note that the file system on which a large file is created must be a VxFS file system enabled for large files. See .

Multiple core processors have two or more processor cores in each physical package. (The number of internal processors may also be used in the processor name; for example, "dual core" processors.) This architecture continues the trend started with hyperthreading, adding enhanced parallelism and improved performance.

One critical difference between hyperthreading and multiple core processors is that multiple processor cores are detected automatically and utilized if available; hyperthreaded processors, on the other hand, are not utilized unless the administrator specifically requests their use.

The use of multiple processor cores is enabled by default. To disable it, enter the MULTICORE=N boot parameter at the boot loader prompt (or add it to the /stand/boot file). If the use of multiple processor cores is explicitly disabled, then the use of hyperthreading is also disabled. (Having multiple core support enabled has no effect on systems that do not have multiple core processors.)

Note that on some systems (particularly where multi-core processors are included in the system's MPS tables), ACPI=Y must be entered in addition to MULTICORE=N to disable the use of multiple cores.

Hyperthreaded processor support is disabled by default. Support for hyperthreaded processors can be enabled with any of the following boot parameters:

ENABLE_HT=Y
   ENABLE_JT=Y
   HYPERTHREAD=Y

These and all the boot parameters are discussed on the boot(HW) manual page.

Note that if your system supports hyperthreading, then hyperthreading should always be enabled in the system BIOS, regardless of the operating system setting.

Both AMD and Intel multiple core processors are supported. No additional CPU licenses are required to use either multiple processor cores or hyperthreaded processors.

MP2 supplied version 8.0.6b of the network driver nd package.

MP3 updates this package to version 8.0.6f. For more information, see in .

The Online Data Manager (ODM), version 3.2, was provided in Maintenance Pack 2. It is currently available as a download from either the SCO web site or using FTP:

Maintenance Pack 3 includes updates to ODM. These updates are applied during installation of MP3 only if ODM is already installed. Thus, to install ODM with MP3, you must first install MP3; then install ODM; and then reinstall MP3 to get the ODM updates.

ODM provides advanced data redundancy and recovery, including:

concatenation (data is mapped linearly onto one or more subdisks in a plex)
spanning (concatenation using subdisks that reside on more than one VM disk)
mirroring (a technique of using multiple plexes to duplicate the information contained in a volume)
striping (a technique of mapping data so that the data is interleaved among two or more physical disks)
RAID-5 (a method of providing data redundancy through the use of parity--a calculated value that can be used to reconstruct data after a failure)
logs for mirror recovery

ODM includes the Veritas Volume Manager (VxVM) and the Veritas Visual Administrator (VxVA). Once installed and licensed, follow the instructions in the online documentation under to initialize and configure ODM. In particular, be sure to read the software notes and initialization instructions in the document before you begin to use ODM. Also included are the for all the ODM utilities.

ODM requires a separate license, which can be entered using the SCOadmin License Manager (scoadmin license), either before or after installing ODM.

Online documentation updates: The Release Supplement includes many updates to existing manual pages and guides, as well as new documentation for the Online Data Manager (see above), , and updated BIND documentation.

OpenServer 6 now automatically configures devices for all PCI parallel ports installed, including on-board ports and PCI add-on cards. These devices are configured using device names of the form /dev/lp[0..n]. There is no need to run the mkdev parallel command, as required in previous releases.

Use the graphical dcu interface or the command-line resmgr utility to list the enabled parallel ports. Enter /sbin/dcu and check the Hardware Device Configuration. You should see, for example:

Device Name   IRQ IOStart IOEnd MemStart MemEnd DMA
= ===========   === ======= ===== ======== ====== ===
Y Parallel Port 7   3bc     3bf   -        -      -

You could also use the resmgr command:

# resmgr | grep mfpd
3 mfpd 1 5 1 7 3bc 3bf - - - - 1 - - - 1 -

If an existing parallel port is not listed by the dcu and resmgr utilities, reboot and enter the system BIOS to ensure that the port is enabled, and to determine the hardware resource settings (IRQ and I/O addresses) for the undetected port. Then, you need to change the BIOS settings or the dcu/resmgr settings (or both), so that they match.

You can add a parallel port manually within dcu by selecting Software Device Drivers -> Miscellaneous -> mfpd, selecting F5, and entering the appropriate values for the device. Similarly, you can edit the values for an existing driver by selecting the appropriate line in the dcu display and editing the values.

Or use the resmgr command, as in these examples:

# resmgr -a -p "MODNAME UNIT IPL ITYPE IRQ IOADDR BRDBUSTYPE ENTRYTYPE" -v "mfpd 1 5 1 7 3bc 3bf 1 1"
# resmgr -a -p "MODNAME UNIT IPL ITYPE IRQ IOADDR BRDBUSTYPE ENTRYTYPE" -v "mfpd 1 5 1 7 378 37f 1 1"

Then run the following commands to rebuild the operating system and reboot:

# /etc/conf/bin/idconfupdate -f
# /etc/conf/bin/idbuild -B
# init 6

: Various improvements, including pseudo filesystem support and enhanced support for memory-based (memfs) filesystems, have been made to the SCOadmin Filesystem Manager. Please see the section of the section ``Fixes Provided in MP2'', below.

As an alternative to the configure(ADM) command, a graphical System Tuner is provided for changing kernel tunable parameters.

NOTE: The System Tuner modifies kernel parameters - not to be confused with networking parameters (which are modified using the inconfig(ADMN) utility). For more information, including a list of kernel parameters, please see in the online documentation.

To start the graphical System Tuner, enter scoadmin hardware and select Tune Parameters from the display or the Kernel menu. Note that you must start the System Tuner from a graphical desktop, or have your DISPLAY environment variable set to display on a graphical desktop in order to access the System Tuner, which is a graphical display only application. (On a character display, or when the DISPLAY environment variable is not set, the OpenServer classic character based configure(ADM) tool is launched instead.)

To view and change a parameter:

Kernel parameters are divided into categories you can view by clicking on the category button at the top of the window. To see a description of any parameter in the current category, click on the parameter. A description appears in the text box in the window. If the tunable parameter you want to modify is not shown in the current set of parameters, click on the category button and select the appropriate category.
Once the tunable parameter you want to change is displayed, click in the text box next to the parameter name.
To change the value of the tunable parameter, either enter the new value or move the slider bar near the bottom of the window until the desired value is displayed. If the auto check box appears for a parameter, you can select it to have the system select the parameter value automatically.

Use these buttons to control your selections:

Reset	resets values for all parameters changed since the last save
Reset to Factory	resets values to those that were set when the system was installed
Cancel	discards the changes you have made
OK	saves your settings (and proceeds to the next step)

If you changed any parameter values, you are prompted to rebuild the kernel to incorporate the new tunable values: choose Yes to rebuild it now or No to rebuild it the next time you reboot. If you rebuild the kernel, any errors encountered are recorded in the /tmp/kernel_status file.
You are prompted to reboot now. If you select Yes, the system is rebooted immediately using the new kernel parameter values. If you select No, you continue with the old tunable parameter values in effect until the next reboot.

The ahci driver has been updated to support Serial ATA (SATA) tape devices. The AHCI v1.0 Specification is fully supported with the exception of port multipliers and power management. All AHCI v1.0 compliant SATA controllers should work with this driver. Controllers based on the Intel ICH6M, ICH6R, ICH7M and ICH7R are known to work. This driver is provided in pkgadd format, and is added using the following command (with the MP CD in the primary drive):

# mount -F cdfs /dev/cd0 /cd-rom
# pkgadd -d /cd-rom ahci

Then, rebuild the operating system and reboot the system:

# /etc/conf/bin/idbuild -B
# init 6

: The mkdev apc command has been updated to recognize that OSR6 serial ports are capable of the signaling required for the APC UPS daemon to operate.

: The USB Printing subsystem has been updated to correct various problems, including unintelligible output observed at the end of many print jobs.

MP3 updates the X.org Windows System version 6.9.0 released in MP2 with version 7.2.0.

The X.Org X server has been updated from Release 6.8.2 to Release 6.9.0. This new release contains: updated support for many drivers, including ATI Radeon (RN50/ES1000); several new or enhanced protocol extensions; and, a new acceleration architecture for improved graphics performance. For full details on this release please see EF="REF=""> .

OpenServer 6.0.0 MP3 provides the following new features:

: OpenServer 6.0.0 MP3 adds an Accelerated Graphics Port (AGP) driver for faster access to the graphics controller. It uses a Graphics Address Remapping Table (GART) to map discontiguous host memory into a physically contiguous view for DMA transfer to video memory. It is primarily used for running the X11 server on the Intel i81x and AMD 7x1 class of controllers.

Apache has been upgraded to version 1.3.37, and includes both Perl and PHP support. With this release of SCO OpenServer, PHP has been significantly updated from version 4.3.11 to version 5.2.3.

See also in .

: Timezone rules were updated to comply with changes to United States Daylight Savings Time beginning in 2007.

The Extended Shells package has been updated to provide modern versions of the shells originally provided, as well as to add the latest version of the Korn Shell. The following shells have been upgraded or added:

The Z Shell (zsh) has been upgraded from 4.2.6 to 4.3.4
The GNU Bourne Again Shell (bash) has been upgraded from 3.1 to 3.2
The Korn Shell (ksh98) version ksh98s has been added

OpenServer 6.0.0 MP3 provides a Flash Player plugin for Mozilla and Firefox. This plugin was previously provided as a post OpenServer 6.0.0 MP2 supplement on the SCO public FTP site.

Please note:

If you install Mozilla after installing the OpenServer 6.0.0 Flash Player product then remove and reinstall the OpenServer 6.0.0 Flash Player product. This is needed to create the Mozilla links for the Flash Player.
The Flash plugin uses the OSS sound APIs. To enable sound support, install the 4Front oss package which is available from .

GMP 4.2.1 is the initial release of GNU MP for OpenServer 6. GNU MP is a free library for arbitrary precision arithmetic.

Additional information on GNU MP can be found at .

This release of SCO OpenServer contains a new release of the Supplemental Graphics, Web and X11 Libraries (GWXLIBS) set of packages. Aside from many of the individual libraries being updated, there has been a significant change in the way these libraries are packaged. Each library is now its own component, which allows for finer grained dependencies for user packages that use these libraries, as well as making future updates significantly smaller and easier. The build procedure has also been significantly simplified for those who want to rebuild all or part of the package.

The following libraries have been updated:

All X11 libraries upgraded from 6.9.2 to 7.2.0
GNU gettext upgraded from 0.14.5 to 0.16.1
JASper JPEG-2000 upgraded from 1.701.0 to 1.900.1
TIFF upgraded from 3.7.4 to 3.8.2
libpng upgraded from 1.2.8 to 1.2.18
libmng upgraded from 1.0.9 to 1.0.10
FreeType 2 upgraded from 2.1.10 to 2.3.5
libgd2 upgraded from 2.0.33 to 2.0.35
libgif upgraded from 4.1.0 to 4.1.4
NetPBM upgraded from 10.26.14 to 10.34
GTK 2 upgraded from 2.8.9 to 2.10.14
Pango upgraded from 1.10.2 to 1.17.3
Cairo upgraded from 1.0.2 to 1.4.10
GNU readline upgraded from 5.1 to 5.2
BerkeleyDB upgraded from 4.3.28 to 4.6.18
Expat upgraded from 1.95.8 to 2.0.1
libxml2 upgraded from 2.6.22 to 2.6.29
libxslt upgraded from 1.1.15 to 1.1.21
XMLSEC 1 upgraded from 1.2.9 to 1.2.10
OpenSSL 0.9.8e added
OpenSSL 0.9.7 upgraded from 0.9.7i to 0.9.7m
OpenSSL 0.9.6m has been deprecated and no longer provided
OpenLDAP upgraded from 2.2.30 to 2.3.37
Cyrus SASL upgraded from 2.1.20 to 2.1.22
MM upgraded from 1.4.0 to 1.4.2
PCRE upgraded from 6.4 to 7.2
LCMS upgraded from 1.15 to 1.16
libIDL upgraded from 0.8.6 to 0.8.8
cURL upgraded from 7.15.1 to 7.16.4
Sablotron upgraded from 1.0.2 to 1.0.3
ICU upgraded from 3.4 to 3.6
FontConfig upgraded from 2.2.2 to 2.4.2
trio upgraded from 1.10 to 1.12
libart LGPL upgraded from 2.3.17 to 2.3.19
GNOME Options Library (libpopt) upgraded from 1.7 to 1.10.4
GNOME Structured File library (libgsf) upgraded from 1.13.3 to 1.14.5
GNOME CSS library (libcroco) upgraded from 0.6.0 to 0.6.1
librsvg upgraded from 2.13.3 to 2.18.0
libexif upgraded from 0.6.12 to 0.6.16
GnuPG upgraded from 1.4.0 to 1.4.7
libgcrypt upgraded from 1.2.2 to 1.2.4
libgpg-error upgraded from 1.0.0 to 1.5
Tcl 8.4 upgraded from 8.4.10 to 8.4.15
Tk 8.4 upgraded from 8.4.10 to 8.4.14

For more details please see .

OpenServer 6.0.0 can have both J2SE 1.4.2 and J2SE 5.0 installed and functional at the same time. J2SE 1.4.2 is used specifically by various OpenServer tools and by default is updated to version 1.4.2_16 when you install OpenServer 6.0.0 MP3 CD #1.

The Java 2 Standard Edition (J2SE) is upgraded from 1.4.2_10 (in MP2) to 1.4.2_16 (in MP3), and includes these fixes:

A fix for Sun Alert #102934: A buffer overflow vulnerability in the image parsing code in the Java Runtime Environment may allow an untrusted applet or application to elevate its privileges. For example, an applet may grant itself permissions to read and write local files or execute local applications that are accessible to the user running the untrusted applet. A second vulnerability may allow an untrusted applet or application to causes the Java Virtual Machine to hang.
A fix for numeric keypad data entry with the keyboard Num Lock active.
A JVM abort when the mouse wheel is used on a scrolled List widget has been resolved.
The latest fixes from Sun including DST timezone changes.
A problem with embedded Java JVM initialization within a thread application has been corrected.
Additional Root CA Certificates.
A fix for Sun Alert #102686: The JRE and Java Secure Socket Extension (JSSE) may verify incorrect RSA PKCS #1 v1.5 signatures if the RSA public key exponent is 3. This may allow applets or applications that are signed by forged signing certificates and web sites with forged web server certificates to be verified as valid.
Java option -XX:+UseAltSigs was not honered in previous releases. The option functions as Sun intended in 1.4.2_12.
Fixes in java.nio.MappedByteBuffer support. Behavior difference and availability of APIs fsync(), fdatasync() and madvise() between Solaris and UnixWare (SVR5) have been resolved.
Removal of the javasoap package containing the Apache Axis jar file from the j2se142 component. Jar file(s) required by Apache/Tomcat have been incorporated into the Apache/Tomcat updates.
The latest bug and security fixes from Sun.

After installing MP3 both the symbolic links /usr/java and /usr/java2 will point to the J2SE 1.4.2 installation.

For more information please see the "Java 2 Standard Edition, v 1.4.2_16 for SCO UNIX Operating Systems" (ReleaseNotes.html) in the info/java/J2SE_142 directory of MP3 CD #1.

By default, OpenServer 6.0.0 provides Java 2 Standard Edition (J2SE) 1.4.2. That version of Java is used by various OpenServer tools and by default is updated to version 1.4.2_16 when you install OpenServer 6.0.0 MP3.

OpenServer 6.0.0 MP3 CD #2 offers you the option of additionally installing and using Java 2 Standard Edition (J2SE) 5.0, update 09d (1.5.0Id). This version provides:

: J2SE 5.0_09d Runtime Environment (JRE)
: J2SE 5.0_09d Java Plugin for Mozilla
: J2SE 5.0_09d Software Development Kit (SDK)
: Java Communications API, vers. 2.0
: Apache Axis SOAP Web Services 1.2 and Apache Xerces-J XML Parser 1.4.4

J2SE 5.0, update 09d, contains the following fixes to the the J2SE 5.0's update 06 previously released on the SCO Support web site.

A packaging fix to make the javap executable.
A fix to avoid a bug on SCO platforms in the parallel garbage collection routines encountered when running JBoss on "server class" systems. This update is a minimum requirement for the SCO Me Inc. Mobility Server on OpenServer 6.0.0.
Daylight Savings Time timezone changes that go into effect in 2007.
Additional Root CA certificates have been added to the cacerts file.
A problem with embedded Java JVM initialization within a threaded application has been corrected.
A fix for Sun Alert #102760: A buffer overflow vulnerability in processing GIF images in the Java Runtime Environment may allow an untrusted applet to elevate its privileges.
A fix for Sun Alert #102732: Two vulnerabilities in the Java Runtime Environment may allow an untrusted applet to access data in other applets.
A fix for Sun Alert #102731: Two vulnerabilities related to serialization in the Java Runtime Environment may independently allow an untrusted applet or application to elevate its privileges.
A fix for Sun Alert #102729: Two buffer overflow vulnerabilities in the JRE may independently allow an untrusted applet to elevate its privileges. For example, an applet may grant itself permissions to read and write a local file or execute local applications that are accessible to the user running the untrusted applet.
A fix for Sun Alert #102662: A security vulnerability in the JRE Swing library may allow an untrusted applet to access data in other applets.
A fix for Sun Alert #102686: The JRE and Java Secure Socket Extension (JSSE) may verify incorrect RSA PKCS #1 v1.5 signatures if the RSA public key exponent is 3. This may allow applets or applications that are signed by forged signing certificates and web sites with forged web server certificates to be verified as valid.
Removal of the javasoap package containing the Apache Axis jar file froms the j2se142 component.

If you install this version from MP3 CD #2 after installing CD #1, then both /usr/java and /usr/java2 will point to J2SE 5.0 software. If this is not what you want to use as the default Java, you can manually change either or both of these links. These adjustments will need to be repeated following the installation of any J2SE updates.

For more information please see the "Java 2, Standard Edition 5.0, update 9d for SCO UNIX Operating Systems" (ReleaseNotes.html) in the info/java/J2SE_150 directory of MP3 CD #1.

KDE 3.5.6 contains numerous fixes and additional features as well as many security fixes since the previous release of KDE for OpenServer 6.

Changes since the previous release of KDE for OpenServer 6 can be found at:

In addition, KDE 3.5.6 International is provided on the SCO web site (). Additional KDE utilities and the KDE Integrated Development Environment, KDevelop, are provided on the SCO Skunkware download site at . SCO SkunkWare is not officially supported; report any problems to .

Once you have installed KDE 3.5.6 and then the KDE 3.5.6 i18n Language Support, first select the menu item Settings (Control Center) -> Regional & Accessibility -> Country/Region & Language. Next follow the Add Language button -> Other -> your desired language from the menu list, and click on Apply.

OpenServer 6.0.0 Maintenance Pack 3 now allows you to install and run the SCO Mobile Server or SCO HipCheck Mobile Server at the same time that you install and run the SCO HipCheck agent for OpenServer. Thus you can now use the HipCheck agent to monitor and manage the SCO Mobile Server or HipCheck Mobile Server itself.

OpenServer 6.0.0 Maintenance Pack 3 also allows you to install and run the SCO HipCheck agent at the same time that you install third-party Java application server software, such as Tomcat, JBoss, WebLogic, and so on.

: OpenServer 6.0.0 MP3 CD #2 provides a new product, Apache Tomcat mod_jk Module (mod_jk). This replaces the mod_jk2 functionality that was previously part of the Apache Tomcat Servlet Container (tomcat) product. The prior mod_jk2 implementation is deprecated and interferes with other Java web server applications such as the SCO Mobility Server.

MPlayer 1.0rc1 is the initial release of MPlayer for OpenServer 6. MPlayer is a movie and animation player that supports a wide range of codecs and file formats including AVI, MPEG, QuickTime, FLC/FLI, and WMV.

Additional information on MPlayer can be found at .

MP3 updates the Network Driver Package (nd) to version 8.0.6f. A README file for the package is on CD #1 in /info/drivers. This file provides more information about the nd package, including the list of supported network cards, as well as what is new in this package from the previous version.

The nd package is installed using pkgadd. We recommend installing this package following installation of the custom components in CD #1. Please see the instructions at of .

First-time installation of the nd package requires extra steps described in in .

: OpenSSH has been upgraded to version 4.6p1, and several bugs have been fixed. Most notably, OpenSSH now correctly sets the MAIL environment variable to the correct location.

: Perl has been upgraded to version 5.8.8, and most of the extension modules have been updated to later versions. See for more details.

In support of OpenServer 5 customers that may have a third party Perl interface to their OSR 5 application and that interface requires Perl to load an OSR5 ABI shared object, the basic OSR5 perl binaries, scripts and runtime have been provided. This component should only be installed when there is a definitive need for an OSR5 ABI perl.

These binaries install in /osr5/usr/bin/ and make use of the generic Perl modules and programs installed by the regular (SVR5) Perl in /usr/lib/perl5. Customers that require the OSR5 ABI perl should prefix the PATH environment setting with /osr5/bin.

PATH=/osr5/bin:$PATH

before starting "perl". Any complete path invocation of perl - /usr/bin/perl or /bin/perl - should be modified to use /osr5/bin/perl.

At present,the only known requirement for the OSR5 ABI perl is an interface to the Oracle 7.3.x database.

Note that this is not a complete Perl release for the OSR5 ABI, For example the Perl extensions for the OSR5 ABI have not been released but can be released if and when a need arises.

PostgreSQL 8.2.3 is included on the OpenServer 6.0.0 MP3 CD #2. This release of the PostgreSQL Database Server includes many performance and security enhancements. A complete list of changes can be found at .

Systems running a prior release of PostgreSQL are encouraged to upgrade to take advantage of these features. However, due to internal database format changes made by the PostgreSQL developers to provide these features, a dump of any existing databases you wish to preserved must be performed prior to installing this upgrade. Details on this process are provided in these release notes.

: Qt 3.3.8 contains numerous fixes, including several security fixes. A complete list of changes can be found at http://trolltech.com/developer/notes/changes/changes-3.3.8 .

The SCO Admin Account Manager has been enhanced to better facilitate accounts on systems running Samba and NIS.

The SCO Admin Network Configuration Manager is now more robust in its handling of network configuration on systems with multiple NICs.

New for SCO OpenServer 6 are the SCO Admin System Monitor Manager and SCO Admin DNS Manager. For those familiar with SCO UnixWare, these are the same applications found in SCO UnixWare 7 ported to the SCO OpenServer 6 platform.

The SCO Admin System Monitor Manager is a graphical tool that allows choices from a selected set of system performance metrics to be displayed in real-time on a configurable graph. The tool has been improved for OpenServer 6 to provide more robust operation and enhanced usability, however it works only in graphical mode and currently provides no "Help" facility.

The SCO Admin DNS Manager is a graphical tool that enables DNS servers and services to be configured using a convenient interface that helps eliminate the need to run command line utilities and edit DNS configuration files with a text editor. Because the SCO Admin DNS Manager is new for OpenServer 6, there are a few caveats regarding its use that need to be kept in mind:

The SCO Admin DNS Manager is a graphics only tool. It will not execute on a character console in CHARM mode.
While careful attention to detail when using the SCO Admin DNS Manager for most common tasks will produce optimal results, it is important to make backups of your DNS configuration files before starting the manager in case it becomes necessary to restore them due to operation or execution problems with the DNS Manager. The files that should be backed up include /etc/named.conf and all files in the /etc/named.d hierarchy, especially db., db., and any other files beginning with "db".
When entering fully qualified domain names, be sure to include the final ',' (dot), e.g. "beta.mydomain.com."
Care must be taken to only add hosts inside already configured zones. When adding a host, specifying a zone that has not been configured can result in corruption of reverse lookup files. Note: if your domain uses the class C address space 192.168.213, the the reverse lookup file would be "db.213.168.192". (No trailing '.')
It is important that you properly specify your zone's network address correctly the first time. Attempting to modify the network address with the SCO Admin DNS Manager, or delete it and reconfigure it with the manager, will often result in configuration file corruption and a non-functional manager.
Configuring a "Caching-only" server can result in problems executing the "host" utility, which is fundamental to several SCO Admin managers and other system utilities. If after using the SCO Admin DNS Manager to configure a "Cacheing-only" server problems such as hung SCO Admin managers are encountered, try deleting the "Cacheing-only" configuration. While it may be possible to delete the "Cacheing-only" configuration with the DNS Manager, it may be necessary to remove /etc/named.conf and edit the /etc/named.d/db* files manually, or restore previous versions from backup copies. DO NOT simply remove all the files under /etc/named.d!
The SCO Admin DNS Manager may not always properly handle case-sensitivity issues with host names. In particular, adding, modifying, or deleting hostnames or zones with hostnames that differ only in the case of some or all of the letters in their names will generally cause corruption of the DNS configuration files. For best results, make sure all hostnames and zone names are unique without respect to case. E.g., do not have the hostnames "beta" "Beta" or "BETA" in the same domain, nor attempt to configure zones "mydomain.com", "MyDomain.com" (or "MYDOMAIN.com") on the same system. Note: while some applications and environments support case sensitivity, DNS specifications do not recognize case.
There are several problems with importing host data from the /etc/hosts file that can result in extensive corruption of DNS configuration data. At this time, it is best to not use this feature of the SCO Admin DNS manager.
Presently, the manager's "Help" buttons and menu "Help" selections do not work.

: Squid 2.6.STABLE12 contains a fix for a denial of service attack.

OpenServer 6.0.0 MP3 provides updated UDI and USB subsystems. This includes the enhancements provided by the earlier OpenServer 6.0.0 MP2 USB Supplement plus additional bug fixes.

The OpenServer 6.0.0 supplement provided an enhanced USB driver that supports both USB modems and serial adapters. The device driver adds support for USB modems that conform to the CDC/ACM specification. Written to the Uniform Driver Interface (UDI) specification, the new driver includes a number of fixes that improve performance and device support.

Among the USB devices supported by this supplement are:

: All SeaLevel single and multiport devices
: Allied Data Tornado SFM56.0-USB Modems
: BAFO Technologies BF-800 and BF-810 Single port adapters
: Byterunner Technologies USB Communications Adapters.
: Cables Unlimited USB to RS232 Serial Adapter
: Comtrol RocketPortII USB Serial Hubs
: CP-US-03 USB Serial Adapters
: Modems supporting the "Abstract Control Model" Communications Subclass Interface type.
: MultiTech MultiModemUSB Modems
: Serial Adapters that use the FT8U232AM Chipset (**)
: Serial Adapters that use the PL-2303 Chipset (**)
: VScom USB Serial Adapters
: Zoom/Faxmodem 56K USB Modems (*)
(*) Zoom has intermittent start-up failures due to firmware problems.
(**) If a vendor changed the product ID in PL-2303 and FT8U232 then the device may not work with this release.

OpenServer 6.0.0 MP3 also provides these additional bug fixes that were not in the OpenServer 6.0.0 Maintenance Pack 2 USB supplement:

fz534075:1, Recognize Iomega REV changer by not caching INQ across LUNS
fz534090:1, Improve EHCI performance by raising maximum interrupt rate.

Notes on using USB follow.

After installing MP3, once your system is rebooted any supported USB Serial and USB Modem devices connected to the system will be automatically recognized and device nodes for these devices will be created.

To list the serial ports of the USB devices that are recognized by your system run the the command:

: l /dev/usb_ser*

This will return output similar to:

crw-rw-rw-    1 root     root     295,108 Oct 24 10:05 /dev/usb_ser0A
crw-rw-rw-    1 root     root     295,107 Oct 24 10:05 /dev/usb_ser0a
crw-rw-rw-    1 root     root     295,106 Oct 24 10:05 /dev/usb_ser0h
crw-rw-rw-    1 root     root     295,105 Oct 24 10:05 /dev/usb_ser0s

/dev/usb_ser:
total 0
crw-rw-rw-    1 root     root     295,108 Oct 24 10:05 tty.03001-3.A
crw-rw-rw-    1 root     root     295,107 Oct 24 10:05 tty.03001-3.a
crw-rw-rw-    1 root     root     295,106 Oct 24 10:05 tty.03001-3.h
crw-rw-rw-    1 root     root     295,105 Oct 24 10:05 tty.03001-3.s

where

: /dev/usb_ser0A is the modem control device
: /dev/usb_ser0a is the non modem control device
: /dev/usb_ser0h is the Hardware flow control device
: /dev/usr_ser0s is the Software flow control device

and

/dev/usb_ser/tty.03001.3.A
 /dev/usb_ser/tty.03001.3.a
 /dev/usb_ser/tty.03001.3.h
 /dev/usb_ser/tty.03001.3.s

are USB Serial Device names for the serial ports where the first five digit number is the location of the host controller interface (HCI) to which the serial port/modem is connected. It's five digits represent the PCI bus number (two digits), the PCI device number (two digits), and the PCI function number (the final digit). For example:

/dev/usb_ser/tty.03001.3.A

The above device name indicates that the HCI is located at PCI bus number 03, PCI device 00, PCI function 1. Note that this number is completely determined by the hardware vendor's PCI configuration.

The remainder of the device name after the second period is a sequence of from one to six decimal numbers, each of which can be from one to three digits. The final number, which is required, indicates the port number on the device to which the serial port/modem is physically connected. Up to five hubs can be connected between the serial port/modem and the PC USB port, and the ports to which these devices are connected are indicated by the five optional three digit numbers in the device name, separated by periods.

In the example above, the serial port is connected to PC USB Port 3.

A device name like /dev/usb_ser/tty.00072.1.4.2 indicates the following device configuration:

PC USB Port 1 --- | Hub#1 Port 1
   PC USB Port 2     | Hub#1 Port 2
                     | Hub#1 Port 3
                     | Hub#1 Port 4  --- | Hub#2 Port 1
                     ...                 | Hub#2 Port 2  --- USB Serial Port

You can use the Serial Manager to configure USB Serial Port devices. For details on configuring serial ports using the serial manager see

You can use the Modem Manager to configure USB Modem devices. For more details on the modem manager see:

: The VIM editor has been upgraded to the latest available version, 7.2. This version has many new features, including structure completion for C programs and other languages. Many bugs have been fixed and improvements made.

OpenServer 6.0.0 MP3 implements a major update for the Xenix emulator and the underlying kernel services. In general, most known Xenix emulator problems have been addressed. Both Xenix x.out binaries as well as COFF applications linked with the Xenix Services library via the -lx flag should now function correctly.

The kernel now implements Xenix semaphores, Xenix shared memory, and Xenix file and record locking. Additionally, the Xenix emulator xrun has been enhanced to make use of the restored kernel services.

The brkctl(S) system call has now been fully implemented for the Xenix emulator. This mostly affects model large Xenix applications, most of which previously did not run on OSR6.

The ls command has been upgraded to display properly Xenix shared memory and semaphore device nodes.

Limitations

A previously installed Xenix application that uses semaphores may fail immediately after upgrading to MP3 because of a change in the way Xenix semaphores are implemented. Previously, the xrun emulator simulated Xenix semaphores via System V semaphores, using regular files that contained information about the semaphore properties. As noted above, MP3 eliminates that implementation in favor of a direct kernel-level implementation of Xenix semaphores.
If such an application failure is encountered after installing MP3, application functionality can usually be restored by shutting down the application, deleting the old semaphore files, and then restarting the application. In a few cases, it might be necessary to reinstall the application.
This update does not address missing Xenix ioctls (fz530099:2).
This update does not address Xenix applications that fails due to various ancillary environmental issues, such as missing termcap entries, changed VT characteristics, etc.
Xenix shared memory may not work properly when using sdget(S) with the SD_UNLOCK flag in small model data segments (i.e. models small and medium). This behavior is consistent with the original Xenix manual page, which states, "For 286 programs, it is strongly recommended that sdget and other shared memory data function be reserved for large model programs only." (Statement reproduced from SCO document XG-6-21-87-4.0, (c) 1980-1987 Microsoft Corporation, (c) 1983-1987 Santa Cruz Operation, Inc.)

We believe this problem is unlikely to be encountered in practice.
Post-System V Xenix 386 x.out binaries and COFF binaries linked with -lx are virtually indistinguishable when executing on OSR5 because both execute directly on the kernel; neither one is emulated. However, Xenix 386 x.out binaries run under the xrun emulator in OSR6, and as a result, there is a small chance that environmental differences, such as address space layout, might cause application failures.

: SCO OpenServer Release 6 Maintenance pack 3 contains a major upgrade to the X11 windowing system. This has been upgraded from the 6.9.2 series to the 7.2.0 series. This new version has several new driver optimizations, drivers for more video cards, and improvements to older drivers. Changes include the new RandR extension; better OpenGL support; the new EXA accelerated driver architecture; better TrueType font support; and many other improvements.

: Xpdf 3.02 contains support for PDF 1.6 and PDF 1.7 as well as numerous fixes and additional features. A complete list of changes can be found at:

SCO OpenServer Release 6.0.0Maintenance Pack 3Release and Installation Notes

Contents of this Document

Limitations

SCO OpenServer Release 6.0.0
Maintenance Pack 3
Release and Installation Notes