SCO OpenServer Release 5.0.7 Maintenance Pack 4 Release and Installation Notes

SCO OpenServer Release 5.0.7 Maintenance Pack 4 Release and Installation Notes

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

NOTE: Maintenance Pack 4 is the third in the series of Maintenance Packs provided for SCO OpenServer Release 5.0.7. Because the previous Maintenance Pack was coordinated with the release of Update Pack 3, there was 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 4. 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

Historically, there were two support ``tracks'' that were 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.

With the release of Maintenance Pack 4, the SCO OpenServer Release 5.0.7 Update Pack track is discontinued and new licenses are no longer available. All of the functionality from Update Pack 3 is now available in Maintenance Pack 4.

Obtaining Maintenance Packs

SCO OpenServer Maintenance Pack 4 is available for download from the SCO OpenServer Release 5.0.7 Supplements web page:

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

Additionally, SCO OpenServer Maintenance Pack 4 is included on the SCO OpenServer Release 5.0.7 Supplement CD Version 4. The SCO OpenServer Release 5.0.7 Supplement CD also provides other new and updated components, including Java, Samba, Squid, and updated graphics, NIC, and HBA drivers. Your SCO OpenServer media kit may contain Version 4 of the Supplement CD; if not, you can download the ISO image for this CD from the SCO OpenServer Release 5.0.7 Supplements web page.

Before installing the Maintenance Pack from the Supplement CD, check the SCO OpenServer Release 5.0.7 Supplements web page 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 4, 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 4:

If there are multiple systems on your TCP/IP network that require Maintenance Pack 4, 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 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 a previous Maintenance Pack was never installed on your system, SCO Update will not be available from within the Software Manager until after you install MP4.

NOTE: You will not be able to use the SCO Update feature if you are behind a firewall that prevents incoming FTP connections (i.e., the use of passive FTP is required). If you try to connect to the SCO Update server in this situation, the Software Manager displays the following timeout message after a few minutes: 
   Unable to initialize device

A fix for this problem will be made available in a future supplement or release.

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 maintenance packs, drivers, and so forth that are currently available.

  4. Highlight Maintenance Pack 4 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 now by clicking on Cancel, 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 4 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 4 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. Because all 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.

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

    tar xvf osr507mp4_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 4 media images. For example:

    /usr/spool/patches/osr507mp4

    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 RS507C Release Supplement) must be installed. New features 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 now by clicking on Cancel, 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 4 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

The SCO OpenServer Release 5.0.7 Maintenance Pack 4 is included on the SCO OpenServer Release 5.0.7 Supplement CD Version 4. Your SCO OpenServer media kit may contain Version 4 of the Supplement CD; if not, you can download the ISO image for this CD from the SCO OpenServer Release 5.0.7 Supplements web page.

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

  1. Log in as root.

  2. Insert the SCO OpenServer Release 5.0.7 Supplement CD Version 4 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 RS507C Release Supplement) must be installed. New features 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 now by clicking on Cancel, 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 4 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 4 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 4 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 4 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 4 de-installs the Apache, Mozilla, OpenSSH, Perl, and Supplemental Graphics, Web, and X11 Libraries (GWXLIBS) 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 re-install the previous versions of Apache, Mozilla, OpenSSH, Perl, and Supplemental Graphics, Web, and GWXLIBS. This section explains how to do this.

To remove the Maintenance Pack and reinstall your previous versions of the Apache, Mozilla, OpenSSH, Perl, and GWXLIBS 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. Now re-install Apache, Mozilla, OpenSSH, Perl, and GWXLIBS.

    It is important that you replace these components with the versions that you were running prior to installing Maintenance Pack 4. If your system contains Maintenance Pack 3, use that media. If Maintenance Pack 4 was the first maintenance pack installed on your system, use the SCO OpenServer Release 5.0.7 System CD-ROM.

  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. Depending on the media you are using, the list displayed in the Install selection window will be different. Double-click on the appropriate software -- maintenance pack or operating system edition.

    From the expanded list, select to install the Apache, Mozilla, Secure Shell (OpenSSH), Perl, and Supplemental Graphics, Web, and X11 Libraries components. You can use the <Ctrl> key to select multiple components for installation. When all of these components are highlighted, click on Install.

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

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

  15. 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 Packs and are now available on the Supplement CD.

Support for IDE hard disks larger than 137GB

Previously, this feature was provided in Maintenance Pack 3 and, before that, in the Update Packs.

Maintenance Pack 4 includes a version 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 4. We strongly recommend that you review these instructions before using the new features of the driver.

Hyper-Threading Technology and multi-core support

Hyper-Threading (HT) Technology was previously part of the Update Packs; it is now included in Maintenance Pack 4. Hyper-Threading allows two series of instructions to run simultaneously and independently on a single Intel® HT-enabled processor. With Hyper-Threading Technology enabled, the system treats a physical processor as two ``logical'' processors. Each logical processor is allocated a thread on which to work, as well as a share of execution resources such as cache memories, execution units, and buses.

