SCO OpenServer Release 5.0.7 Maintenance Pack 3 Release and Installation Notes

The SCO OpenServer(TM) Maintenance Pack 3 contains important fixes for your SCO OpenServer Release 5.0.7 system and should be applied at your next maintenance period.

NOTE: This is the second SCO OpenServer Release 5.0.7 Maintenance Pack. To preserve a numerical correlation with Update Pack 3, this Maintenance Pack is named MP3. There is no Maintenance Pack 2.

These Release and Installation Notes contain critical information that you need to know before and after installing SCO OpenServer Release 5.0.7 Maintenance Pack 3. Please familiarize yourself with the information that is relevant to your system, then install the Maintenance Pack according to the instructions in this document.

NOTE: Unless otherwise noted, this document supplements the SCO OpenServer Release 5.0.7 Late News, which are still relevant. As information becomes available after the publication of these Release and Installation Notes, it is added to the SCO OpenServer Release 5.0.7 Late News document, available from the SCO web site at:

http://www.sco.com/support/docs/openserver

These Release and Installation Notes cover the following topics:

About Maintenance Packs and Update Packs

There are two support ``tracks'' that are available to SCO OpenServer Release 5.0.7 customers:


Maintenance Packs
A Maintenance Pack (MP) is a collection of security updates and fixes for reported problems. Maintenance Packs are made available periodically and can be downloaded and installed free-of-charge. Maintenance Packs are cumulative, so only the latest one needs to be installed.

Update Packs
An Update Pack (UP) is a collection of some of the new features and product enhancements that will be included in the next SCO OpenServer release. Available only for registered subscribers to the SCO Update Service, Update Packs provide a simplified and streamlined process for deploying new technology and keeping systems updated.

Update Packs supplement the Maintenance Packs. Each Update pack requires the installation of a corresponding Maintenance Pack. Update Packs are cumulative, so you only need to install the latest Maintenance Pack plus the latest Update Pack to bring the system up to date with the latest features and enhancements.

Obtaining Maintenance Packs

SCO OpenServer Maintenance Packs are available for download from the SCO OpenServer Release 5.0.7 Maintenance Pack web page:

http://www.sco.com/support/update/download/osr507mp.html

If your SCO OpenServer media kit contains the SCO OpenServer SCO OpenServer Release 5.0.7 Supplement CD, you can install the MP from the CD. You should check the SCO OpenServer Release 5.0.7 Supplements web page, however, to verify that the Supplement CD contains the most current Maintenance Pack available.

Before installing the Maintenance Pack

Before installing SCO OpenServer Release 5.0.7 Maintenance Pack 3, note the following:


Maintenance Pack Installation

NOTE: Be sure to read ``Before installing the Maintenance Pack'' prior to starting this procedure.

You can acquire and install SCO OpenServer Release 5.0.7 Maintenance Pack 3:

If there are multiple systems on your TCP/IP network that require Maintenance Pack 3, you can load and install the MP on a software server and use it as a centralized distribution point. See ``Installing the Maintenance Pack across the network'' for more information.

Installing the Maintenance Pack using SCO Update

SCO Update allows you to install Maintenance and Update Packs directly over the Internet. This approach saves you the time -- and extra hard disk space -- of first downloading installable image files from the SCO web or FTP sites.

NOTE: Maintenance Pack 1 added support for SCO Update to the Software Manager. If MP1 was never installed on your system, SCO Update will not be available from within the Software Manager until after you install MP3.

To use SCO Update:

  1. Log in as root.

  2. Start the Software Manager by double-clicking on its icon on the desktop, or by entering the following at the command-line prompt:

    scoadmin software

  3. From the Software menu, select SCO Update. The system connects to the SCO Update server.

    The Install Selection window displays all of the SCO OpenServer Release 5.0.7 update packs, maintenance packs, drivers, and so forth that are currently available.

  4. Highlight "Maintenance Pack 3" and click on Install.

    The selected software is automatically downloaded and installed on your system.

    WARNING: The Software Manager displays one or more warnings if the Maintenance Pack contains fixes for software features that are not currently installed on your system. If you do not plan to install the affected package (for example: SMP), you can ignore such messages and click on Continue. However, if you do plan to install this package later, you should stop the install process, install the package in question from the installation media, and restart the Maintenance Pack installation. This ensures the fixes are applied properly (and avoids potential problems).

    If any Maintenance Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Maintenance Pack as only partially installed. This is normal.

  5. When the installation is complete, click on OK.

  6. Exit the Software Manager by selecting the Host menu, then Exit.

  7. Reboot the machine. (Because the Software Manager relinks the kernel, you must reboot before the new kernel takes effect.)

