February 2009
SCO OpenServerTM Release 6.0.0 Maintenance Pack 4 (MP4) 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 MP4 is not supported.
These Release and Installation Notes contain critical information that you need to know before and after installing MP4. Please read them entirely, and also check the SCO OpenServer Release 6.0.0 Late News web site, before beginning to install MP4. Late News can be found at: http://www.sco.com/support/docs/openserver. Additional information and release notes for device drivers and some MP4 components (for example, Java, Mozilla® Firefox®, and Mozilla® ThunderbirdTM) are provided on each MP4 CD in the /info directory.
Also periodically check http://www.sco.com/support/update/download/product.php?pfid=12&prid=20 (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:
* 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 MP4 provides ODM updates to this web-posted ODM product. See the Online Data Manager (ODM) section below for further details.
Before installing the Maintenance Pack, please read the following notes carefully:
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:
NOTE: If OSS703, OSS704, or OSS705 are installed, either remove them prior to installing OpenServer 6.0.0 MP4 or, during the OpenServer 6.0.0 MP4 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.
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.
Maintenance Pack 4 (MP4) contains updates to base system components (installed with Release Supplement RS600D, as well as separately installable optional components:
| SCO OpenServer Release 6.0.0 | ||||
| Software Components and Packages | FCS/MP1 Version |
MP2 Version | MP3 Version | MP4 Version |
| MP4 CD #1 (Required custom Components) | ||||
| SCO OpenServer 600 Release Supplement | RS600A | RS600B | RS600C | RS600D |
| Supplemental Graphics, Web and X11 Libraries | ||||
| Supplemental Graphics, Web and X11 Libraries* | 2.0.0 | 2.1.0 | 3.0.0 | 3.0.1 |
| X.org X11R7.2.0 Runtime | 6.8.2 | 6.9.0 | 7.2.0 | 7.2.0 |
| X.org X11R7.2.0 Core Fonts | 6.8.2 | 6.9.0 | 7.2.0 | 7.2.0 |
| SCO UNIX Perl Interpreter | 5.8.6 | 5.8.7 | 5.8.8 | 5.8.8 |
| X-Window System Version 11 | ||||
| X.org X11R7.2.0 Server | 6.8.2 | 6.9.0 | 7.2.0 | 7.2.0 |
| X.org X11R7.2.0 Clients | 6.8.2 | 6.9.0 | 7.2.0 | 7.2.0 |
| PostgreSQL Database Management System | 7.4.7 | 8.1.2 | 8.2.3 | 8.2.9 |
| Apache 1 & 2 Web Servers | ||||
| Apache 1 Web Server | 1.3.33 | 1.3.34 | 1.3.37 | 1.3.37 |
| Apache 2 Web Server | n/a | n/a | n/a | 2.2.6 |
| Secure Sockets Layer (SSL) Support for Apache | 2.8.23 | 2.8.25 | n/a | n/a |
| Perl Support for Apache 1 (modperl1) | n/a | 1.29.2 | 1.30.0 | 1.30.0 |
| Perl Support for Apache 2 (modperl2) | n/a | n/a | n/a | 2.0.3 |
| PHP Hypertext Processor | 4.3.11 | 4.4.2 | 5.2.3 | 5.2.3 |
| ASP Support for Apache/Perl | n/a | 2.59.1 | 2.59.3 | 2.59.3 |
| AxKit XML Toolkit for Apache/perl | n/a | 1.62.1 | 1.62.3 | 1.70.0 |
| Secure Shell | OpenSSH_4.0p1 | OpenSSH_4.2p1 | OpenSSH_4.6p1 | OpenSSH_4.6p1 |
| VIM - Vi IMproved | 6.3 | 6.4.0 | 7.1.068 | 7.1.068 |
| Mozilla Firefox Web Browser | n/a | n/a | n/a | 2.0.0.18 |
| OpenServer 6.0.0 Flash Player | n/a | n/a | 7,0,70,0 | 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 | 1.4.2_19 |
| (URW)++ Free X11 Fonts | n/a | 2.0 | 2.0 | 2.0 |
| SCOx language support | ||||
| SCOx web services demos in 5 languages | 1.1.0 | 1.1.0 | 1.1.1 | 1.1.1 |
| gSOAP C and C++ SOAP Web Services | 2.2.3 | 2.2.3 | 2.2.3 | 2.2.3 |
| Portable Document Format (PDF) Viewer | 3.0.0 | 3.01pl2 | 3.0.2 | 3.0.2 |
| Common UNIX Printing System | 1.1.21 | n/a | n/a | 1.3.9 |
| ESP Ghostscript | 7.7.1 | 8.15.1 | 8.15.1 | 8.62 |
| Heimdal Kerberos 5 Implementation | 0.6.2 | 0.6.5 | 0.6.5 | 1.2 |
| Samba File and Print Server | 3.0.13 | 3.0.20 | 3.0.20 | 3.0.30 |
| Extended Shells | 1.3 | 1.4.0 | 1.5.0 | 1.5.0 |
| GNU Bourne Again Shell (bash) | 3.0.14 | 3.1.1 | 3.2 | 3.2 |
| Z Shell (zsh) | 4.2.5 | 4.2.6 | 4.3.4 | 4.3.4 |
| Extended C-Shell (tcsh) | 5.13.0 | 5.14.0 | 6.14.0 | 6.14.0 |
| Korn Shell (ksh) | n/a | n/a | 93s | 93s |
| Lynx Web Browser | 2.8.5dev.8 | 2.8.5rel5 | 2.8.5rel5 | 2.8.5rel5 |
| Qt - Graphical User Interface Library | n/a | n/a | 3.3.8 | 3.3.8 |
| gmp | n/a | n/a | 4.2.1 | 4.2.1 |
|
MP4 CD #1 (pkgadd Components)
(For HBA drivers only, IHVVERSION shown below VERSION) |
||||
| aacraid - Adaptec AACRAID Family PCI SCSI IHV HBA | 8.0.2 6011 |
n/a | 8.0.3 6011 |
8.0.3 6011 |
| adp94xx - Adaptec SAS HostRaid HBA | n/a | n/a | 1.4 11658 |
1.4 11658 |
| adpu320 - Adaptec Ultra320 Family PCI SCSI IHV HBA | 7.1.3d d3.0 |
n/a | n/a | 8.0.1a d3.0 |
| adst70 - Adaptec Ultra160 Family PCI SCSI IHV HBA | 7.1.3b d3.14 |
n/a | n/a | 7.1.3c d3.14 |
| ahci - AHCI HBA Driver | 1.0 1.1 |
1.1 1.1 |
1.2 1.2 |
1.2 1.2 |
| ide - Generic IDE/ATAPI Driver | 7.1.4a 7.1.4a |
7.1.4c 7.1.4c |
7.1.4g 7.1.4g |
7.1.4h 7.1.4h |
| mega - LSI Logic MegaRAID HBA | 8.0.3 2.0.5 |
n/a | 8.0.3b 2.0.5 |
8.0.3b 2.0.5 |
| megasas - LSI Logic MegaRAID SAS HBA | n/a | n/a | 1.1 00.00.03.05 |
1.1 00.00.03.05 |
| mpt - LSI Logic MPT IHV HBA | 8.0.2 1.03.29 |
8.0.2 1.03.29 |
8.1.0 1.04.14 |
8.1.0 1.04.14 |
| nd - Network Drivers | n/a | 8.0.6b | 8.0.6f | 8.0.6g |
| MP4 CD #2 (Optional custom Components) | ||||
| ant - Java based build tool | n/a | 1.6.5 | 1.6.5 | 1.6.5 |
| Apache Tomcat Servlet Container | 4.1.31Pb | 4.1.31Na | 4.1.31Na | 4.1.31Na |
| Java 2 Standard Edition 5.0 (J2SE 5.0) | n/a | n/a | 1.5.0_09d | 1.5.0_17 |
| KDE | 3.3.2 | n/a | 3.5.6 | 3.5.9 |
| KDE i18n Language Support | n/a | n/a | n/a | 3.5.9 |
| mod_jk - Apache Tomcat mod_jk Module | n/a | n/a | 1.2.25 | 1.2.25 |
| MPlayer | n/a | n/a | 1.0rc1 | 1.0rc1 |
| Squid Proxy Cache | 2.5.9 | 2.5.12 | 2.6.12 | 2.7.3 |
| Mozilla Thunderbird Mail/News | n/a | n/a | n/a | 2.0.0.18 |
* The Supplemental Graphics libraries and Perl components have many individual libraries and modules. See the Appendix for complete lists.
Release Supplement RS600D (see the list above) contains the following components that you must not select individually for installation
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 RS600D (such as the SCO UNIX Development System or SCO SendMail) will not be installed with RS600D 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 RS600D are installed. (If you install any component from your original OpenServer 6.0.0 media kit after installing MP4, please reinstall the release supplement RS600D so that the update for that component is installed as well.)
The components other than RS600D (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 4 is not supported. Because MP4 contains important updates to the system, removing it or any of its components may cause unexpected behavior in the components that remain installed.
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 previously installed. For a default installation the following space is needed:
| Selected Components | Disk Space Requirements |
|---|---|
| Release Supplement RS600D | 225 MB |
| Remaining MP4 CD #1 Components | 325 MB |
| MP4 CD #2 (Additional Optional Components) | 1100 MB |
| All of the above | 1650 MB |
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 table above showing all Maintenance Pack 4 Software Components, Maintenance Pack 4 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 §2: Installing the Maintenance Pack, 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 reinstall nd immediately after installing it for the first time in order to update configured network drivers in the kernel build tree.
If you previously installed any nd package, version 8.0.6b or later, then you can skip this reinstallation step.
Maintenance Pack 4, like MP3, includes PHP5, while Maintenance Pack 2 and earlier included PHP4. Upgrading to Maintenance Pack 4 from OpenServer Maintenance Pack 2 or earlier will introduces significant differences to the PHP configuration file /usr/lib/php/php.ini due to the PHP4 to PHP5 upgrade. In this case, your prior /usr/lib/php/php.ini file will be 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 MP4.
The default Apache 1 configuration file /usr/lib/apache/conf/httpd.conf included in Maintenance Pack 4 matches the version that was first included in Maintenance Pack 3 The default file is installed if Apache 1 was not previously on your system, or if your original httpd.conf had no user modifications. If there were user modifications, then the MP4 installation only updates "php4" references, if there are any, 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 MP4 Apache 1 installation always includes /usr/lib/apache/conf/httpd.conf.default so you can see what other default configuration changes have been made since Maintenance Pack 2.
As described in the Cups feature section below, OpenServer 6.0.0 Maintenance Pack 4 provides significant enhancements to the Common UNIX Printing System (CUPS) system. Previous releases of Cups for OpenServer 6 carried forward any existing Cups /etc/cups/cupsd.conf configuration file. However, due to the many Cups changes this release introduces, a new /etc/cups/cupsd.conf configuration file is provided. Your existing cupsd.conf file is backed up as /etc/cups/cupsd.conf.bak.
If you made changes to your previous Cups configuration, after installing MP4 you will need to re-apply those changes to the newly installed /etc/cups/cupsd.conf file.
PostgreSQL 8.2.9 is included on the Maintenance Pack CD #1. 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.9 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. (If you are upgrading from another version of Postgres 8.2.*, such as Postgres 8.2.3, then you do not need to back up/restore your existing Postgres databases.) 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.9 database on OpenServer 6, follow this procedure.
On the system running PostgreSQL 7.x/8.1.2, log in as the PostgreSQL super-user:
# su - postgres
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:
# pg_dumpall > exampledb.out
To preserve only the database /exampledb/, you could enter the shell command:
# pg_dump -F c -f exampledb.out exampledb
Move the existing default data directory to your PostgreSQL backups directory:
# cd /usr/postgres # mv data backups/data-7.4.7
or
# cd /usr/postgres # mv data backups/data-8.1.2
Exit the PostgreSQL super-user account
Install PostgreSQL from CD #2 following the instructions in §2.3: Adding Software after Installing the Maintenance Pack, below.
Configure and start the 8.2.9 PostgreSQL server:
# mkdev pgsql
Log in as the PostgreSQL super-user:
# su - postgres
Restore the preserved databases from any previous dumps, as in this example for the database we backed up in Step 2:
# psql -f exampledb.out postgres
Detailed documentation on backing up and restoring PostgreSQL databases is available both in the online documentation:
``Migration Between Releases''
``Backup and Restore''
And, online at the PostgreSQL web site:
http://www.postgresql.org/docs/8.2/static/migration.html
http://www.postgresql.org/docs/8.2/static/backup.html
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:
# kill `ps -e | grep slapd | awk '{print $1}'`
# slapcat -l /usr/lib/openldap/openldap-data/openldap.ldif
After the OpenLDAP upgrade, the OpenLDAP database backup can be restored using the following procedure:
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 "#":
# ls -1 /etc/openldap/schema README corba.schema corba.schema# ...
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":
# ls -1 /etc/openldap DB_CONFIG.example ldap.conf ldap.conf.default schema slapd.conf slapd.conf.default
# cd /usr/lib/openldap # mv openldap-data openldap-data.bak # mkdir openldap-data # chmod 700 openldap-data
# slapadd -l /usr/lib/openldap/openldap-data.bak/openldap.ldif
A warning will display, although it doesn't affect the restoration of the database:
bdb_db_open: Warning - No DB_CONFIG file found in directory /usr/lib/openldap/openldap-data: (2) Expect poor performance for suffix dc=my-domain,dc=com.
/etc/openldap/DB_CONFIG.example can be used to create /usr/lib/openldap/openldap-data/DB_CONFIG to avoid this warning.
Squid 2.7.STABLE3 requires a new configuration file, /etc/squid/squid.conf. Any previously modified Squid configuration file will be backed up as the file /etc/squid/squid.conf.bak and the changes (against the pre-MP4 /etc/squid/squid.conf.default file) saved as the file /etc/squid/squid.conf.dif. Configuration changes made to a previously installed Squid will need to be reapplied to the updated Squid configuration file.
The OpenServer 6.0.0 MP4 update returns the Squid configuration files back to /etc/squid and the control script is /etc/init.d/squid.
Installing the Tomcat upgrade available on Maintenance Pack 4 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 MP4 Tomcat upgrade, you will need to reinstall the HipCheck Agent.
There are several bind8 to bind9 migration issues that you may encounter as part of this upgrade. For example, several /etc/named.conf options have changed, logging categories are enhanced, handling of configuration error is different, and so on. One can run the named-checkconf command to ensure that the configuration file does not have any syntactic errors. Details are available at http://uw714doc.sco.com/en/NET_tcpip/dnsN.main.html#dns.bind8-9notes or at the ISC website http://www.isc.org/software/bind/documentation.
In addition, while it is recommended to use rndc to control the name daemon, ndc is also provided as a compatibility front-end to rndc. To use ndc, it is first necessary to run the following command to edit the pathname of various configuration files:
# cd /etc # cp -p ndc ndc.old # sed 's/\/etc\/inet/\/etc/g' < ndc.old > ndc
In Maintenance Pack 3 and earlier, a few GNU Utilities were shipped as part of GWXLIBS, a subparcel of the Maintenance Pack.
However, starting with Maintenance Pack 4, these GNU Utilities will be shipped as an independent package and will no longer be part of the Maintenance Pack.
Customers who install Maintenance Pack 4 will find that they are missing the GNU Utilities until they install the GNU Utilities package. This package can be downloaded from the following URL shortly after the release of MP4:
If P533446A, the OpenServer 6.0.0 CUPS pdftops security update, is installed on your system then we recommend that you remove it prior to installing OpenServer 6.0.0 MP4.
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 ``Installing the Maintenance Pack from the Network'' for more information.
Maintenance Pack 4 install media is distributed on two CD images and can be obtained in three formats:
Follow this procedure to install SCO OpenServer Release 6.0.0 MP4 from any of the above media.
Do one of the following:
If you are installing from CDs:
Insert CD #1 into the primary CD drive.
If you are installing from CD ISO Images:
In what follows, we have chosen to save these images in the directory /osr600mp4.
Make sure nothing is already mounted on /cd-rom, and enter this command to mount the first CD ISO image:
# mount -F cdfs -r `marry -a /osr600mp4/osr600mp4_cd1.iso` /cd-rom
Note the backquote characters around the marry command above; the backquote key is usually on the upper left side of the keyboard.
If you are installing from Media Image Files:
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/osr600mp4, with subdirectories cd1 and cd2 containing the VOL files for the first and second tar archives, respectively.
# mkdir -p /usr/spool/patches/osr600mp4/cd1 # mkdir -p /usr/spool/patches/osr600mp4/cd2 # cd /usr/spool/patches/osr600mp4/cd1 # tar xvf osr600mp4_cd1.tar # cd ../cd2 # tar xvf osr600mp4_cd2.tar
# scoadmin software
From the Software menu, select Install New.
If you are installing from CDs:
Select the appropriate CD-ROM drive as the Media Device and then select Continue.
If you are installing from CD ISO Images or Media Image Files:
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/osr600mp4/cd1.
Select OK.
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 §2.3: Adding Software after Installing the Maintenance Pack)
"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 and the post MP3 Apache 2 web release. 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.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:
See whether you already have a version of the nd package installed by running:
# pkginfo ndIf you see this output:
system nd Network Driversthen you are upgrading from an earlier version of nd and no special steps are required below. Otherwise, this is a first-time installation of the nd package, and you should follow the instructions at step 4 below after you finish installing the driver packages.
Find out which HBAs are present on your system:
# /sbin/sdiconfig
Do one of the following:
If you are installing from Media Image Files:
Download the MP4 device drivers from http://www.sco.com/support/update/download/release.php?rid=367. Mount this ISO and then follow the If you are installing from CDs or CD ISO Images instructions below.
If you are installing from CDs or CD ISO Images:
# mount -F cdfs -r <cdrom-device> /cd-rom
where <cdrom-device> 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.
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.
# pkgadd -d /cd-rom ndThis is necessary to update configured network drivers in the kernel build tree.
# umount /cd-romand remove Supplement CD #1 from the CD drive.
# cd / # shutdown -i6 -g0 -y
See the section, Adding Software after Installing the Maintenance Pack 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:
On the client side, to install the Maintenance Pack from the server:
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:
If you are installing from CDs:
Insert CD #2 into the primary CD drive.
If you are installing from CD ISO Images:
Make sure nothing is already mounted on /cd-rom, and enter the following commands to mount the CD #2 ISO image:
# CD2DEV=`marry -a /osr600mp4/osr600mp4_cd2.iso` # mount -F cdfs -r $CD2DEV /cd-romThe shell variable CD2DEV will be used later.
If you are installing from Media Image Files:
Proceed to the next step; no action is required here.
Start the Software Manager by double-clicking its icon on the desktop, or by entering the following at the command-line prompt:
# scoadmin software
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:
If you are installing from CDs:
Select the appropriate CD-ROM drive as the Media Device and then select Continue.
If you are installing from CD ISO Images or Media Image Files:
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/osr600mp4/cd2.
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 Before Installing the Maintenance Pack, 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 <CTRL> 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.
For more information on upgrading some of these components, refer to the various Upgrade Notes in Before Installing the Maintenance Pack.
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:
If you are installing from CDs::
Remove CD #2 from the CD drive.
If you are installing from CD ISO Images::
Enter the following commands to unmount the CD #2 ISO image:
# umount /cd-rom # marry -d $CD2DEV
If you are installing from Media Image Files:
Proceed to the next step; no action is required here.
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:
# cd / # shutdown -i6 -g0 -yThis 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 4:
The OpenServer 6.0.0 MP4 CDs /info directory provides these Release and Installation Notes (the document you are reading) and additional release notes. See the /info directory for MP4 HBAs, networking device drivers, Java releases, Mozilla Firefox, and Mozilla Thunderbird release notes.
As described in the Before Installing the Maintenance Pack section, after installing MP4 you may need to restore your PHP, Apache 1, Cups, PostgreSQL, OpenLDAP, Squid, and/or Tomcat configuration/databases.
Also, if you installed the post OpenServer 6.0.0 MP3 Apache 2 web supplement, you need to back up any Apache 2 configuration file changes; remove that Apache 2 parcel, and then reapply those changes after installing MP4. See the Apache 2 feature section for more information.
To facilitate user transition to Firefox and Thunderbird, Mozilla is not removed from your system. Users can use either browser/mailer. Instructions for moving existing user Mozilla configurations to FireFox/Thunderbird are provided in the MP4 CDs' in the info/mozilla directory .
NOTE: If you intend to continue using Mozilla than you should download the final version for OpenServer 6.0.0, Mozilla 1.7.13Ca, from the SCO FTP site.
If you installed Firefox version 2.0.0.20 or later
before you installed MP4, then after installing MP4
you must remove this later version of Firefox and then reinstall it.
(ID: 535210:1)
If you installed Thunderbird version 2.0.0.19 or later before
installing MP4 and then installed Thunderbird 2.0.0.18 from CD #2,
you must remove the later version of Thunderbird and then reinstall it.
(ID: 535215:1)
The OpenServer 6.0.0 MP4 CD #1 has been designed to be a OpenServer 6.0.0 and UnixWare 7.1.4 ISL HBA CD. During an ISL installation of OpenServer 6.0.0 or UnixWare 7.1.4, you can obtain the latest OpenServer 6/UnixWare 7 by using the OpenServer 6.0.0 MP4 CD #1 when prompted for an HBA CD.
After installing the RS600D Release Supplement from MP4, 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.
PEAR modules for PHP 5 are not included in MP4.
If you are installing MP4 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 <Enter>
to continue with the installation.
(ID: 534538:1)
To fix this problem, append this line:
zoom="1"
to the $HOME/.mplayer/config configuration file.
(ID: 534416:1)
ln -s /opt/K/SCO/MySQL/4.1.10Na/usr/java/lib/mysql.jar \ /usr/java/lib/mysql.jar
In a future release we plan to create this link in a location that does not conflict with a Java upgrade.
After installing OpenServer 6.0.0 MP4 CD #1 you need to reboot your system before installing other products. This includes the additional software on the OpenServer 6.0.0 MP4 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)
Although upgrading to version 3.5.9 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 also install the KDE 3.5.9 i18n Language Support (http://www.sco.com/support/update/download/release.php?rid=305) to get matching localized support for the new KDE.Upgrading to KDE 3.5.9 renders the older KDE 3.3.2 language support packages obsolete if they are present on your system. It also removes symlinks to files in these now-obsolete packages, in turn causing custom verify errors. Therefore, if you have not previously removed them, 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.9 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:
custom -r KDE3FR # to remove KDE 3.3.2 French Language Support custom -r KDE3DE # to remove KDE 3.3.2 German Language Support
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)
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:
/usr/X11R7/bin/Xorg -configure
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:
mv /etc/xorg.conf /etc/xorg.conf.sav mv /xorg.conf.new /etc/xorg.conf
Restart the X server.
Starting with OpenServer 6.0.0 MP3,
AGP devices are supported.
However,
only a single instance of an X session is supported when an AGP device
is being used.
(ID: 535083:3)
OpenServer 6.0.0 MPs' release supplements (rs600d for MP4, rs600e for MP5, and so on) overwrite the sysmonitor app-default configuration. Any modifications you made to this file must be manually reapplied. The prior version of this file is saved in /usr/lib/X11/app-defaults/sysmonitor.prers600<release_supplement_letter>; for example, in /usr/lib/X11/app-defaults/sysmonitor.prers600d.
MP4 incorrectly reports a verify error for the /etc/named file. If you select the custom option to fix verify errors then custom will change the /etc/named link to a pre-MP4 binary. The old named binary will not function correctly with MP4. We thus recommend not fixing this verify error in MP4.
If you have already selected to fix this verify error then this link needs to be restored to its MP4 location. To do so log in as root and run these commands:
cd /etc
mv named named.old
mv named# named
The proper named link was moved to named# when you asked
custom to try to fix the verify errors.
The above steps restores the correct link.
(ID: 535181:2)
The ndc command includes erroneous pathnames. To use ndc, it is first necessary to run the following command to edit the pathname of various configuration files:
# cd /etc # cp -p ndc ndc.old # sed 's/\/etc\/inet/\/etc/g' < ndc.old > ndc
Note that with the upgrade to bind9, the command
rndc
is now the primary means for controlling the name daemon.
Ndc is provided as a compatibility front-end to rndc.
(ID: 535186:1)
The following error may sometimes be seen when trying to compile certain programs on OpenServer 6.0.0 MP4:
UX:ld: ERROR: library not found: -lintlThis problem occurs because there are a few libtool archive (compilation options and link directives) and a /usr/bin/*-config file that are still referencing libintl as a needed library to link against. This is incorrect. All should require linking againt libgnuintl instead.
If you are running the Open Office package supplied by SCO and had Open Office icons installed on your KDE desktop or KDE main panel, you will notice that they now appear as the default KDE application widget. To refresh these icons after installing MP4:
OpenServer 6.0.0 MP4 includes the following notable enhancements to OpenServer 6:
OpenServer 6.0.0 MP4 includes all the features previously provided in OpenServer 6.0.0 MP2. Description of these OpenServer 6.0.0 MP2 features follows:
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 http://ant.apache.org/. The documentation for ANT 1.6.5 is available at http://ant.apache.org/manual/index.html.
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 Serial ATA (SATA) Support).
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 Graphics 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 MP4 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 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 Managing Large Files.
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 updated this package to version 8.0.6f.
MP4 updates this package to version 8.0.6g. For more information, see Network Driver Package version 8.0.6g in §4.3: Features Provided in MP4.
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 4 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:
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 Filesystems to initialize and configure ODM. In particular, be sure to read the software notes and initialization instructions in the Overview and Installation document before you begin to use ODM. Also included are the ODM manual pages 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.
The Release Supplement includes many updates to existing manual pages and guides, as well as new documentation for the Online Data Manager (see above), a comparison of Release 5 and Release 6 kernel tunable parameters, 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 SCOAdmin 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 System Management → Performance 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="http://wiki.x.org/wiki/X11R69Release"> http://wiki.x.org/wiki/X11R69Release.
OpenServer 6.0.0 MP4 includes all the features previously provided in OpenServer 6.0.0 MP3. Description of these OpenServer 6.0.0 MP3 features follows:
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. Note that only a single instance of an X session is supported when an AGP device is being used.
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 PHP 5 Upgrade Notes and Apache 1 Upgrade Notes in §1: Before Installing the Maintenance Pack.
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:
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:
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 http://gmplib.org.
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:
For more details please see Appendix: Graphics libraries, Perl modules, and PHP PEAR modules.
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:
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, update 09d, contains the following fixes to the the J2SE 5.0's update 06 previously released on the SCO Support web site.
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 ( http://www.sco.com/support/update/download/release.php?rid=305). Additional KDE utilities and the KDE Integrated Development Environment, KDevelop, are provided on the SCO Skunkware download site at ftp://ftp2.sco.com/pub/skunkware/osr6/vols/. SCO SkunkWare is not officially supported; report any problems to skunkware@sco.com.
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 4 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 4 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 http://www.mplayerhq.hu/design7/info.html.
MP3 supplied version 8.0.6f of the network driver nd package.
MP4 updates this package to version 8.0.6g. For more information, see Network Driver Package version 8.0.6g in §4.3: Features Provided in MP4.
First-time installation of the nd package requires extra steps described in SVR5 Driver Updates in §1: Before Installing the Maintenance Pack.
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 Appendix: Graphics libraries, Perl modules, and PHP PEAR modules 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:$PATHbefore 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 http://www.postgresql.org/docs/8.2/static/release-8.2.html .
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 here 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:
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:
(*) 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:
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:
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_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 http://osr600doc.sco.com/en/HW_io/config_trigger_level.html
You can use the Modem Manager to configure USB Modem devices. For more details on the modem manager see: http://osr600doc.sco.com/en/HW_modem/modem_manager.html
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.
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.
We believe this problem is unlikely to be encountered in practice.
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: http://www.foolabs.com/xpdf/CHANGES
OpenServer 6.0.0 MP4 provides the following new features:
OpenServer 6.0.0 MP4 installs both the Apache 1 and Apache 2 Web Servers for SCO OpenServer 6.0.0. By default both Apache 1 and 2 are installed and are available for use, either separately or in combination.
NOTE: Apache 2 was first released as an OpenServer 6.0.0 MP3 web posting. The Apache Web Servers included in MP4 cannot be installed on top of SCO's web-released Apache 2 product; the MP4 web servers do upgrade prior OpenServer 6.0.0 Apache 1 releases.
If MP4 is attempted to be installed on a system with the web-released Apache 2, a clashing software message is displayed and you are directed to discontinue MP4's install.
To allow MP4's install in this case, you will first need to remove your existing web-released Apache 2 package. If you have made any changes to configurable Apache 2 files, such as /usr/lib/apache2/conf/httpd.conf (the main configuration file), you should save a copy before removing your existing Apache 2 package.
Once the web-released Apache 2 is removed, MP4 can be installed.
The docview patch that accompanied the Apache 2 handoff has also been integrated into MP4 (and now it works with either Apache 1 or Apache 2).
Whether either or both Apache servers will be active is controlled by their respective administration scripts:
/etc/apache # for Apache 1
/etc/apache2 # for Apache 2
Both of these scripts accept the same argument strings:
enable # have the server automatically run on reboot
disable # do not have the server started on reboot
restart # reset a running server; otherwise start it
start # begin running the server
stop # shutdown a running server
For example, /etc/apache2 enable causes Apache 2 to be run whenever your server is rebooted.
Also, both Apache 1 and 2 have their respective configuration files:
/usr/lib/apache/conf/httpd.conf
/usr/lib/apache2/conf/httpd.conf
A key part of what is specified in these files is the port number on which that server will be listening. Note: You cannot have the two different Apache servers listening on the same port number.
For http (the main way web pages are accessed), the default port number is 80 (see /etc/services), which is what is specified in both of the supplied httpd.conf files. A URL can name an explicit port number to use instead of 80, and will look like
http://myserver.com:1234/mypage.html
where the port specified here is 1234.
By default, Apache 1 listens on port 80.
Docview and Apache
System documentation is also made available in your web browser through a completely separate use of Apache for docview on port 8457. Docview also has a main administration script
/etc/docview
which accepts the following argument strings
start
stop
Docview will choose to use Apache 2 if it's installed as its documentation server, but it will use Apache 1 otherwise. So by default Apache 2 is the documentation server. If you want to have docview use Apache 1 even though Apache 2 is installed, add the following line to /etc/default/man:
APACHE=apache
Then stop and start up docview:
/etc/docview stop
/etc/docview start
Docview will continue to use Apache 1, even after reboots, until the APACHE=apache line is removed from /etc/default/man.
Running one or both Apache serversThe simplest approach to web serving is to choose one of Apache 1 or 2 to be enabled and running. For example, to have just Apache 2 used:
/etc/apache stop
/etc/apache disable
/etc/apache2 enable
/etc/apache2 start
However, there's no problem with having both Apache servers running at the same time as long as they are listening on separate ports.
For example, suppose you want Apache 2 to listen on port 80 and you also want Apache 1 enabled and serving web pages, but instead listening on, say, port 81. Be sure to choose a port number which is not already in use (not displayed by netstat -an) and not reserved for another application (look through /etc/services). Then:
Port 81
/etc/apache enable
/etc/apache2 enable
/etc/apache restart
/etc/apache2 restart
Both Apache servers accept various loadable modules to support:
and other capabilities. If you want to disable any of these modules, perhaps because of security concerns, edit the appropriate Apache configuration file:
/usr/lib/apache/conf/httpd.conf
/usr/lib/apache2/conf/httpd.conf
Search for lines that begin with
LoadModule
Then comment out (or just remove) the lines which refer to modules which you want to disable. After you're done editing the file(s) restart the affected Apache server(s). For example, run /etc/apache2 restart to restart the Apache 2 server.
OpenServer 6.0.0 MP4 includes an upgrade to bind version 9.4.2-P1. Among the new features in bind9, this version includes several critical security fixes related to weak query-ids (CVE-2007-2930) and cache-poisoning attacks (CVE-2008-1447).
There are several additional bind8 to bind9 migration issues that you may need to deal with as part of this upgrade. For example, several /etc/named.conf options have changed and logging categories are different. Details are available at http://uw714doc.sco.com/en/NET_tcpip/dnsN.main.html or at the ISC website http://www.isc.org.
CUPS is one of the two print systems included in OpenServer 6.0.0. It uses the Internet Printing Protocol ("IPP") as the basis for managing print jobs and queues, and supports network printer browsing and PostScript Printer Description ("PPD") based printing options.
This update includes CUPS 1.3.9. Among the features added are the following:
@LOCAL).
For a full list of updated features please see the "Changes in CUPS 1.2" and "Changes in CUPS 1.3" documents available below http://www.cups.org/documentation.php.
GNU Ghostscript 8.62 is included on the OpenServer 6.0.0 MP4 CD #1. This is a merge of GNU Ghostscript and the ESP Ghostscript fork used to support the CUPS printing system. This release includes many important bug fixes and improvements to performance, memory footprint, shading, and image
The Internet Group Management Protocol (IGMP) is upgraded to the Version 3. This version adds support for source filtering so that packets are either allowed or not allowed from specific source addresses. It is also commonly referred to as source-specific multicast in contrast any-source multicast.
The OpenServer 6.0.0 MP4 CD #1 has been designed to be a OpenServer 6.0.0 and UnixWare 7.1.4 ISL HBA CD. During an ISL installation of OpenServer 6.0.0 or UnixWare 7.1.4, you can obtain the latest OpenServer 6/UnixWare 7 by using the OpenServer 6.0.0 MP4 CD #1 when prompted for an HBA CD.
For more information,
see the various HBA README files in the
info/drivers directory of the MP4 CD or osr600mp4_cd1.iso,
image,
once mounted.
Following Sun MicroSystem's synchronized release of updates for all actively supported versions of the Java 2 Standard Edition (J2SE), SCO is releasing the same updates for the following J2SE versions supported on SCO OpenServer 6.0.0:
For a complete list of security issues resolved in each J2SE version, check the Release Notes for that version in the:
info/java directory of the MP4 CD or the
osr600mp4_cd1.iso image,
once mounted.
/opt/java2-1.x.x
Because these updates resolve numerous security issues, it is strongly recommended that all J2SE versions on your system be updated. J2SE 1.4.2 is part of MP4 and will be updated by default. The J2SE 5.0, update 16, is on the OpenServer 6.0.0 MP4 CD #2, and you must select this component for update or installation.
These J2SE updates are the same J2SE updates recently posted on the SCO Support web-site, but with a package installation change to make the Java plug-in module available to any Mozilla browser installed on the system.
Multiple major versions of J2SE can co-exist on your SCO UNIX platform.
The installation is to a version specific directory in /opt.
J2SE 1.4.2 ==>Updates to each major version of J2SE install in the same base directory./opt/java2-1.4.2
J2SE 5.0 ==>/opt/java2-1.5.0
Prior to an earlier synchronized release of J2SE 1.4.2_17 and 5.0 update 15,
the installation of the JRE piece for each of these major point releases
would automatically symbolicly link /usr/java and
/usr/java2 to point to the "newly" installed JRE
directory.
Starting with those synchronized J2SE releases,
the symbolic links will only be updated if the JRE being installed
is a later J2SE version than the current symbolic links.
For example, if prior to installation of J2SE 5.0, update 15, the symbolic links were:
Following the installation of J2SE 5.0, update 15, the links would be:/usr/java==>/opt/java2-1.4.2
/usr/java2==>/opt/java2-1.5.0
/usr/java==>/opt/java2-1.5.0
/usr/java2==>/opt/java2-1.5.0
Removal of the J2SE 5.0, update 15, will attempt to restore the pre-installation links,
if and only if an executable /opt/java2-1.4.2/bin/java
still exists on the system.
System administrators can and should readjust these symbolic links as needed by their specific system and software requirements.
Other software released by SCO for your SCO UNIX platform, as well as third party applications that use Java, may require a specific J2SE major version. That software may either reference the J2SE of interest through:
JAVA_HOME
that points to /usr/java
or directly to the installation directory /opt/java2-1.x.x
/usr/java/bin/command
or /opt/java2-1.x.x/bin/command
Caution: Before removing earlier/other major versions of J2SE on your system, be certain that other installed software does not require that version. For example, the Apache-Tomcat product released on UnixWare 7.1.4 and OpenServer 6.0.0 have been configured, tested and certified with J2SE 1.4.2. Removal of that JRE will result in Tomcat failing to start.
Mozilla® Firefox® is the browser successor to the Mozilla browser suite 1.7.x released as part of the OpenServer 6.0.0 product. Like the former releases of Mozilla for SCO platforms, Firefox is built from the source code open-sourced by the Mozilla Foundation. What previously was a single application with multiple functionality is now released as separate products; Firefox providing the browser and file download features. The e-mail client and news reader functions are provided by Mozilla ThunderbirdTM which is a separate component released as part of MP4, on CD2. The ChatZilla internet relay chat (IRC) feature of Mozilla is available through a Firefox add-on extension; see the "User Customization" section in the accompanying release notes..
While Firefox is the ultimate replacement for the Mozilla browser on OpenServer 6.0.0, installation of this Firefox release will install in parallel with the existing Mozilla browser. Installation of Firefox will not automatically remove Mozilla from your system. Because there are a variety of ways in which the "default browser" can be configured on any installed system, there is no simple way to automatically replace the Mozilla browser with the new Firefox browser. Allowing both browsers to be active on the system provides each site the opportunity to switch from Mozilla to Firefox at their convenience. If users have been using the Mozilla e-mail / news client, the Mozilla Thunderbird application will also need to be installed.
See the accompanying release notes for:
The release notes are in
the Firefox.README.html file in the
info/mozilla directory of the MP4 CD or osr600mp4_cd1.iso
image, once mounted. When Firefox is installed, this README will be installed
in /usr/lib/firefox/README.html.
Mozilla and Firefox are registered trademarks of the Mozilla Foundation.
Mozilla® ThunderbirdTM is the e-mail client and news group reader successor to the Mozilla browser suite 1.7.x released as part of the OpenServer 6.0.0 product. Like the former releases of Mozilla for SCO platforms, Thunderbird is built from the source code open-sourced by the Mozilla Foundation. What previously was a single application with multiple functionality is now released as separate products; the e-mail client and news reader functions are provided by Mozilla Thunderbird.
While Thunderbird is the ultimate replacement for the Mozilla e-mail client on OpenServer 6.0.0, installation of this Thunderbird release will install in parallel with the existing Mozilla suite. Installation of Thunderbird will not automatically remove Mozilla from your system. Because the functionality provided by the earlier Mozilla suite is now provided by separate applications, there is no simple way to automatically replace the Mozilla suite with the new Thunderbird e-mail client. Allowing both e-mail clients to be active on the system provides each site the opportunity to switch from Mozilla to Thunderbird at their convenience.
The Thunderbird component is contained on the OpenServer 6.0.0 MP4 CD #2. This component can be optionally installed following the installation of MP4.
For more information on the configuration and usage of Thunderbird,
migration from the Mozilla 1.7.x e-mail client,
and useful links for extensions and help from the Mozilla community,
see the Thunderbird.README.html release notes in the
info/mozilla directory of the MP4 CD or osr600mp4_cd1.iso
image, once mounted. When Thunderbird is installed, this README will be installed
in /usr/lib/thunderbird/README.html.
Mozilla and Thunderbird are trademarks and registered trademarks of the Mozilla Foundation.
KDE 3.5.9 is included on the OpenServer 6.0.0 MP4 CD #2. This release of KDE provides numerous security fixes as well as many important bug fixes and performance enhancements. Also, the KDE 3.5.9 i18n Language Support parcel is now included on the OpenServer 6.0.0 MP4 CD #2.
MP4 enhances the marry(7) command to support a configurable 128, 192, or 256 bit AES key length. A new -k option is provided to specify the key length. The default key length continues to be 128-bit to ensure compatibility with existing encrypted marry devices.
MP4 updates the Network Driver Package (nd) to version 8.0.6g. 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 step 11 of §2.1: Installing the Maintenance Pack from CD, CD ISO Image, or Media Images.First-time installation of the nd package requires an extra step described in SVR5 Driver Updates in §1: Before Installing the Maintenance Pack.
PostgreSQL 8.2.9 is included on the OpenServer 6.0.0 MP4 CD #1. This release of the PostgreSQL Database Server includes many performance and security enhancements. A complete list of changes can be found at http://www.postgresql.org/docs/8.2/static/release-8.2.html .
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. (Note: This step is not necessary if you have an earlier 8.2.* version of PostgreSQL installed.) Details on this process are provided here in these release notes.
Samba 3.0.30 is included on the OpenServer 6.0.0 MP4 CD #1. This release of Samba provides many important security and bug fixes as well as performance enhancements and support for interoperability with the Microsoft Vista operating system.
The fixes contained in this Maintenance Pack are described in the following sections (the references in parentheses following each description are internal tracking numbers).
MP4 contains the following fixes that were also included in MP1:
Backup and Restore
Files and Directories
Filesystems
Networking
MFSA 2005-56 Code execution through shared function objects MFSA 2005-55 XHTML node spoofing MFSA 2005-54 JavaScript prompt origin spoofing MFSA 2005-52 Same origin violation: frame calling top.focus() MFSA 2005-51 The return of frame-injection spoofing MFSA 2005-50 Possibly exploitable crash in InstallVersion.compareTo() MFSA 2005-48 Same-origin violation with InstallTrigger callback MFSA 2005-46 XBL scripts ran even when JavaScript disabled MFSA 2005-45 Content-generated event vulnerabilities
This updates the browser to the same code base as
Mozilla Firefox 1.0.6 and Thunderbird 1.0.6.
(ID: 532746, 532631)
# /etc/conf/cf.d/link_unix # shutdown -i6 -g0 -ySee the following manual pages for more information on ACLs: getacl(C), setacl(C), acl(S), facl(S), aclipc(S), aclsort(S).
System Management
/tmp/00448dos: Permission denied doscp: can't seize /dev/installThis happened because of a temporary file left behind by the first execution of the command. This problem has been fixed.
Development System
UX:acomp: ERROR: "compiler_err.c", line 12: internal compiler error: can't deal with op STAR ... UX:as: ERROR: /var/tmp/ctm2AAAa005X_:56:invalid operand combination: xorbThis problem is fixed.
MP4 contains the following fixes that were also included in MP2:
# rm file3g
rm: file3g non-existent
To:
# rm file3g
rm: file3g non-existent: Value too large for defined data type (error 79)
(ID: 532738:1)As root, enter: scoadmin international.
Set the Internal Codeset to ISO8859-15 using the Settings --> Codesets --> Internal Codeset menu command.
When the Internal Codeset is changed in the last step, the Console Codeset changes automatically to IBM858. You can also set the console codeset to ISO8859-15 using the Settings --> Codesets --> Console Codeset menu command, if desired. Both codesets will enable you to display the Euro symbol, but IBM858 is slightly preferable, because this setting lets you use an ansi-based TERM type (specifically, ansi-858).
Select an appropriate Console Keyboard from the list on the right of the International Settings screen.
Select File --> Save to save the new settings; then, File --> Exit to close the manager.
Further notes on displaying and printing the Euro symbol:
There's a minor bug in the X.org X server's keyboard layout files that prevents the Euro symbol from being correctly mapped in some keyboards. Use the xmodmap command to work around this problem. For example, the following commands map the Euro symbol to Alt-4 (the right-hand "Alt" key followed by "4"):
# xmodmap -e 'keycode 113 = Mode_switch' # xmodmap -e 'keycode 13 = 4 dollar currency currency'
(On many non-US keyboards, the first command above is not necessary.)
Other keyboard layouts place the Euro symbol on other keys, so different xmodmap commands would be called for. See the xmodmap(C) man page for details. Once the proper commands have been determined, they can be placed in $HOME/.startxrc so they will be run before every X session.
Note that Euro symbols do not work in scoterm; use xterm instead.
Euro symbols can also be typed using compose key sequences. Run the command:
# mapchan -f /usr/lib/mapchan/deadcomp
This enables the key sequence "^_ee" (control-underscore, e, e) to type a Euro symbol.
To print a file containing Euro symbols to a PostScript printer, set the LANG environment to refer to an ISO8859-15 locale, as in this example:
# LANG=en_US.ISO8859-15 lp <filename>
xterm -fn 8x13bold-15The International Setting Manager now modifies the default X font.alias file, so that when the administrator chooses an internal codeset of ISO8859-15, a font with the Euro symbol will be used in xterm and other applications. Changing to a different internal codeset will revert the fonts back to their original state.
int *" and not "const int *".
Also updated header file /usr/include/netdb.h.
installf: ERROR: bad entry read in contents file
pathname=/tmp
problem=illegal value for mode
UX:pkginstall: ERROR: postinstall script did not complete successfully.
This problem has been resolved.
PANIC: DBLFLT exception; registers saved in TSS 0xFFFF5AF0
...
Observed cases so far have been provoked by the SIOCGIFCONF ioctl.
This problem has been resolved.
(Also see the Security section for security updates to CUPS.)
A vulnerability in Lynx can be exploited by malicious people to compromise a user's system.
The vulnerability is caused by a boundary error in the "HTrjis()" function's handling of article headers sent from NNTP (Network News Transfer Protocol) servers. This can be exploited to cause a stack-based buffer overflow (e.g. by tricking a user into visiting a malicious web site which redirects to a malicious NNTP server via the "nntp:" URI handler).
Successful exploitation allows execution of arbitrary code.
(ID: 533159:4)
Remote exploitation of a command injection vulnerability could allow attackers to execute arbitrary commands with the privileges of the underlying user.
The problem specifically exists within the feature to execute
local cgi-bin programs via the "lynxcgi:" URI handler. The handler is
generally intended to be restricted to a specific directory or program(s).
However, due to a configuration error on multiple platforms, the default
settings allow for arbitrary websites to specify commands to run as the user
running Lynx.
(ID: 533314:6)
A blind connection-reset attack is reported, which takes advantage of the specification that describes that on receiving a 'hard' ICMP error, the corresponding connection should be aborted. A remote attacker may terminate target TCP connections and deny service for legitimate users.
An ICMP Source Quench attack is reported, which exploits the specification that a host must react to ICMP Source Quench messages by slowing transmission on the associated connection. A remote attacker may effectively degrade performance for a legitimate connection.
To fix these issues, a new networking parameter tcp_ignore_quench is
introduced
for configuring ICMP source quench message behavior for tcp connections. When
it is set to 1, ICMP source quench messages are ignored for tcp connections.
Default value of this parameter is 1.
(ID: 533089:2 ESC: erg712928)
store.c in Squid 2.5.STABLE10 and earlier allows remote attackers to cause a denial of service (crash) via certain aborted requests that trigger an assert error related to STORE_PENDING.
The sslConnectTimeout function in ssl.c for Squid 2.5.STABLE10
and earlier allows remote attackers to cause a denial of service
(segmentation fault) via certain crafted requests.
(ID: 533116:1)
Squid 2.5.STABLE10 and earlier, while performing NTLM
authentication, does not properly handle certain request
sequences, which allows attackers to cause a denial of service
(daemon restart).
(ID: 533151:1)
The rfc1738_do_escape function in ftp.c for Squid 2.5 STABLE11
and earlier allows remote FTP servers to cause a denial of
service (segmentation fault) via certain "odd" responses.
(ID: 533254:1)
zgrep in gzip does not properly sanitize arguments, which allows local users to execute arbitrary commands via filenames that are injected into a sed script.
Race condition in gzip, when decompressing a gzipped file, allows local users to modify permissions of arbitrary files via a hard link attack on a file while it is being decompressed, whose permissions are changed by gzip after the decompression is complete.
Directory traversal vulnerability in gunzip -N allows remote attackers to
write
to arbitrary directories via a .. (dot dot) in the original filename within a
compressed file.
(ID: 532855:1 ESC: erg712906)
Tavis Ormandy has reported a vulnerability in libTIFF, which potentially can be exploited by malicious people to compromise a vulnerable system.
The vulnerability is caused due to a boundary error and can be exploited to cause a buffer overflow via a specially crafted TIFF image containing a malformed BitsPerSample tag.
Successful exploitation may allow execution of arbitrary code, if a malicious
TIFF image is opened in an application linked against the vulnerable library.
(ID: 532777:1 ESC: erg712888)
The error handling in the (1) inflate and (2) inflateBack functions in ZLib compression library 1.2.x allows local users to cause a denial of service (application crash).
inftrees.h in zlib 1.2.2 allows remote attackers to cause a denial of service (application crash) via an invalid file that causes a large dynamic tree to be produced.
Buffer overflow in zlib 1.2 and later versions allows remote attackers to
cause
a denial of service (crash) via a crafted compressed stream, as demonstrated
using a crafted PNG file.
(ID: 532829:1 ESC: erg712899)
MP4 contains the following fixes that were also included in MP3:
Specifying "ACPI=X" in /stand/boot or at the interactive boot prompt enables hybrid ACPI/MPS initialization when hyperthreading or multicore support is also enabled. Hybrid ACPI/MPS initialization should be enabled only if the default full-ACPI based initialization fails.
2. Implement dynamic PCI interrupt assignment to fix interrupt related problems seen on some platforms when hyperthreading, multicore, and/or ACPI are enabled. Observed problems included excess interrupt activity, poor device response, and device timeouts.
3. Allow override of kernel algorithms for sorting the processors listed in ACPI BIOS tables through the use of the new LAPIC_SORT parameter. This is necessary on some platforms to ensure that all logical processors can be used even if the ACPIS BIOS tables does not list them in the proper order.
Specifying "LAPIC_SORT=Y" in /stand/boot or at the interactive boot prompt will cause the kernel to reorder the processors listed in the ACPI BIOS tables; "LAPIC_SORT=N" disables that reordering. If LAPIC_SORT is unspecified, then the kernel uses its own internal algorithm to determine whether to reorder the processors listed in the tables. (ID: 533926:1)
This very unusual situation only occurred when an inode number was first used for /dev/udp or /dev/tcp, then deleted, and then reused for a named pipe. (ID: 533770:3)
The memory allocation policy for Xenix programs in OSR6 has been loosened to match OSR5, allowing such programs to work as before.
It is no longer necessary to set XEMUL_OSR5 to obtain Xenix execution behavior compatible with OSR5. Such behavior is now the default and only case available. The XEMUL_OSR5 environment variable is no longer supported. The default behavior is now as if XEMUL_OSR5=1 had been set. Pre-OSR5 behavior is no longer supported. (ID: 534333:1)
Notes:
USB modems & serial port adapters need to be plugged in and powered
on for the /dev/usb_ser* device nodes to be created and listed in the
serial and modem managers.
Automatic detection is not available for USB modems - use the manual configuration option with the Standard Modem selection. (ID: 534245:3)
Sendmail has been updated to version 8.13.8 which is not vulnerable to this attack. (ID: 534042:4)
Sendmail has been updated to version 8.13.8 which is not vulnerable to this attack. (ID: 533700:4)
MP4 contains the following additional fixes that were not in MP3:
void _flushlbf(void); size_t __fbufsiz(FILE *stream); size_t __fpending(FILE *stream); void __fpurge(FILE *stream); int __flbf(FILE *stream); int __freading(FILE *stream); int __fwriting(FILE *stream); int __freadable(FILE *stream); int __fwritable(FILE *stream);(ID: 535164:1)
1. The OS sometimes failed to recognize some processor cores because of mishandling of the LAPIC_SORT boot parameter. Previously, the LAPIC_SORT boot parameter erroneously defaulted to NO and setting it to YES has no effect; it now defaults to YES.
2. The number of available processor cores may be cut in half on systems on which the processor supports hyperthreading but on which the BIOS has hyperthreading disabled.
3. An error in the processor licensing check could prevent some processor cores from coming online even when the system had the requisite processor licensing. (ID: 534338:2)
The following libraries are provided as part of the Supplemental Graphics, Web and X11 Libraries parcel (see Before Installing the Maintenance Pack).
| Software Components and Packages | Abbreviation | FCS Version | MP2 Version | MP3/MP4 Version |
| 3D Athena Widget Set for X11 | xaw3d | 1.5E | 1.5E | 1.5E |
| Apache Portable Runtime Utility Library | aprutil | n/a | n/a | 1.2.8 |
| Apache Portable Runtime | apr | n/a | n/a | 1.2.9 |
| Accessibility Toolkit | atk | 1.8.0 | 1.10.3 | 1.10.3 |
| bzip2 compression library and utilities | bzip2 | 1.0.3 | 1.0.3 | 1.0.3 |
| Cairo Graphics Library | cairo | n/a | 1.0.2 | 1.4.10 |
| compface Image Manipulation Library | compface | 1.0.0 | 1.0.0 | 1.5.2 |
| cURL URL Library | curl | 7.13.2 | 7.15.1 | 7.16.4 |
| Berkeley-DB Database Library | bdb | 4.3.27 | 4.3.28 | 4.6.18 |
| Expat XML Parser | expat | 1.95.8 | 1.95.8 | 2.0.1 |
| Expect TCL Extension | expect | 5.42 | 5.43 | 5.43 |
| FontConfig | fontcfg | 2.2.2 | 2.2.2 | 2.4.2 |
| FreeType Font Engine Version 1 | freetype1 | 1.3.1 | 1.3.1 | 1.3.1 |
| FreeType Font Engine | freetype2 | 2.1.9 | 2.1.10 | 2.3.5 |
| GD Graphics Library | gd1 | 1.8.4 | 1.8.4 | 1.8.4 |
| GD Graphics Library | gd2 | 2.0.33 | 2.0.33 | 2.0.35 |
| GNU dbm Library | gdbm | 1.8.0 | 1.8.0 | 1.8.0 |
| Gnome DOM Library | gdome2 | 0.8.1 | 0.8.1 | 0.8.1 |
| GNU gettext | gettext | 0.14.1 | 0.14.5 | 0.16.1 |
| GIF Image Manipulation Library | giflib | 4.1.0 | 4.1.0 | 4.1.4 |
| GIMP Portability Library | glib1 | 1.2.10 | 1.2.10 | 1.2.10 |
| GIMP Portability Library | glib2 | 2.4.8 | 2.8.4 | 2.12.13 |
| GNU Privacy Guard (gnupg) | gnupg | 1.4.0 | 1.4.0 | 1.4.7 |
| GIMP Toolkit | gtk1 | 1.2.10 | 1.2.10 | 1.2.10 |
| GIMP Toolkit | gtk2 | 2.4.14 | 2.8.9 | 2.10.14 |
| GWXLIBS Base Support Tools | gwxlibs | 2.0.0 | 2.1.0 | 3.0.0 |
| International Components for Unicode (ICU) | icu | 3.2 | 3.4 | 3.6 |
| Enlightenment Imaging Library | imlib | 1.10.0 | 1.10.0 | 1.9.15 |
| JASper JPEG2000 library | jasper | 1.701.0 | 1.701.0 | 1.900.1 |
| ISO/IEC 11544:1993 JBIG kit | jbig | 1.6 | 1.6 | 1.6 |
| IJG JPEG library | jpeg | 6b | 6b | 6b |
| JavaScript Embedded C Library | js | 1.5rc5 | 1.5rc5 | 1.5 |
| Little Color Management System (LCMS) | lcms | 1.14 | 1.15 | 1.16 |
| Gnome IDL Library | libIDL | 0.85 | 0.8.6 | 0.8.8 |
| Gnome ART library | libart | 2.3.17 | 2.3.17 | 2.3.19 |
| Gnome CSS2 Parsing Toolkit (libcroco) | libcroco | 0.6.0 | 0.6.0 | 0.6.1 |
| Gnome EXIF Widget for GTK | exifgtk | 0.3.5 | 0.3.5 | 0.3.5 |
| EXIF Processing Library | libexif | 0.6.10 | 0.6.12 | 0.6.16 |
| GNU Cryptographic Library | libgcrypt | 1.2.1 | 1.2.2 | 1.2.4 |
| Gnome HTTP Client Library | libghttp | 1.0.9 | 1.0.9 | 1.0.9 |
| GNU Privacy Guard Error Library | libgpg-err | 1.0.0 | 1.0.0 | 1.5 |
| Gnome Structured File Library | libgsf | 1.11.1 | 1.13.3 | 1.14.5 |
| Gnome HTML Widget for GTK | gtkhtml | 2.6.3 | 2.11.0 | 2.11.0 |
| Multi-image Network Graphics (MNG) Library | libmng | 1.0.9 | 1.0.9 | 1.0.10 |
| Portable Network Graphics (PNG) Library | libpng | 1.2.8 | 1.2.8 | 1.2.18 |
| Gnome SVG Rendering Library | librsvg | 2.9.5 | 2.13.3 | 2.18.0 |
| WMF Conversion Library | libwmf | n/a | 0.2.8.4 | 0.2.8.4 |
| W3C Consortium Library (libwww) | libwww | 5.40 | 5.40 | 5.40 |
| libxml2 XML C Parser and Toolkit | libxml2 | 2.6.19 | 2.6.22 | 2.6.29 |
| libxslt XSLT C Parser and Toolkit | libxslt | 1.1.14 | 1.1.15 | 1.1.21 |
| Libtool Dynamic Loading | ltdl | 1.5.22 | 1.5.22 | 1.5.22 |
| MD5 Hash Library | md5 | 1.0.0 | 1.0.0 | 1.0.0 |
| mktemp | mktemp | 1.5 | 1.5 | 1.5 |
| OSSP mm Shared Memory Allocation Library | mm | 1.3.1 | 1.4.0 | 1.4.2 |
| MPEG Encoder/Decoder Library | mpeglib | 1.2.1 | 1.2.1 | 1.3.1 |
| Portable Bitmap Utilities and Libraries | netpbm | 10.26.1 | 10.26.14 | 10.34 |
| OpenLDAP | openldap | 2.2.24 | 2.2.30 | 2.3.37 |
| OpenSLP (Service Location Protocol) | openslp | 1.2.1 | 1.2.1 | 1.2.1 |
| OpenSSL | openssl | 0.9.7g | 0.9.7i/0.9.6m | 0.9.7m/0.9.8e* |
| Pango Layout and Text Rendering Library | pango | 1.4.1 | 1.10.2 | 1.17.3 |
| Perl Compatible Regular Expressions | pcre | 5.0 | 6.4 | 7.2 |
| pkg-config | pkgconfig | pre 0.19 | 0.19 | 0.22 |
| Gnome Option Processing Library | popt | 1.7 | 1.7 | 1.10.4 |
| True Random Library | rand | 1.0.0 | 1.0.0 | 1.0.0 |
| GNU readline | readline | 5.0 | 5.1 | 5.2 |
| Sablotron XML, DOM and XPath Processor | sablot | 1.0.1 | 1.0.2 | 1.0.3 |
| Cyrus SASL | sasl | 2.1.20 | 2.1.20** | 2.1.22 |
| S-lang Interpreter and Library | slang | 1.4.9 | 1.4.9 | 1.4.9 |
| Tcl 8.4 | tcl84 | 8.4.9 | 8.4.10 | 8.4.15 |
| Extended Tcl | tclx84 | 8.3.5 | 8.3.5 | 8.4 |
| TIFF library and utilities | tiff | 3.7.2 | 3.7.4 | 3.8.2 |
| Tk 8.4 | tk84 | 8.4.9 | 8.4.10 | 8.4.14 |
| trio printf library | trio | 1.10 | 1.10 | 1.12 |
| Xalan XSLT Processor | xalan | 1.9.0 | 1.10.0 | 1.10.0 |
| Xerces Validating XML C++ Parser | xerces | 2.6.0 | 2.7.0 | 2.7.0 |
| XML Security Library | xmlsec1 | 1.2.8 | 1.2.9 | 1.2.10 |
| X.org Fonts | XORGFonts | 6.8.2 | 6.9.0 | 7.2.0 |
| X.org Runtime | XORGRT | 6.8.2 | 6.9.0 | 7.2.0 |
| zlib compression library | zlib | 1.2.2 | 1.2.3 | 1.2.3 |
* For OpenServer 6.0.0 MP3, OpenSSL 0.9.8e has been added; OpenSSL 0.9.7 is upgraded from 0.9.7i to 0.9.7m; and OpenSSL 0.9.6m is deprecated and no longer provided.
** With respect to Cyrus-SASL: the version did not change in OpenServer 6.0.0 MP2 but the way it was compiled significantly changed. In previous (prior to OpenServer 6.0.0 MP2) releases all of the backends were static. All the backends are now dynamic.
The core Perl interpreter was upgraded from 5.8.6 (5.8.7 in MP2) to 5.8.8. The following Perl extensions are included with 5.8.8:
Archive-Tar-1.32 Archive-Zip-1.20 Authen-SASL-2.10 BerkeleyDB-0.32 Bit-Vector-6.4 Cache-2.04 Cache-Cache-1.05 Carp-Clan-5.9 Class-ErrorHandler-0.01 Class-Loader-2.03 Compress-Bzip2-2.09 Compress-Zlib-1.42 Convert-ASCII-Armour-1.4 Convert-ASN1-0.21 Convert-PEM-0.07 Crypt-Anubis-1.0.4 Crypt-Blowfish-2.10 Crypt-Blowfish_PP-1.12 Crypt-CAST5-0.05 Crypt-CAST5_PP-1.04 Crypt-CBC-2.22 Crypt-DES-2.05 Crypt-DES_EDE3-0.01 Crypt-DES_EEE3-0.01 Crypt-DES_PP-1.00 Crypt-DH-0.06 Crypt-DSA-0.14 Crypt-ECB-1.40 Crypt-GOST-1.00 Crypt-IDEA-1.08 Crypt-OpenPGP-1.03 Crypt-OpenSSL-Bignum-0.04 Crypt-OpenSSL-DSA-0.13 Crypt-OpenSSL-RSA-0.25 Crypt-OpenSSL-Random-0.04 Crypt-OpenSSL-SMIME-0.02 Crypt-Primes-0.50 Crypt-RIPEMD160-0.04 Crypt-RSA-1.58 Crypt-Random-1.25 Crypt-Rijndael-1.04 Crypt-Rot13-0.6 Crypt-SEAL2-1.0.4 Crypt-SSLeay-0.56 Crypt-Salt-0.01 Crypt-SmbHash-0.12 Crypt-TripleDES-0.24 Crypt-Twofish-2.12 Crypt-Twofish2-1.01 Crypt-UnixCrypt-1.0 DBD-SQLite-1.12 DBD-SQLite2-0.33 DBI-1.58 DBM-Any-0.1 Data-Buffer-0.04 Data-Random-0.05 Data-ShowTable-3.3 Date-Calc-5.4 DateManip-5.44 Devel-Symdump-2.07 Digest-BubbleBabble-0.01 Digest-EMAC-1.2 Digest-HMAC-1.01 Digest-MD2-2.03 Digest-MD4-1.5 Digest-Nilsimsa-0.06 Digest-SHA-5.45 Digest-SHA1-2.11 Digest-SHA2-1.1.1 Error-0.17008 ExtUtils-CBuilder-0.19 ExtUtils-ParseXS-2.18 File-NFSLock-1.20 File-PM2File-0.08 File-Package-0.06 File-SmartNL-0.05 File-Where-0.05 FreezeThaw-0.43 Getopt-ArgvFile-1.11 HTML-Clean-0.8 HTML-FillInForm-1.06 HTML-Parser-3.56 HTML-SimpleParse-0.12 HTML-TagReader-1.08 HTML-Tagset-3.10 HTML-Tree-3.23 HTML-TreeBuilder-XPath-0.08 HTTP-GHTTP-1.07 Heap-0.80 IO-Multiplex-1.09 IO-Socket-SSL-1.07 IO-String-1.08 IO-Zlib-1.07 IO-stringy-2.110 IPC-MM-0.03 IPC-ShareLite-0.09 MIME-Lite-3.01 MIME-Types-1.20 MIME-tools-5.420 MLDBM-2.01 MLDBM-Sync-0.30 MailTools-1.77 Math-Pari-2.010604 Module-Build-0.2808 Module-ScanDeps-0.60 Module-Signature-0.55 Msgcat-1.03 Net-DNS-0.60 Net-DNS-Codes-0.09 Net-DNS-SEC-0.14 Net-DNS-ToolKit-0.31 Net-Daemon-0.39 Net-Daemon-SSL-1.0 Net-IP-1.25 Net-Server-0.97 Net-ext-1.011 NetAddr-IP-4.007 Net_SSLeay.pm-1.30 PAR-0.94 PAR-Dist-0.10 Parse-RecDescent-1.94 Parse-Yapp-1.05 Perl-Tidy-20070508 PlRPC-0.2020 Pod-Coverage-0.18 Pod-Escapes-1.04 Pod-Readme-0.09 Pod-Simple-3.05 RPC-XML-0.59 Regexp-Common-2.120 Sort-Versions-1.5 String-CRC32-1.4 Test-Pod-1.26 Test-Pod-Coverage-1.08 Test-Portability-Files-0.05 Text-Iconv-1.4 Tie-Cache-0.17 Tie-EncryptedHash-1.21 Tie-Gzip-0.06 Tie-IxHash-1.21 Tie-TextDir-0.06 TimeDate-1.16 URI-1.35 Unicode-Map8-0.12 Unicode-String-2.09 Unix-Syslog-0.100 XML-DOM-1.44 XML-DOM-XPath-0.13 XML-Dumper-0.81 XML-Encoding-2.01 XML-Filter-BufferText-1.01 XML-GDOME-0.86 XML-GDOME-XSLT-0.75 XML-Generator-1.01 XML-Generator-DBI-1.00 XML-Generator-PerlData-0.89 XML-Grove-0.46alpha XML-Handler-YAWriter-0.23 XML-LibXML-1.63 XML-LibXML-Common-0.13 XML-LibXSLT-1.62 XML-NamespaceSupport-1.09 XML-Parser-2.34 XML-SAX-0.16 XML-SAX-Expat-0.39 XML-SAX-Writer-0.50 XML-Sablotron-1.01 XML-Simple-2.16 XML-Twig-3.29 XML-Writer-0.603 XML-Writer-String-0.1 XML-XPath-1.13 XML-XPathEngine-0.08 XML-XSLT-0.48 YAML-0.65 gettext-1.05 libwww-perl-5.806 libxml-enno-1.02 libxml-perl-0.08
© 2009 The SCO Group, Inc. All rights reserved.