Hyper-Threading Technology can be used on an SCO OpenServer Release 5.0.7 system that is equipped with the following:

NOTE: By default, Hyper-Threading support is disabled when Maintenance Pack 4 is installed. The Hyper-Threading support provided in Update Pack 3 was enabled by default. To enable Hyper-Threading support after Maintenance Pack 4 is installed, see the hyperthread(HW) manual page.

Multi-core support is new in Maintenance Pack 4. A multi-core processor is a single physical processor that includes two or more ``cores'' and one or more logical processors per core. Each core acts as a discrete processor, complete with its own set of execution resources. A dual-core processor includes two cores, with one logical processor per core. A dual-core processor that also includes Hyper-Threading Technology provides two cores and two logical processors per core, allowing the execution of four simultaneous threads.

Maintenance Pack 4 provides support for Intel Xeon and Intel Pentium 4 multi-core processors. SCO OpenServer's multi-core support also requires a chipset and a system BIOS that support HT Technology.

NOTE: Hyper-Threading Technology and multi-core processor support for SCO OpenServer is provided by the SCO OpenServer Release 5.0.7 Symmetrical Multiprocessing (SMP) product. If you want Hyper-Threading Technology or multi-core support, the SMP product must be installed before Maintenance Pack 4.

An SMP license is not required to install SMP on a single-CPU system; simply select to Defer licensing during the installation.

For more details on Hyper-Threading and multi-core support in SCO OpenServer Release 5.0.7, see the hyperthread(HW) manual page.

CD writer support: cdrtools

First provided in Maintenance Pack 3.

Maintenance Pack 4 updates the cdrtools package to version 2.01.01a01. This package is a set of programs for creating CD images (mkisofs) and writing data to recordable/rewritable CDs (cdrecord).

cdrecord(1) 2.01 has been updated to check the CD recorders DMA (Direct Memory Access) speed and adjust the default burn rate accordingly. However, SCO OpenServer Release 5.0.7 does not currently support DMA mode for ATAPI devices; only PIO mode is used. Consequently, you may see a message similar to: 

   cdrecord: DMA speed to slow (OK for 16x),  Cannot write at speed 24x.

This message is misleading in that there is not any performance degradation between this version of cdrecord and the version provided with Update Pack 3. CD recording continues to run in PIO mode -- a recording at 24x takes the same amount of time to complete as a recording at 16x speed.

ATAPI DMA support is planned for a future maintenance pack release.

cdrecord(1), a port of the ProDVD utility, supports many options and formats that are beyond the scope of basic file archiving. The following sections document the most common tasks for creating data CDs and include 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)

First provided in Maintenance Pack 3.

The mount(ADM) command 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.

DVD writing with dvdrecord

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

Maintenance Pack 4 includes DVD writing support with the dvdrecord(C) command, a port of the ProDVD utility.

Because the industry standard for writing DVDs is SAO (DAO) mode, this is now the only mode supported by dvdrecord. The previously supported TAO and RAW modes are no longer available for writing DVDs.

NOTE: If you have not already used the DVD drive to install SCO OpenServer Release 5.0.7, you need to manually configure the drive with the mkdev cdrom command (which also supports DVD drives).

The command options for dvdrecord are the same as those for cdrecord (see ``CD writer support: cdrtools''). The dvdrecord(C) manual page is provided (and is maintained) by SCO. It contains basic information on creating DVD and CD data discs and includes key examples. The cdrecord(1) manual page is the generic documentation provided with the free software and is not specific to SCO UNIX operating systems. Refer to cdrecord(1) for the complete option set and information on creating specialized disc layouts and formats.

DVD writers tested

dvdrecord has been reported to work with most DVD drives. The following drives have been tested on SCO OpenServer Release 5.0.7:

Updates to the Supplemental Graphics, Web, and X11 Libraries

First provided in Maintenance Pack 1.

Maintenance Pack 4 includes the following changes in the Supplemental Graphics, Web, and X11 Libraries (GWXLIBS):

X.Org X11 runtime libraries

First provided in Maintenance Pack 3.

Maintenance Pack 4 updates the X.Org X11 runtime libraries, header files, and core fonts to Release 6.8.2. Note that these libraries are now part of the Supplemental Graphics, Web, and X11 Libraries and no longer a separate package.

The manual 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 manual pages instead of those for the X11R5 server, 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 Perl

The Perl component in Maintenance Pack 4 has been updated to version 5.8.7. This updated version includes a vast number of upgraded Perl modules. Additionally, this version of Perl has been recompiled to take advantage of the updated GWXLIBS component.

Updates to OpenSSH