We recommend that you use SCO Update periodically to check for new updates, fixes, or drivers for SCO OpenServer Release 5.0.7.

Installing the Maintenance Pack from downloaded media images

To install the SCO OpenServer Release 5.0.7 Maintenance Pack 3 from media images that you manually download:

  1. Log in as root.

  2. Download the Maintenance Pack from either the SCO web site or using FTP:

    NOTE: Maintenance Pack 3 consists of a tar archive containing a number of media image files with names of the form VOL.000.000, VOL.000.001, and so forth. (You also have the option of downloading the individual VOL files.) Because all update and maintenance packs use this same filename scheme, you should create a master directory with a unique subdirectory to store each pack. The master directory could be /usr/updates, /usr/spool/patches, or whatever suits your system layout. The master hierarchy should be writable by root only.

    If you download the individual files rather than the tar archive, please be sure to carefully verify that all of the sequentially-numbered VOL files are present in your download directory before proceeding.

  3. Download the 507mp3_vol.tar file and use this command to extract the media image files:

    tar xvf 507mp3_vol.tar

  4. Start the Software Manager by double-clicking on its icon on the desktop, or by entering the following at the command-line prompt:

    scoadmin software

  5. From the Software menu, select Install New.

  6. When prompted for the host (machine), select the current host and then click on Continue.

  7. Select Media Images as the Media Device, then click on Continue. (You may need to scroll down before you see the Media Images option.)

  8. Enter the absolute pathname for the directory that contains the Maintenance Pack 3 media images. For example:

    /usr/spool/patches/507mp3

    Click on OK.

  9. In the Install Selection window, make sure that the Maintenance Pack is highlighted, then click on Install.

    NOTE: Any component of the Maintenance Pack that updates existing software (such as the RS507B Release Supplement) must be installed. New features such as cdrtools are optional.

  10. If you previously installed any of the components that are modified by the Maintenance Pack, you are notified that these components will be upgraded. Click on Continue.

    Additionally, you are warned if certain packages in the Maintenance Pack will not be installed because the software they modify is not installed on your system. Click on Continue.

    WARNING: The Software Manager displays one or more warnings if the Maintenance Pack contains fixes for software features that are not currently installed on your system. If you do not plan to install the affected package (for example: SMP), you can ignore such messages and click on Continue. However, if you do plan to install this package later, you should stop the install process, install the package in question from the installation media, and restart the Maintenance Pack installation. This ensures the fixes are applied properly (and avoids potential problems).

    If any Maintenance Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Maintenance Pack as only partially installed. This is normal.

  11. When the installation is complete, click on OK. The Software Manager lists Maintenance Pack 3 among the installed software.

  12. Exit the Software Manager by selecting the Host menu, then Exit.

  13. Reboot the machine. (Because the Software Manager relinks the kernel, you must reboot before the new kernel takes effect.)

Installing the Maintenance Pack from CD-ROM

To install the SCO OpenServer Release 5.0.7 Maintenance Pack 3 from the SCO OpenServer Release 5.0.7 Supplement CD Version 3:

  1. Log in as root.

  2. Insert the SCO OpenServer Release 5.0.7 Supplement CD Version 3 into the drive.

  3. Start the Software Manager by double-clicking on its icon on the desktop, or by entering the following at the command-line prompt:

    scoadmin software

  4. From the Software menu, select Install New.

  5. When prompted for the host (machine), select the current host and then click on Continue.

  6. Select the appropriate CD-ROM drive as the Media Device, then click on Continue.

  7. In the Install Selection window, make sure that the Maintenance Pack is highlighted, then click on Install.

    NOTE: Any component of the Maintenance Pack that updates existing software (such as the RS507B Release Supplement) must be installed. New features such as cdrtools are optional.

  8. If you previously installed any of the components that are modified by the Maintenance Pack, you are notified that these components will be upgraded. Click on Continue.

    WARNING: The Software Manager displays one or more warnings if the Maintenance Pack contains fixes for software features that are not currently installed on your system. If you do not plan to install the affected package (for example: SMP), you can ignore such messages and click on Continue. However, if you do plan to install this package later, you should stop the install process, install the package in question from the installation media, and restart the Maintenance Pack installation. This ensures the fixes are applied properly (and avoids potential problems).

    If any Maintenance Pack fixes were not installed because the corresponding feature was not present, the Software Manager shows the Maintenance Pack as only partially installed. This is normal.

  9. When the installation is complete, click on OK. The Software Manager lists Maintenance Pack 3 among the installed software.

  10. Exit the Software Manager by selecting the Host menu, then Exit.

  11. Reboot the machine. (Because the Software Manager relinks the kernel, you must reboot before the new kernel takes effect.)

