Update Pack 3 contains all the new features from Update Pack 1 and Update Pack 2, as well as the additional new features listed in this section. See the Update Pack Feature List for a complete list.
Also see the sections Problems Fixed for the maintenance fixes included in the Update Pack, and Known Problems for limitations and workarounds.
The features listed in this section are installed with the Update Pack Set. See the Installation Procedures section for how to install the Update Pack Set.
A new boot(4) parameter has been added that allows newer video cards and chips (such as the nVidia GeForce onboard chip) to work with UnixWare. In these newer cards and chips, EGA environment tables are no longer provided and the video modes must be initialized by the kernel using VESA BIOS calls instead. If the USE_VESA_BIOS boot parameter is set on boot, then the kernel will initialize the video modes using VESA BIOS calls; if it is not set or set to "NO" (the default), then the EGA environment table is used. If you are installing UnixWare 7.1.3 for the first time, this parameter is not yet available at installation time. Install the system using another supported graphics card; then, after the system is installed, you can then edit boot(4) as described above to enable VESA BIOS initialization. See the Compatible Hardware Web Page at http://www.sco.com/chwp for graphics cards that work during a fresh install of UnixWare.
An entry has been added for India Standard Time (IST) to the list of time zones presented in both the SCOadmin International Settings Manager (scoadmin international) and the SCOadmin Time Manager (scoadmin system time). After setting the new time zone, reboot the system and set the current system date and time, if necessary, to the current local date and time using the Time Manager or the date(1) command.
A number of enhancements and fixes have been made to the Licensing subsystem. Most of these are listed in the Problems Fixed section. The following changes in the Licensing subsystem are significant to administrators and users:
The maximum number of simultaneous users, as determined by your current licenses, is now strictly enforced. Each connection (for example, via telnet, rlogin, ssh) counts as a "user", even if the same login is using multiple connections. If the number of allowable users (determined by the installed licenses) is exceeded, additional logins are denied until a current user logs off the system.
The new sco_pmd license policy manager daemon replaces the ifor_pmd, ifor_sld, and sco_cpd daemons from previous releases. See the sco_pmd(1M) manual page for details.
See the Installation and Licensing topic in the online documentation for more information about licensing.
The sendmail(1M) Mail Transfer Agent (MTA) has been updated to version 8.12.9, along with security fixes from version 8.12.10. As a result, the following message will be displayed when sendmail starts:
Warning: .cf file is out of date: sendmail 8.12.9 supports version 10, .cf file is version 9
Mail will still continue to work as before; however, none of the new versions added to sendmail after version 8.9 (including anti-spam filters) will not be implemented in the configuration file, /etc/sendmail/sendmail.cf. For a review of what has changed in sendmail since version 8.10, see .
For more information on using sendmail, see Mail and Messaging in the online documentation, and the Sendmail Web Site at http://www.sendmail.org.
The mkmsgs(1) command has been enhanced to accept message strings that span more than one line in the input file, and to accept message string input longer than 4095 characters. There is now no limit on the size of message string input.
Multi-line messages are encapsulated in the input file with "%<" and "%>" delimiters on a line by themselves, as in the following example:
%< first line of message second line of message ... %>
Only space, tab, and linefeed characters are allowed on the lines with the delimiters.
The security and reliability of the rndc(1M) program and the handling of secret keys used between rndc and DNS/BIND control channels has been improved.
The upper limit on the amount of swap space that can be allocated has been increased from 2GB (2 gigabytes) to 4GB. Use the swap command to increase the current swap space size. See the swap(1M) manual page and the sections Configuring systems for large physical memory and Adding swap space for more information.
USB 2.0 support has been enhanced to include limited support for a single USB printer connected to the system. Rather than delay the release of this important feature in order to undertake the task of certifying a large sample of the wide range of printers currently available, SCO has chosen to speed the availability of this much-requested feature to our customers by certifying a small number of printers for this first release of USB Printing. These printers are listed in the SCO Certified Hardware Web Page (CHWP) at http://www.sco.com/chwp. As we certify new examples we will add them to the CHWP.
As of the publication of this document, the certified list includes:
There is also a set of printers that we know are problematic. This list includes:
In addition, we have some generic guidelines which will enhance your experience if you attempt to attach a printer that is not yet certified.
USB printer support in UnixWare is not designed to replace parallel printer support for existing installations. In fact, we strongly suggest that if you currently have a printer connected to your UnixWare system via the parallel interface you should not move it to a USB interface. It is likely that to do so would result in different printer behavior than you currently experience.
If you want to attach a new printer to your UnixWare system and the printer provides both a parallel interface and a USB interface, we suggest that you use the parallel interface. Our testing suggests that many printers that support both interfaces provide a less than spec-compliant USB interface. Thus, using the parallel interface on these printers usually results in a better experience.
The Common UNIX Print System (see CUPS) is also being released along with USB Printing. We strongly suggest that you use CUPS as the print system when connecting USB printers. One side effect of this suggestion is that CUPS and System V LP cannot both be running at the same time on your UnixWare system. Although installing CUPS does not automatically replace LP as the default print spooler on your system, once you activate the CUPS print spooler the LP print spoller is disabled. In order for printers currently working under LP to work under CUPS, the printers must be manually added to the CUPS configuration. There is no provision to automatically transfer your System V LP printer configuration to your CUPS configuration. Further documentation on CUPS is available in the UnixWare online documentation under Printing (after you install the cupsdoc package) and at http://www.cups.org/documentation.php
CUPS provides a small set of printer drivers (also called PostScript Printer Definition files, or PPD files). If the printer descriptions supplied with CUPS do not meet your needs, we also provide the foomatic package of printer descriptions. Foomatic requires the ESP GhostScript printer drivers provided in the gs package, and supports dozens of printers. We have included all drivers except gimp-print and hpijs. If your printer model is only supported through these drivers (for example, the HP OfficeJet v40), it will not work with CUPS. These drivers will be made available in a future release.
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, and then look for the driver in the Make/Model selection list displayed by the CUPS graphical interface. You can also search for a driver and display the printers it supports. This site rates the quality as well as availability of printer drivers.
The support provided by foomatic for a given printer model also depends upon the cooperation which the Open Source community gets from various printer vendors. Vendors are ranked at http://www.linuxprinting.org/vendors.html. If the vendor for your printer is listed here in the "Useless" category, for example, it may not be possible to obtain an acceptable driver for your printer.
Please note that any fax and scanner capabilities provided by printers are not currently supported, even if the driver supports them.
To configure a USB printer using the active print subsystem from the command line, use the lpadmin(1M) command. Use the scoadmin printer graphical interface to add a USB printer to System V LP, or CUPS. If CUPS is the current print system, scoadmin printer launches the CUPS graphical interface on http://localhost:631. In the online documentation, see the CUPS Quick Start Guide and Adding a USB Printer to LP.
When defining the printer, use the USB device name. When a USB printer is connected to the system and turned on, two device nodes are created automatically for the printer. They can be listed by entering:
ls -tr /dev/usb_prnt* /dev/usblp*
The device node names are defined as follows:
The # appearing in the device name is the order the printer was recognized as attached. If you have only one printer, it will always be at /dev/usb_prnt0 regardless of how it is physically connected. If you have multiple USB printers connected (which is not currently supported), the digits at the end should not be regarded as stable: they will change as, for example, device timing varies and configuration changes are made.
Please Note: Only device names of the form /dev/usb_prnt# should be used in the scoadmin printer LP manager. See the procedures referenced above for how to add printers to LP and CUPS.
The first five digit number is the location of the host controller interface (HCI) to which the printer 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/usblp-00072-1.4.2
The above device name indicates that the HCI is located at PCI bus number 00, PCI device 07, PCI function 2. Note that this number is completely determined by the hardware vendor's PCI configuration.
The remainder of the device name after the second dash 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 printer is physically connected. Up to five hubs can be connected between the printer 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.
For example, if a USB printer were connected directly to the first USB port on the system, the device name might look like this:
/dev/usblp-00072-1
A device name like /dev/usblp-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 Printer
...
where Hub#1 is connected into the system's first USB port, a second hub is plugged into Hub#1 Port 4, and the USB Printer is plugged into Hub#2 Port 2. This device name is completely unique and will not change as long as the physical configuration of the USB devices is not changed.
See the documentation for LP and CUPS (if installed) under the Printing topic in DocView for more information on printer management.
The UNIX95 version of the Korn shell, /u95/bin/ksh, has been updated to fix a number of problems:
The features listed in this section are contained in separate packages from the Update Pack Set. To install them, either select them from the Upgrade Wizard when you install the Update Pack Set, or follow the instructions in the section Installing Additional Packages after the Update Pack Set.
The gs package includes version 7.05.6 of the GhostScript PostScript and PDF file interpreter, used to display, convert, and print PostScript and PDF (Portable Document Format) files. The documentation accompanying GhostScript is installed with the gs package. See the gs(1) manual page and the Desktops topic in the online documentation.
The ide host bus adapter (HBA) driver has been updated to include a number of bug fixes, as well as the following new features:
Compliance with the ATA/ATAPI-6 standard (see http://www.t13.org).
Supported IDE hard disk capacity has increased from 128GB (gigabytes) to just below 1TB (terabyte), a total of 1,099,510,579,200 bytes (1 terabyte minus 1 megabyte). Full 48-bit addressing in the driver allows support for IDE hard disks up to 1PB (1 petabyte; 1,125,899,906,842,624 or 2^50 bytes) in size; however, the 32-bit addressing used by the kernel limits IDE hard disk support on UnixWare to just below 1TB (a terabyte is 2^40 bytes).
The ide driver is available as a separate package image in the Update Pack, as well as a floppy disk image suitable for use during a fresh install of UnixWare. The floppy image is available at: ftp://ftp.sco.com/pub/unixware7/drivers/storage.
The Broadcom bcme network card driver has been updated to version 6.0.16. This version fixes known kernel panics in the previous driver, which occurred when calling bcopy to copy a transmit buffer. The driver code has also been improved for better transmit performance. The updated driver is included in the nd package. For a list of network cards supported by the bcme driver, please see the Update Pack 2 Notes.
The Intel e1008g PRO/1000 networking card driver has been updated to version 7.2.15. This version includes new adapter support, fixes a panic when transmitted packets are excessively fragmented, fixes PHY initialization problems, and fixes problems that caused the driver to return inaccurate speed information. The updated e1008g driver is included in the nd package, and now supports the following Intel network cards:
700262-xxx PRO/1000 Gigabit Server Adapter PWLA8490
717037-xxx PRO/1000 Gigabit Server Adapter PWLA8490
713783-xxx PRO/1000 Gigabit Server Adapter PWLA8490G1
A38888-xxx PRO/1000 F Server Adapter PWLA8490SX
738640-xxx, PRO/1000 F Server Adapter PWLA8490-SX
A06512-xxx PRO/1000 Gigabit Adapter PWLA8490SXG1P20
A19845-xxx PRO/1000 T Server Adapter PWLA8490T
A33948-xxx PRO/1000 T Server Adapter PWLA8490TG1P20
A51580-014 PRO/1000 XT Server Adapter PWLA8490XT
A73668-001 PRO/1000 XT Server Adapter PWLA8490XTL
A68178-xxx PRO/1000 XT Lo Profile PCI Server Adapter PWLA8490XTL
A50484-xxx PRO/1000 XF Server Adapter PWLA8490XF
739456-xxx IBM Netfinity Gigabit Ethernet SX Adapter 09N3599
721352-xxx IBM Netfinity Gigabit Ethernet SX Adapter 30L7076
A34085-xxx IBM Gigabit Ethernet SX Server Adapter 06P3718
A36407-xxx IBM Gigabit Ethernet Server Adapter 22P4618
A78408-xxx PRO/1000 MT Desktop Adapter PWLA8390MT
PRO/1000 MT Low Profile Desktop PWLA8390MTBK20
A92165-xxx PRO/1000 MT Server Adapter PWLA8490MT
A92111-xxx PRO/1000 MT Dual Port Server Adapter PWLA8492MT
A91622-xxx PRO/1000 MF Server Adapter PWLA8490MF
A91624-xxx PRO/1000 MF Server Adapter (LX) PWLA8490LX
A91620-xxx PRO/1000 MF Dual Port Server Adapter PWLA8492MF
PRO/1000 MT Mobile Connection
A81081-xxx PRO/1000 MT Server Adapter PWLA8490MT
A65396-xxx PRO/1000 MT Dual Port Server Adapter PWLA8492MT
PRO/1000 MT Quad Port Server Adapter PWLA8494MT
A81983-xxx PRO/1000 MF Server Adapter PWLA8490MF
A78709-xxx PRO/1000 MF Dual Port Server Adapter PWLA8492MF
PRO/1000 CT Network Connection
PRO/1000 CT Mobile Connection
PRO/1000 MB Server Connection
PRO/1000 MB Dual Port Network Connection
82544GC Based Network Connection
HP NC6132 Gigabit Module
HP NC6133 Gigabit Module
HP NC6134 Gigabit NIC
HP NC6136 Gigabit Server Adapter
HP NC6170 Dual PCI-X 1000-SX Server Adapter
HP NC7131 Gigabit Server Adapter
HP NC7132 Gigabit Upgrade Module
HP NC7170 Dual PCI-X 1000-T Server Adapter
Updated manual pages and online guides are provided by the baseman and basedoc packages, as well as some of the other packages included with the Update Pack (e.g., cupsdoc, openssld, jpeg, tiff, libpng). Both guides and manual pages can be viewed using any browser via the DocView Documentation Server. By default, DocView can be reached at http://hostname:8458, where hostname is the network node name of the UnixWare system, or localhost when using a browser on your UnixWare 7 system. The browser can be running on native UnixWare, on the Linux Kernel Personality (LKP), or on the OpenServer Kernel Personality (OKP). The manual pages can also be viewed using the man(1) command; this must be done from a UnixWare shell. (The man commands under LKP and OKP display the manual pages installed in those environments, not the UnixWare 7 pages.)
Note that none of the Update Pack documentation packages rebuild DocView's Search index, so any documentation added will not be searchable using DocView's Search button until indexing is run. This is done, by default, at 3:10AM local time by a root crontab(1) entry. If this time is not appropriate for your site, you can edit the crontab entry to change the time indexing is run. In general, it is a good idea to run indexing when the system load is low, since indexing can consume considerable time and system resources, depending on the amount of text being indexed. Alternately, you can run indexing manually using the /usr/lib/docview/conf/rundig command after you finish installing documentation from the Update Pack.
Version 1.1.19 of the Common UNIX Printing System (CUPS) is available in three separate packages:
| cups | Client and Server Software for CUPS |
| cupsdev | CUPS Development Libraries |
| cupsdoc | CUPS Online Guides and Manual Pages |
The current CUPS implementation supports all the documented features of CUPS, with the following exceptions:
CUPS also supports USB printing (see Printing: USB Support). We strongly suggest that you use CUPS as the print system when connecting USB printers. One side effect of this suggestion is that CUPS and System V LP cannot both be running at the same time on your UnixWare system. Although installing CUPS does not automatically replace LP as the default print spoller on your system, once you activate the CUPS print spooler the LP print spoller is disabled. In order for printers currently working under LP to work under CUPS, the printers must be manually added to the CUPS configuration. There is no provision to automatically transfer your System V LP printer configuration to your CUPS configuration. Further documentation on CUPS is available in the UnixWare online documentation under Printing (after you install the cupsdoc package) and at http://www.cups.org/documentation.php
If the printer descriptions supplied with CUPS do not meet your needs, we are also providing the foomatic package of printer descriptions. Foomatic requires the ESP GhostScript printer drivers provided in the gs package, and supports dozens of printers.
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, and then look for the driver in the Make/Model selection list displayed by the CUPS graphical interface. You can also search for a driver and display the printers it supports. This site rates the quality as well as availability of printer drivers.
The support provided by foomatic for a given printer model also depends upon the cooperation which the Open Source community gets from various printer vendors. Vendors are ranked at http://www.linuxprinting.org/vendors.html. If the vendor for your printer is listed here in the "Useless" category, for example, it may not be possible to obtain an acceptable driver for your printer.
You must install the Update Pack Set before you install cups, or CUPS will not work properly. The following packages are required by CUPS to provide the indicated functionality; they can be installed either before or after cups:
| foomatic | printer filters and PPD files |
| libpng | printing PNG image files |
| jpeg | printing JPEG image Files |
| gs | printing PostScript files |
| openslp | remote printer management |
| openssl | remote printer management |
| perl | support for Perl scripts used by CUPS |
| tiff | printing TIFF image files |
| zlib | decompressing image files |
After you install cups, the System V LP System is still the default printing subsystem. Use the chprnsys(1M) command to switch between the System V LP and CUPS printing Systems, as in this example:
# chprnsys cups
The chprnsys command, among other things, reconfigures the system manual pages so that the pages appropriate to the currently active print subsystem are displayed by the man command and by DocView. The online CUPS guides can be viewed under the Printing topic in DocView, when CUPS is the active print subsystem. (Note that you must install cupsdoc to get all the CUPS manual pages and guides.)
CUPS can be administered using command line tools (see Printing for a list), or using the CUPS graphical interface on http://localhost:631. The scoadmin printer graphics interface will launch the administrative interface for the currently active print system. To get started, see the CUPS Quick Start Guide in the on line documentation.
Please Note: If you have a USB printer, connect it to your system and turn it on before you enable CUPS. If you connect a USB printer after you enable CUPS, restart CUPS by entering:/etc/init.d/cups restart
Once you install cups, the Update Pack installation is locked, until you remove the cups package. This is necessary to preserve the integrity of system software. See the section Known Problems.
The foomatic package contains a generic printer filter and PPD (PostScript Printer Definition) files for printers that understand printer languages other than PostScript (such as PCL). This enables printing of PostScript files to these printers, by translating the PostScript file to the language understood by the printer. The filter and PPD files are integrated with the cups package (see CUPS), 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.
The jpeg package installs libjpeg and associated utilities from Version 6b of the Independent JPEG Group's open source JPEG image compression software. The libjpeg library allows applications to compress images and store them in JFIF format files, and decompress JFIF format files containing JPEG compressed images. For JPEG release notes, see the jpeg(7) manual page. The following utilities are also provided; see the associated manual pages listed below:
| cjpeg(1) | sample application for converting PPM, PGM, BMP, Targa image formats to JPEG |
| djpeg(1) | sample application for converting JPEG files to PPM, PGM, BMP, GIF, Targa image formats |
| jpegtran(1) | utility for lossless transcoding between different JPEG processes |
| rdjpgcom(1) | extracts textual comments from JFIF files |
| wrjpgcom(1) | inserts textual comments in JFIF files |
See the JPEG Archive Site at ftp://ftp.uu.net/graphics/jpeg for more documentation on the JPEG software.
A new multithreaded version of the Perl Programming Language, version 5.8.0, is supplied and installed automatically when the cups package is selected for installation using the Upgrade Wizard. The perl package does not replace the version of Perl (perl5) installed from the UnixWare 7.1.3 media. Instead, it is installed separately under /opt. The file /usr/bin/perl is, however, made a link to the new 5.8.0 version of the perl interpreter.
The perl package can also be installed separately from cups. Most perl users will also want to install the perlmods package from the SCOx CD. This package fixes a CGI.pm security vulnerability (see Known Problems), and provides other updated and useful modules as well. The perlmods package can only be installed and used with the new perl package.
The libpng package installs Version 1.2.5 of libpng, an open source library that applications can use to manipulate PNG (Portable Network Graphics) raster image files. See libpng(3) for release notes, a usage overview, and further references. See libpng(3) and libpngpf(3) for function definitions. Further documentation and archives are available at http://www.libpng.org, or ftp://ftp.uu.net/graphics/png. This package requires that the zlib package is already installed.
The libtiff package contains a library for manipulating Tag Image File Format (TIFF) image files, along with TIFF-related utilities. This version of libtiff supports TIFF version 4.0, 5.0, and 6.0 files. The package installs its own manual pages:
See Section 3t. See the libtiff(3t) manual page for an introduction.
Also see the following command manual pages:
| fax2ps (1) - convert a TIFF facsimile to compressed |
| fax2tiff (1) - create a TIFF Class F fax file from raw fax data |
| gif2tiff (1) - create a TIFF file from a GIF87 format image file |
| pal2rgb (1) - convert a palette color TIFF image to a full color image |
| ppm2tiff (1) - create a TIFF file from a PPM image file |
| ras2tiff (1) - create a TIFF file from a Sun rasterfile |
| rgb2ycbcr (1) - convert non-YCbCr TIFF images to a YCbCr TIFF image |
| sgi2tiff (1) - create a TIFF file from an SGI image file |
| thumbnail (1) - create a TIFF file with thumbnail images |
| tiff2bw (1) - convert a color TIFF image to greyscale |
| tiff2ps (1) - convert a TIFF image to PS |
| tiff2rgba (1) - convert a TIFF image to RGBA color space |
| tiffcmp (1) - compare two TIFF files |
| tiffcp (1) - copy (and possibly convert) a TIFF file |
| tiffdither (1) - convert a greyscale image to bilevel using dithering |
| tiffdump (1) - print verbatim information about TIFF files |
| tiffgt (1) - display an image stored in a TIFF file (Silicon Graphics version) |
| tiffinfo (1) - print information about TIFF files |
| tiffmedian (1) - apply the median cut algorithm to data in a TIFF file |
| tiffsplit (1) - split a multi-image TIFF into single-image TIFF files |
| tiffsv (1) - save an image from the framebuffer in a TIFF file (Silicon Graphics version) |
The SCOx Client API is a set of application programming interfaces that use standard web technologies such as WSDL, SOAP, XML, and XML Schemas to enable your applications to interface with SCObiz. SCObiz is a comprehensive web site development, deployment, and hosting service through which SCO's partners can provide web site hosting solutions to their customers. SCObiz provides an infrastructure that enables solution providers to quickly and easily create e-Commerce or information-oriented web sites. The web services supported by SCOx and SCObiz enable applications to exchange data directly over the internet, without human intervention. Such applications can be anything from simple requests to complex business processes.
The SCOx client libraries and web services are available on a separate CD image. Release notes and installation instructions can be found at the top level of the SCOx CD image, and on the UnixWare Supplements Web Page. Also see the SCOx and SCObiz Web Sites.
Please Note: You must install the Update Pack Set before you install the SCOx CD. Please read the SCOx Release Notes from the CD or Supplements Page before installing SCOx.
© Copyright 2003 The SCO Group, Inc. All rights reserved.