OpenSSH is updated to version 4.2p1 in Maintenance Pack 4.

In this new version, long passwords (longer than eight characters) are now supported. Previously, only the first eight characters of a password were recognized.

Note that if your SCO OpenServer system was installed with either the Low or Traditional security profiles, you need to activate the OpenSSH long password support. To do this, run the following command:

# usermod -D -x "{passwdSignificantSegments 2}" <username>

Updates to the Apache Web Server

Maintenance Pack 4 includes the following changes to the Apache Web Server component:

Additions to Internet Services: Tomcat and JK

First provided in Maintenance Pack 3.

The following Internet Services are included in Maintenance Pack 4:

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.

Updates to Mozilla web browser and plugins

First provided in Maintenance Pack 3.

Maintenance Pack 4 updates the Mozilla web browser to version 1.7.12.

MozPlugger 1.7.3 replaces the Plugger 5.0 plugin that was provided in Maintenance Pack 3. MozPlugger is a general purpose multimedia plugin for Mozilla that supports the display of media files within the browser.

MozPlugger is configured to use xpdf 3.0.1 (also provided in Maintenance Pack 4) to display PDF documents in Mozilla. Additionally, Mozilla is pre-configured to work with the Java plugin provided on the SCO OpenServer Release 5.0.7 Supplement CD Version 4.

The SCO OpenServer Release 5.0.7 Skunkware Download area contains many packages providing multimedia support that can be configured in MozPlugger.

Mozilla and the XSENDER command

This release of Mozilla is configured to enable mail authentication via the XSENDER command. If your POP server does not support the XSENDER command and you wish to disable this feature, either edit the system-wide preferences in /usr/lib/mozilla-1.7.12/defaults/pref/mailnews.js and set the auth_login preferences to ``false'', 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 MMDF

First provided in Maintenance Pack 3.

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.

CUPS printer subsystem

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

Maintenance Pack 4 includes version 1.1.23 of the Common UNIX Printing System (CUPS). When installed, both the CUPS and standard (SYSV) print systems are active. Although both systems use the same command names, the options and behavior differ somewhat (each print system has a separate set of commands stored in /usr/lib/lp/cups and /usr/lib/lp/sysv):

accept cancel disable enable lp lpadmin lpmove lpr lpstat reject

Both command sets are supported. To make it easier to use the commands, you can define the default command set (SYSV or CUPS) to be used when a print command (such as lpstat) is entered on the command line. This can be done in any of three ways:

When the pathname is not supplied, the commands from the default print system are executed. You can use the full pathname to run a command belonging to the non-default print system. In a similar way, you can access the manual pages for the two printer systems by supplying the relevant section name in the man(C) command (1 or 8 for CUPS man pages, C or ADM for the SYSV man pages):

Command CUPS SYSV
accept 8 ADM
cancel 1 C
disable 8 C
enable 8 C
lp 1 C
lpadmin 8 ADM
lpmove 8 ADM
lpr 1 C
lpstat 1 C
reject 8 ADM

The CUPS package installs the following online documentation -- the Overview of the Common UNIX Printing System, CUPS User's Manual, Software Administrator's Manual, and CUPS Security Report.

CUPS Administration