Installing the Maintenance Pack across the network

You can install SCO OpenServer Release 5.0.7 Maintenance Pack 3 from one SCO OpenServer Release 5.0.7 system onto another across a TCP/IP network. To do so, you need a software server, which you can create as described in "Installing and managing software over the network" in the SCO OpenServer Networking Guide. This server has a user account called swadmin.

Install or load Maintenance Pack 3 on the software server using one of the installation procedures described in ``Maintenance Pack Installation''. Also see "Installing and managing software components" in the SCO OpenServer Handbook for more information on loading software.

To install Maintenance Pack 3 onto a local machine once the Maintenance Pack is available from the software server, start the Software Manager and select Install New. In the Begin Installation window, you are prompted for the source location of the Maintenance Pack. Select From Another Host. You need to provide the name of the software server, as well as the password of the swadmin user on the software server.

Removing a Maintenance Pack

WARNING: Because of interdependencies between the components that are included in Maintenance Packs, partial removal of an MP is not supported.

Removing Maintenance Pack 3 de-installs the Apache Web Server, Perl, and Supplemental Graphics, Web, and X11 Libraries components. When these components are removed, many system functions will cease to work, including Squid, Samba, and the GNU Development Tools (if installed).

After removing the Maintenance Pack, it is imperative that you reinstall the Apache Web Server, Perl, and Supplemental Graphics, Web, and X11 Libraries components from your SCO OpenServer Release 5.0.7 System CD-ROM. This section explains how to do this.

To remove the Maintenance Pack and reinstall your Release 5.0.7 versions of the Apache Web Server, Perl, and Supplemental Graphics, Web, and X11 Libraries components:

  1. Log in as root.

  2. Start the Software Manager by double-clicking its icon on the desktop, or by entering the following at the command-line prompt:

    scoadmin software

  3. Select the Maintenance Pack in the list of installed software.

  4. From the Software menu, select Remove Software. In the confirmation window, verify that you selected the correct software, then click on Remove.

  5. A window displays, showing you a list of software that will stop functioning after the Maintenance Pack is removed. Click on Continue.

  6. When the Removal complete window appears, click on OK and exit the Software Manager by selecting Exit from the Host menu.

  7. Insert the SCO OpenServer Release 5.0.7 System CD-ROM into the drive.

  8. Restart the Software Manager, as you did in Step 2.

  9. From the Software menu, select Install New.

  10. When prompted for the host (machine), select the current host and then click on Continue.

  11. Select the appropriate CD-ROM drive as the Media Device, then click on Continue.

  12. In the Install selection window, locate the operating system edition (Enterprise, Desktop, or Host) that you installed and double-click to expand it.

  13. Double-click on these three components under the operating system edition:

    UNIX (This is always the first entry in the list.)
    Connectivity
    Internet Services

  14. Under the UNIX component, double-click on the Core OS component.

  15. Using the <Ctrl> key to select multiple components, click on the following components to select them for installation:

    Under Core OS: 

       Perl 5.8.0
   Perl 5.8.0 Extensions
   Supplemental Graphics, Web, and X11 Libraries
   Apache Web Server
   mod_perl for Apache
   mod_ssl for Apache
   php4 for Apache
   Apache XML Toolkit (AxKit)
   Perl ASP Support for Apache

    Under Connectivity: 

       Secure Shell

    Under Internet Services: 

       Mozilla

    When all of these components are highlighted, click on Install.

  16. When the installation is complete, click on OK.

  17. Exit the Software Manager by selecting the Host menu, then Exit.

  18. Reboot the machine. (Because the Software Manager relinks the kernel, you must reboot before the new kernel takes effect.)

Highlights of the Maintenance Pack

Changes and additions provided by this Maintenance Pack include:

NOTE: Drivers for new hardware have been moved out of the Maintenance Pack and are available on the Supplement CD.

Support for IDE hard disks larger than 137GB

Previously, this feature was part of the Update Packs; it is now included in Maintenance Pack 3.

Maintenance Pack 3 includes a new revision of the wd(HW) driver that supports IDE hard disks larger than 137GB.

NOTE: If you have a new IDE hard disk that is larger than 137GB that you want to add to your system, you should do so after you have installed the Maintenance Pack and the new wd driver. If you want to use the disk as your root drive, you need to load the new driver at boot time (using the link(HW) bootstring) before beginning the installation.

If your system currently uses an IDE drive larger than 137GB, the new wd driver makes it possible to use the full capacity of the disk. To use the entire disk, however, you must manually reconfigure the drive to recreate the existing disk partitions or to create new ones. The wd driver readme explains this process in detail.

Instructions for installing the wd driver are provided on the SCO web site at:

http://www.sco.com/support/update/download/wddrvr.html

or the SCO OpenServer Release 5.0.7 Supplement CD Version 3. We strongly recommend that you review these instructions before using the new features of the driver.

CD writer support: cdrtools

The cdrtools package (ver 2.01a27) is now included and officially supported in SCO OpenServer Release 5.0.7. It is a set of programs for creating CD images (mkisofs) and writing data to recordable/rewritable CDs (cdrecord).

NOTE: cdrecord(1) supports many options and formats that are beyond the scope of basic file archiving. This section documents the most common tasks for creating data CDs and includes information specific to SCO OpenServer Release 5.0.7.

Tested hardware

The following drives have been tested on SCO OpenServer Release 5.0.7:

Matsushita CW-7502
Philips CDD-2600
Plextor PX-R412Ci
Plextor PX-R820Ti
Plextor PX-W2412TA
Plextor PX-W4824TA
Ricoh MP6200S
Teac CD-R50S
Teac CD-R55S
Teac CD-R56S
Teac CD-R58S
YAMAHA CDRW4416S
YAMAHA CRW2260

Most MMC-compliant CD writers should work.

Configuration

If you have not already used the CD drive to install SCO OpenServer Release 5.0.7, you need to manually configure the drive with the mkdev cdrom command.

Listing available devices

To display a list of CD devices on the system, use the -scanbus option of the cdrecord(1) command:

cdrecord -scanbus

A list of devices similar to this is displayed (SCSI addresses are shown regardless of the controller type): 

   scsibus0:
         0,0,0   0) 'ATAPI '  'CD-RW 52X24X ' 'MB51' Removable CD-ROM
         0,1,0   1) *
         0,2,0   2) *
         0,3,0   3) *
         0,4,0   4) *
         0,5,0   5) *
         0,6,0   6) *
         0,7,0   7) *
In this case an ATAPI CD writer is the first device on an IDE controller (address 0,0,0).

cdrecord default file (/etc/default/cdrecord)

This file contains the default device settings for cdrecord. First are the device, speed, and buffer settings (note that the latter two are commented out): 

   CDR_DEVICE=ide
   #CDR_SPEED=40
   #CDR_FIFOSIZE=4m
The CDR_DEVICE setting is actually an index into a table with a series of drive-specific defaults: 
   # drive name    device  speed   fifosize driveropts
   #
   teac=           1,3,0   -1      -1      ""
   panasonic=      1,4,0   -1      -1      ""
   plextor=        1,4,0   -1      -1      ""
   sanyo=          1,4,0   -1      -1      burnfree
   yamaha=         1,5,0   -1      -1      ""
   ide=            0,0,0   -1      -1      burnfree
   cdrom=          0,6,0   2       1m      ""