The CUPS distribution includes a web-based administrative interface that is configured on port 631 (http://localhost:631).

NOTE: You may have trouble logging in as root to the CUPS web administrative interface if each of the following three conditions are true:

  1. Your system was installed with a Traditional or Low security profile.

  2. You set a root password longer than eight characters during installation.

  3. The root password has not been changed since installation.
In this case, use the passwd(C) command to re-enter the existing root password or change the password to a different value.

A list of available printers is generated at the time the CUPS print daemon (cupsd) is started (when the system enters multiuser mode). To regenerate the list (such as after connecting a new USB printer), enter the command:

/etc/init.d/cups restart

NOTE: Do not change the configuration for a printer (such as dpi) while it is printing. This has been known to corrupt the output of the print job.

CUPS and Remote Printing (LPD)

Although CUPS supports LPD as both a server and a client, the CUPS LPD server implementation does not support access control (based on the settings in the /etc/hosts.equiv and /etc/hosts.lpd files). If your setup requires the use of the standard LPD, or you wish to use access control, do not install CUPS.

WARNING: If you have never run mkdev rlp and you wish to do so, the CUPS package must be removed before running mkdev rlp and then reinstalled after remote printing is configured.

Using CUPS as an LPD client

To configure CUPS so that jobs can be sent to a remote LPD printer, add a printer via the CUPS administrative interface and use the following settings:

Attribute Setting
Device LPD/LPR Host or Printer
Prototype device URI lpd://hostname/printername
Model/driver Raw

NOTE: If the printer was already configured for remote printing, the host and printer name are present in the /etc/printcap file.

Using CUPS as an LPD server

To configure CUPS so that remote hosts can send jobs to the CUPS printing system on the local host using the LPD protocol, follow the instructions found in the ``Printing to LPD Servers'' section of the Software Administrator's Manual in the online CUPS documentation.

WARNING: Because only one service can listen for print requests on the LPD port, mkdev rlp must not be configured on the local host. If mkdev rlp has ever been run on the host, it must be run again either before CUPS (MP4) is installed or with CUPS temporarily removed as described previously. If you intend to use CUPS as an LPD server you should run mkdev rlp to de-configure remote printing before CUPS/MP4 is installed (this is because the CUPS configuration is lost when the package is removed).

CUPS lpstat(1) command

The CUPS lpstat(1) always reports the state of devices as having been last modified on January 1st at 00:00. For example: 

   Obie accepting requests since Jan 01 00:00

This is because the CUPS version of lpstat does not capture this information. The default date is generated so that applications that parse lpstat output will not fail.

CUPS and HP LaserJet 6 Printers (PCL)

There is a known problem with the default printer driver displayed in the CUPS administrative interface for the HP LaserJet Series PCL 6. You should instead select one of these drivers that are reported to work:

GIMP-Print support

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

Maintenance Pack 4 provides the GIMP-Print (4.2.5) printer drivers for use exclusively with the CUPS printing system. GIMP-Print rasterizes bit images for printers that do not have built-in rasterizers (including many of the more inexpensive USB printers on the market).

The GIMP-Print package installs the following online documentation -- the GIMP-Print User's Guide and GIMP-Print, The Print Plugin for the GIMP.

ESP Ghostscript

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

Maintenance Pack 4 includes the 7.07.1 release of ESP Ghostscript. This is installed by default in conjunction with GIMP-Print to provide better printer support with CUPS.

Foomatic printer drivers

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

The foomatic package contains a generic printer filter and PPD (PostScript Printer Definition) files for over 200 non-PostScript printers. The filter and PPD files are integrated with the CUPS package and cannot be used with the System V LP print system. (Note that the CUPS package also provides its own PPD files. For more information, see the Printing topic in the online documentation.)

Further documentation on the printers supported by foomatic is available at:

http://www.linuxprinting.org/printer_list.cgi

You can search this site for the proper driver name for your printer, then look for the driver in the Make/Model selection list displayed by the CUPS graphical interface.

Foomatic is also a standalone system that creates PPD files from an XML database and includes tools for direct printing. The PPD creation program is called foomatic-rip(1) and the database is called foomatic-db.

Note that the Foomatic package provides the following manual pages:

foomatic-configure(1)
foomatic-gswrapper(1)
foomatic-ppd-options(1)
foomatic-ppdfile(1)
foomatic-printjob(1)
foomatic-rip(1)
foomatic-perl-data(1)
foomatic-compiledb(1)
foomatic-combo-xml(1)
foomatic-kitload(8)
foomatic-preferred-driver(8)
foomatic-getpjloptions(8)
foomatic-addpjloptions(8)

Extended shells

Previously, this feature was provided in the Update Packs; it is now included in Maintenance Pack 4.

The latest, stable versions of the GNU Bourne-Again Shell (bash), Z-Shell (zsh), and Extended C-Shell (tcsh) are provided in Maintenance Pack 4. Documentation for each of the shells, including manual pages and texinfo help, is provided when the shells are installed.


GNU Bourne-Again Shell (bash) version 3.0
This popular shell from the GNU Project is a feature-rich shell that is largely IEEE POSIX P1003.2 compliant. It has most features of the Korn Shell (ksh) and is well suited to interactive use. Most existing shell scripts should run correctly with bash.

Z-Shell (zsh) version 4.2
This shell is best suited for interactive usage. It has highly programmable command and filename completion, is most compatible with the Korn Shell (ksh), and has features that C-shell (csh) users will find familiar. It also has a full FTP client that you can access with built-in shell commands, as well as a number of additional loadable modules. You can extend zsh with other third-party modules at any time.

Extended C-Shell (tcsh) version 6.13
This is a Berkeley C-shell (csh) compatible shell with many improvements, bug fixes, and command line editing capabilities. Note that the SCO version of csh behaves differently from other implementations of csh (including tcsh) in implementation of the || and && operators.

Vim text editor

Maintenance Pack 4 now includes Vim, version 6.3. Vim is a highly configurable text editor that is intended to increase text editing efficiency. It is an improved version of the vi(C) editor.

See the vim(1) manual page for more information.

Updates to UDK compatibility libraries

First provided in Maintenance Pack 3.

Maintenance Pack 4 includes version 8.0.2b of the UDK compatibility libraries, which contains several fixes to the runtime libraries, including:

List of problems fixed

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

Maintenance Pack 3 included 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 4:


© 2005 The SCO Group, Inc. All rights reserved.