The default entry is ide (as defined by CDR_DEVICE). Because a generic SCSI driver is used for all CD drives, the SCSI address scheme (host adapter, device, LUN) is used even with IDE controllers. At the same time, this scheme only applies to IDE controllers with CD drives (that is, the numbering of host adapters is not absolute.) For example, on a system with no SCSI adapters and two IDE controllers, the controller with the CD drive attached is host adapter 0 (even if it happens to be the secondary IDE controller).

NOTE: On the command line, the LUN (0) can be omitted (as it is in the examples discussed here).

Note the default addresses for other drives are not realistic; be sure and change the device address in second column to match the actual drive settings. The other columns (speed, buffer size, and driver options) can be set as desired. A value of -1 indicates that the device uses its own default value. The quotes in the column indicate an empty option list; burnfree allocates a larger buffer for write operations (if supported by the drive). Other options are documented in cdrecord(1).

Creating a data disc

Before using cdrecord to make a data disc you must first create an ISO image with mkisofs. This sample command creates an ISO9660 image of the working directory (.) with Joliet (-J) and RockRidge (-r) directory entries and stores it in the file /tmp/cdimg.iso:

mkisofs -r -J -o /tmp/cdimg.iso .

To write this image to a disc, you would use a command like this:

cdrecord -v -eject dev=0,0 /tmp/cdimg.iso

The -v is optional and generates verbose output. The dev= argument can also be omitted if the default drive is defined in /etc/default/cdrecord. The -eject option ejects the disc when the process is complete. In addition, cdrecord displays a nine-second countdown to give you an opportunity to abort the command.

You can also perform a test burn using the -dummy option:

cdrecord -v -dummy /tmp/cdimg.iso

The command is executed as specified, but the laser is not activated.

NOTE: The -dummy option may actually damage media on certain older drives (rendering them unusable).

If the system is relatively idle (with little or no disk activity), it is possible to skip creating the image and pipe the output of mkisofs directly to cdrecord:

mkisofs -r /usr/home/cforbin | cdrecord -

In this example, the contents of /usr/home/cforbin is written to the disc (the - argument takes data from the standard input).

WARNING: On active systems you should create an ISO image for best results.

Mounting a disc

You can mount and unmount a disc from the desktop using the MountCD icon, or from the command line as in these examples using /mnt as a mount point:

mount -r /dev/cd0 /mnt
umount /mnt

Media support

cdrecord supports the following drive types/media:

Media Type Read-Write Behavior
CD-R Existing data cannot be erased or overwritten
  Additional sessions can be appended
CD-RW Entire disc can be erased/blanked
  Explicit erasing/blanking required before rewrite
  Additional sessions can be appended

Multisession support

To create multisession disks, you must use the -multi option to leave the CD open (un-fixated) for writing additional sessions:

cdrecord -multi image.iso

To finalize a CD (making it non-writable), simply omit the -multi option.

Writing a new session on a CD normally hides the previous session from view (requiring an application that allows you to select the active session). However, it is possible to import the TOC (table of contents) from the previous session and make the previously-written data available in the ISO image for the new session.

In this example, mkisofs uses the -C option to execute the cdrecord -msinfo command on the specified drive (-M 0,0) to read the location of the previous session and uses the response to create the ISO image:

mkisofs -r -J -C `cdrecord -msinfo` -M 0,0 -o image.iso /usr/home/colossus

When cdrecord is used to write the image to CD, all the previous data will be accessible along with the new files (in this example, from /usr/home/colossus).

Multisession support: mount(ADM)

The mount(ADM) command now includes options to mount CD filesystems by session or sector. See the mount(ADM) manual page for details.

By default, the mount(ADM) command mounts the last session. To override the default and mount the first session, use the syntax in this example:

mount -o session=1 /dev/cd0 /mnt

At this time, only the first and last sessions can be mounted by session number. However, the sector option can be used to mount an arbitrary session by the starting sector number. On newer drives, you can use the -toc option of the cdrecord(1) command to obtain the starting sector:

cdrecord -toc

For a multi-session CD, the output looks something like this: 

   track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 4 mode: 1
   track:   2 lba:     20235 (    80940) 04:31:60 adr: 1 control: 4 mode: 1
   track:   3 lba:     39262 (   157048) 08:45:37 adr: 1 control: 4 mode: 1
   track:lout lba:     53507 (   214028) 11:55:32 adr: 1 control: 4 mode: -1
You can use the lba output to mount the desired sector. In this example, the command mounts session 2, which starts at sector 20235:

mount -o sector=20235 /dev/cd0 /mnt

NOTE: If you used cdrecord(1) when it was provided on the Skunkware CD (and multisession CD read support was not present in SCO OpenServer Release 5.0.7), note that the the last session is now mounted by default. Multisession CDs typically include files from previous sessions by reference, so this should yield a better view of the contents of the disc.

Additions to Internet Services: Tomcat and JK

Maintenance Pack 3 includes the following additions to Internet Services:

Consult the DocView Internet Services page for documentation links relating to these packages.

Tomcat notes

The following sections include additional information about Tomcat.

Enabling Tomcat

After installing Tomcat, you must enable it manually. To enable and start Tomcat, run these commands:

/etc/init.d/tomcat enable

When enabled, Tomcat also automatically restarts each time the system is rebooted.

Tomcat web application

After startup, the default web applications included with Tomcat are available by browsing:

http://localhost:8080/

The administrator application is available directly at:

http://localhost:8080/admin/login.jsp

The logins for the admin and other roles must be set up as described in the next section.

Using the Tomcat admin and manager logins

By default the admin and manager web logins are not enabled. To add these logins, do the following:

  1. Edit the configuration file /usr/lib/apache/tomcat/conf/tomcat-users.xml. The contents are similar to the following: 
       <tomcat-users>
     <user name="tomcat" password="tomcat" roles="tomcat" />
     <user name="role1"  password="tomcat" roles="role1"  />
     <user name="both"   password="tomcat" roles="tomcat,role1" />
   </tomcat-users>

  2. You can change these entries to include the desired web login, password, and the role to which you want them assigned. (Do not confuse these "web" logins that are used to access the administrative web application with operating system system logins.) The admin and manager roles/logins allow someone with the proper password to run the admin and manager web applications. For example, the following entries create admin and manager web logins with tomcat as the password: 
         <role rolename="admin"/>
     <role rolename="manager"/>
     <user username="admin" password="tomcat" roles="admin"/>
     <user username="manager" password="tomcat" roles="manager"/>

  3. After making changes or additions, you must restart Tomcat:

    /etc/init.d/tomcat restart

Tomcat web application Java exception error

If you log into the Tomcat Application Manager, stop an Application, restart it, then proceed to the application path and then use the Back button to return to the Tomcat Web Application Manager, the following error may be displayed in the Messages box of the Tomcat Application Manager: 

   FAIL - Application at context path /tomcat-docs could not be started
   FAIL - Encountered exceptionjava.lang.IllegalStateException:
   standardHost.start /tomcat-docs: LifecycleException:  Container
   StandardContext[/tomcat-docs] has already been started
This is not a fatal error and is not unique to SCO OpenServer Release 5.0.7 systems. The workaround is to use reload instead of stop or start.

X.Org runtime libraries

The X.Org X11 Release 6.7 runtime libraries, header files, and core fonts are now included and supported by SCO in SCO OpenServer Release 5.0.7. The man pages for the X.Org routines are also installed on the system, but are not included in the MANPATH environment variable. (This is done to avoid collision with the existing X11R5 man pages.) If you wish to access the X.Org man pages in preference to X11R5, insert /usr/X11R6/man into your MANPATH variable (or the system-wide setting in /etc/default/man) before the /usr/man entry, as in this example: 

   MANPATH=scohelp:/usr/X11R6/man:/usr/man:/usr/gnu/man:/usr/local/man
If you add the X11R6 path to /etc/default/man, you should also update the man page database by executing the following command as root:

/usr/man/bin/makewhatis /usr/X11R6/man/*

Updates to Mozilla web browser and new plugins

Maintenance Pack 3 includes Mozilla 1.6 and the following new plugins:


Plugger 5.0
supports the display of media files within the browser. You must install a player that supports the desired media; these are available in the Skunkware package on the SCO website.

Xpdf 3.0
plugin that allows PDF files to be displayed inside the browser.
In addition, Mozilla 1.6 is pre-configured to work with the Java Plugin provided on the SCO OpenServer Release 5.0.7 Supplement CD Version 3.

Mozilla and the XSENDER command

This release of Mozilla is configured to disable mail authentication via the XSENDER command. If your POP server supports the XSENDER command and you wish to enable this feature, either edit the system-wide preferences in /usr/lib/mozilla-1.6/defaults/pref/mailnews.js and set the auth_login preferences to true, or add such entries to your individual Mozilla preferences as described at the following URL:

http://www.mozilla.org/unix/customizing.html#prefs

Updates to UDK compatibility libraries

Maintenance Pack 3 includes an update to 8.0.2 of the UDK compatibility libraries, which contains numerous fixes to the runtime libraries and provides support for user-level threads for UDK applications.

Updates to the Supplemental Graphics, Web, and X11 Libraries

The following changes are included with Maintenance Pack 3 in the Supplemental Graphics, Web, and X11 Libraries:

The following changes were included with Maintenance Pack 1 in the Supplemental Graphics, Web, and X11 Libraries (previously SLS OSS631B):

Updates to Perl

The following changes are included with Maintenance Pack 3 in the Perl 5.8.4 component:

The following changes were included with Maintenance Pack 1 in the Perl 5.8.0 component:

Updates to OpenSSH

Maintenance Pack 3 features OpenSSH 3.8p1, which includes the following fixes made by the maintainers of this package:

NOTE: When using ssh(1), the contents of the /etc/motd file are displayed twice at login. To prevent this from occurring, edit the /etc/ssh/sshd_config and change the #PrintMotd yes entry to remove the comment symbol (#) so that it reads as follows: 
   PrintMotd No
The /etc/ssh/sshd_config.default file installed with MP3 includes this corrected entry; if you have not customized sshd_config, you can simply copy this file to overwrite the old version.

Updates to the Apache Web Server

The following changes are included with Maintenance Pack 3 in the Apache Web Server component:

The following changes were included with Maintenance Pack 1 in the Apache Web Server component:

Updates to MMDF

The following sections detail various updates and fixes made to MMDF.

Security fixes

Various buffer overflows, null dereferences, and core dumps that affect all MMDF binaries have been corrected. All but one of the MMDF binaries that were setuid root are no longer (they have been improved to make this unnecessary), reducing the potential for further exploitation. The local channel delivery program is still setuid root because it must deliver mail into users' mailboxes and run processes with users' UIDs.

Improvements to mmdftailor(F)

Three new MMDF general configuration parameters can be set in /usr/mmdf/mmdftailor: ORPHANAGE, DEADLETTER, and TAGCHARS. See mmdftailor(F) for more information.

Improvements to submit(ADM)

Several changes have been made to submit(ADM):

Improvements to the local delivery channel: maildelivery(F)

The following changes have been made to maildelivery(F):

Improvements to the smtp channel

The following changes have been made to the smtp channel and are documented in the newly added smtp(ADM) and smtpd(ADM) manual pages:

Improvements to the badusers channel

The badusers channel is intended to map usernames on the local host to the same usernames on a different host. It intentionally strips the hostname from the recipient address when it does this mapping so that the destination host will treat the recipients as local users. However, it is now common for mail systems to be configured to refuse to accept a recipient address that contains only a user name. If the badusers channel is used to forward mail to a host that is not under the control of the same administrator (for example, a host that is doing virtual mail hosting), this may present a problem. To resolve this, the badusers channel has two new confstr parameters, keepdomain and defdomain. Refer to submit(ADM) for more information.

Improvements to the uucp channel: rmail(ADM)

rmail(ADM) is now executable by group uucp, and not other, to prevent the authority of the UUCP system to inject messages with any sender name from being used by local users. It is possible that some extremely old software expects to be able to use rmail to inject messages locally. If this is the case, change the mode of /usr/bin/rmail to allow others to execute it:

chmod o+x /usr/bin/rmail

Improvements to cleanque(ADM)

cleanque(ADM) no longer sends warnings about messages that were queued with the no-return flag. cleanque also has a new command line option (-t) that displays the actions it would take on queued messages without actually doing anything.

List of problems fixed

SCO OpenServer Release 5.0.7 Maintenance Pack 3 contains the following bug fixes:

Maintenance Pack 1 included the following bug fixes:

Maintenance Pack notes and limitations

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

Footnotes

Copyright © 2004 The SCO Group, Inc. All rights reserved. Date: June 2004
© 2004 The SCO Group, Inc. All rights reserved.