____________________________________________________________________________ Release Supplement 5.0.6A for OpenServer 5 ____________________________________________________________________________ Release and Installation Notes 4/25/2001 ____________________________________________________________________________ This document contains critical information you need to know before and just after installing Release Supplement 506A for OpenServer(TM) Release 5.0.6. Familiarize yourself with the information in these notes that is relevant to your system, then install Release Supplement 506A according to the instructions below. This document is available both in the media distribution and from the download site: ftp://ftp.sco.com/Supplements/rs506a _________________________________________________________________________ NOTE Unless otherwise noted, this document supplements the OpenServer Release 5.0.6 Release Notes, which are still relevant. As information becomes available after the publication of these Release Supplement 506A Release Notes, it is posted as Late News at the OpenServer Release 5 documentation web site: http://osr5doc.sco.com _________________________________________________________________________ This document covers the following topics: + ``Highlights of this supplement'' + ``Installing the supplement'' + ``Installing the supplement across the network'' + ``Removing the supplement'' + ``Preserving customized files'' + ``Software notes and limitations'' + ``Documentation notes and errata'' + ``Bug fixes included in Release Supplement 5.0.6a'' + ``Sendmail Supplement for OpenServer 5.0.6a'' + ``Universal Serial Bus(USB) Supplement for OpenServer 5.0.6a'' Highlights of this supplement The following list highlights some of the more prominent changes that Release Supplement 506A makes to an OpenServer Release 5.0.6 system: + ``BIND 8.2.2'' + ``Client Manager'' + ``Network configuration improvements'' + ``P6 microcode updates'' + ``Pentium 4 support'' + ``SCSI III tape device support'' + ``popper 3.0.2'' + ``FTPD 2.6.1'' + ``Improved PPP Manager authentication and name service support'' + ``DHCP client'' + ``IP Filter improvements'' + ``Improved more command'' + ``MountCD icon'' + ``Bug fixes'' + ``New and updated documentation'' If you have questions regarding this supplement, or the product on which it is installed, please contact your software supplier. BIND 8.2.2 Release Supplement 506A updates Berkeley Internet Name Domain (BIND) software, which implements the Domain Name Service (DNS), from Release 8.1.1 to 8.2.2. New features in BIND Release 8.2 include: + RFC 2308 (Negative Caching) + RFC 2181 (DNS Clarifications) + RFC 2065 (DNS Security) + TSIG (Transaction SIGnatures) + Support for multiple virtual name servers + ndc uses a "control channel" now (no more signals) + ndc uses a "control channel" now (no more signals) + Many bug fixes + Documentation improvements + Performance enhancements For a complete listing of new features in BIND Release 8.2.2 (including patch level 7), see the Internet Software Consortium (ISC) home page: http://www.isc.org/products/BIND/bind8.html See also the updated named(ADMN) manual page. _________________________________________________________________________ NOTE Chapter 6, ``Configuring the Domain Name Service'' in the Networking Guide has not been updated in this Release Supplement 506A release. However, the current Name Server Operations Guide for BIND is available in plain text and PostScript(r) versions; see the /info/bind directory of the media distribution or the ISC home page. _________________________________________________________________________ Client Manager The new Client Manager provides a graphical interface for configuring network client services, including: + name service (DNS and /etc/hosts) + default routes + name service search order + Network Time Protocol (NTP) + a graphical interface for common network administration tools See ``Configuring TCP/IP client services'' in the Networking Guide for more information. Network configuration improvements Release Supplement 506A provides access to new network configuration parameters in the /etc/default/tcp file using the Network Configuration Manager and the Client Manager. See the updated tcp(SFF) manual page for more information. P6 microcode updates Release Supplement 506A adds the latest P6 microcode updates from Intel to the existing p6update command. Pentium 4 support Release Supplement 506A adds support to ensure that the Pentium 4 chip will not run slow due to thermal speed-throttling. _________________________________________________________________________ WARNING Do not run OpenServer on Pentium 4 systems without Release Supplement 506A. Doing so might damage your hardware. OpenServer drivers have been upgraded to support Pentium 4 technology. Before using other drivers on your system, consult your vendor to ensure that they conform to Pentium 4 specifications. _________________________________________________________________________ SCSI III tape device support Release Supplement 506A supports SCSI III tape devices. See the updated scsi(HW) manual page for more information on SCSI devices. popper 3.0.2 New features in popper Release 3.0.2 include: + Bulletins can now be issued to users based on group membership. + Reverse-lookups on client IP addresses can now be disabled by using the -R run-time switch. + User names can be down-cased by using the -c run-time switch. This helps when users are in the habit of entering their user name in ALL CAPS. + Optional automatic deletion of downloaded messages. Can be used to prevent users from keeping mail on the server. + Add your own text to the greeting by editing the banner.h file. See the updated popper(ADM) manual page for more details and a complete list of features. FTPD 2.6.1 New features in FTPD Release 2.6.1 include: + Enhancements to the configuration script options + Fixed security leaks that could result in root shell compromises + Fixed port-allow in ftpaccess + Support for the virtual passwd/virtual shadow features of BeroFTPD + Corrections to SITE MINFO See the updated ftpd(ADMN) manual page for more information. Improved PPP Manager authentication and name service support The PPP Manager now supports configuration of: + Microsoft extensions to the CHAP protocol (MSCHAP). + Domain Name Service (DNS) server addresses. + Windows Internet Naming Service (WINS) server addresses. For further information, see the updated pppauth(SFF) manual page and ``Configuring PPP'' in the Networking Guide. DHCP client Release Supplement 506A includes DHCP client functionality. For more information, see the new dhcpc(ADMN) and dhcpc.conf(SFF) manual pages. IP Filter improvements Release Supplement 506A includes an rc2.d script that automatically loads the IP Filter (IPF) and Network Address Translation (NAT) configuration files at startup. In addition, the mkdev command now supports IP filter configuration. See the updated mkdev(ADM) and ipf(ADMP) manual pages for more information. Improved more command The standard OpenServer more(C) pager has been upgraded to include new functionality from the less command, including interactive commands and environment variable support. See the more(C) manual page for details. MountCD icon After installing Release Supplement 506A and rebooting, the root user desktop includes a new MountCD icon. To mount a CD with this icon, place a CD-ROM in the drive and click on the icon; the icon shows a mountain symbol when the CD-ROM is mounted. To unmount a CD-ROM, click on the drive again; when the mountain symbol disappears, the CD-ROM is unmounted. Bug fixes For a complete list of the changes that Release Supplement 506A makes to an OpenServer Release 5.0.6 system, see the rs506a.fixlist at the end of this document or on the media distribution: + file:/info/506a/506a.fixlist New and updated documentation In addition to new and updated documentation for features described in this section, Release Supplement 506A provides: + the new SCOadmin Developer's Guide + new manual pages for SCOadmin Services Library (C/C++ interface) (section S_ADM) + new manual pages for SCOadmin Services Library (Tcl interface) (section TCL_ADM) + miscellaneous improvements and bug fixes _________________________________________________________________________ NOTE Localized documentation was not updated in this supplement release. _________________________________________________________________________ Installing the Release Supplement 506A: Downloading the Supplement from the server: ftp.sco.com go to the directory: Supplements/rs506a get all the files in that directory: rs506a.tar = The tar archive of the VOL files. rs506a.txt = Cover letter and Installation instructions. Copy these files to a directory on your local server. Before you can install the Supplement, you must extract the files from the tar(1M) archive with the command: # tar xvf rs506a.tar When you install Release Supplement 506A you will be installing the following packages: Release Supplement 506a Sendmail Supplement USB Supplement Please review the Installation instructions for the individual supplements included in the document for package dependencies if you want to install or remove the packages individually. You can install Release Supplement 506A from distribution media (such as a CD-ROM or a floppy disk) or from media images on a software server or web site. The supplement consists of a number of files with names of the form VOL.nnn.nnn. If you download the supplement as media images, make sure you have all the files. To install the supplement: 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 Install New. 4. When prompted for the host (machine), select the current host and then Continue. 5. In the Select Media window: - If you are loading this release supplement from a media image, click on Media Device and select Media Images, then Continue. (You may need to pull down the scroll bar before you see the Media Images option.) In the Enter Image Directory window, enter the absolute pathname for the directory in which the media images reside. For example: /tmp Click on OK. - If you are loading this release supplement from a CD-ROM or floppy disk, select the appropriate drive and then Continue. 6. The Install Selection window lists the supplements included in Release Supplement 506A. You must install the Software Manager Supplement first. Select only the ``Software Manager Supplement'', then click on Install. There is a short delay while the installation takes place, and a message instructs you to restart the Software Manager before installing the rest of Release Supplement 506A and other supplements from the distribution media. 7. In the Installation Complete window, click on OK. The Software Manager should now list the Software Manager Supplement. 8. Exit the Software Manager by selecting Host, then Exit. Then restart the Software Manager, now patched by the supplement you just installed. 9. From the Software menu, select Install New. 10. When prompted for the host (machine), select the current host and then Continue. 11. In the Select Media window: - If you are loading this release supplement from a media image, click on Media Device and select Media Images, then Continue. (You may need to pull down the scroll bar before you see the Media Images option.) In the Enter Image Directory window, enter the absolute pathname for the directory in which the media images reside; for example: /tmp Click on OK. - If you are loading this release supplement from a CD-ROM or floppy disk, select the appropriate drive and then Continue. 12. In the Install Selection window, select the remaining supplement. Click on Install. There is a short delay while the installation takes place. 13. In the Installation Complete window, click on OK. The Software Manager should list the supplements you selected. The patched software is now installed. 14. Exit the Software Manager by selecting Host, then Exit. 15. Reboot the machine. The Software Manager automatically relinks the kernel after each installation. You must reboot before the new kernel takes effect. Installing the supplement across the network You can install the supplement from one OpenServer Release 5.0.6 machine onto another across a TCP/IP network. To do so, you need a software server, which you can create as described in Chapter 21, ``Installing and managing software over the network'' in the Networking Guide. This server has a user account called swadmin. Use the Software Manager to install or load Release Supplement 506A on the software server; see ``Installing the supplement''. To install the supplement onto a local machine 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 patch. Select From Another Host. You will need to provide the name of the software server, as well as the password of the swadmin user on the software server. Removing the supplement _________________________________________________________________________ NOTE You must remove software patches (such as release supplements) in the reverse order of their installation. In other words, if you installed ``Patch1'', then ``Patch2'', then ``Patch3'', you must remove ``Patch3'', then ``Patch2'', before you can remove ``Patch1''. _________________________________________________________________________ To remove a supplement: 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 title of the supplement you are removing. 4. From the Software menu, select Remove Software. In the confirmation window, verify that you selected the right supplement, then click on Remove. _________________________________________________________________________ CAUTION Removing a supplement (patch) in the current OpenServer release corresponds to rolling it back and unloading it in earlier OpenServer releases. If you need to keep a copy of a patch loaded, click on More Options in the Confirm Selected Software window. Then, specify Leave Loaded, and click on Remove. Some effects of certain supplements are irreversible because of the nature of the correction (for example, restoring correct permissions on system directories). However, removing the supplement will remove the patch name from the system. _________________________________________________________________________ There is a short delay, then the Removal complete window appears. Click on OK. The Software Manager should no longer list the supplement you removed. 5. When you have finished removing and installing software, exit the Software Manager by selecting Host, then Exit. 6. Reboot the machine. The Software Manager automatically relinks the kernel after software is removed. You must reboot before the new kernel takes effect. Preserving customized files Release Supplement 506A backs up the following user-configurable files, then modifies or replaces them: /var/opt/K/SCO/link/1.1.1Ga/etc/conf/pack.d/kbmouse/space.c /var/opt/K/SCO/Unix/5.0.6Ga/etc/termcap /var/opt/K/SCO/Unix/5.0.6Ga/usr/lib/terminfo/terminfo.src /var/opt/K/SCO/Unix_FR/5.0.6Ga/usr/lib/nls/misc/fr_FR.ISO8859-1/Unix/magic /var/opt/K/SCO/Unix_DE/5.0.6Ga/usr/lib/nls/misc/de_DE.ISO8859-1/Unix/magic If you have customized any of these files, you can restore your changes from the backed-up copies after you install the supplement. The files are backed up to: /opt/K/SCO/link/rs506a.link111.1.0a/patch_backup/pack.d/kbmouse/space.c /opt/K/SCO/Unix/rs506a.Unix506.1.0a/patch_backup/termcap /opt/K/SCO/Unix/rs506a.Unix506.1.0a/patch_backup/terminfo.src /opt/K/SCO/Unix_FR/rs506a.Unix_FR506.1.0a/patch_backup/magic /opt/K/SCO/Unix_DE/rs506a.Unix_DE506.1.0a/patch_backup/magic Software notes and limitations The following notes and limitations apply to Release Supplement 506A: + ``Unmounting with the MountCD icon'' + ``ftpd root password recognition'' + ``POP server error messages'' + ``Changes in /usr/local directory layout'' + ``Core dump tunables'' + ``NTP subsystem update'' + ``Installing with Adaptec 2916x host adapters'' + ``Installing on Adaptec dual channel host adapters'' + ``Installing on NCR 815XS host adapters'' + ``Non-primary hard disk divisions not available'' + ``Video adapter might require accelerated video driver'' + ``Remove SCODB before upgrading'' + ``Upgrading to the Enterprise configuration from Host or Desktop'' + ``/etc/default/lang errors'' + ``Configuration and startup changes for TCP/IP'' + ``Changes to the contents of /etc/resolv.conf'' + ``DOS session requires ansi terminal type'' + ``Merge upgrade'' Unmounting with the MountCD icon Before unmounting a CD-ROM with the MountCD icon, you must ensure that the mount point directory (usually /mnt) is not busy. If it is, the unmount operation will fail but the MountCD icon will show that the CD- ROM drive is not mounted. To work around this problem, you must unmount the CD-ROM drive manually from the root command line using the umount(ADM) command. ftpd root password recognition The updated ftpd(ADMN) in Release Supplement 506A differs from the previous release in its handling of certain long passwords. The root password will not be recognized by ftpd if all the following conditions are met: + a system was installed with the ``low'' or ``traditional'' security defaults, + its root password was set during system installation to a string longer than 8 characters, and + the root password has never been changed since installation. To correct this, run passwd(C) as root and enter the same password (or a new one). This rewrites the password entry in a form that is understandable to the new ftpd. POP server error messages When connections are established by certain electronic mail clients, including some versions of Netscape Communicator, the popper(ADM) POP 3 server might generate messages in the /usr/adm/syslog file that contain the text: ERR Unknown command: "xsender" These messages are benign and can safely be ignored. Changes in /usr/local directory layout The OpenServer Release 5.0.6 installation creates empty directories (including bin and lib) under /usr/local. This is a change from previous releases that is a potential source of problems, particularly if you have an existing /usr/local hierarchy on a separate filesystem. The /usr/local directories are symlinks in the /opt/K/SCO hierarchy, and during an upgrade, the original /usr/local directories are lost when the symlinks are created. Because the Release 5.0.6 directories are recorded in the custom(ADM) database, any changes made by an administrator after installation will be undone by custom verify operations (using the custom -v or -V options). If you have added files to the /usr/local directory or its subdirectories, you must back up the directory manually before performing an upgrade. The contents of /usr/local are overwritten during an upgrade installation. When the upgrade installation is complete, you can copy your files back into the directories within the root filesystem created by the installation. If you want these files elsewhere, create any desired links to other filesystems within the /opt/K/SCO hierarchy, which should make the files visible through the /usr/local directory once again. Core dump tunables A new undocumented feature in OpenServer is the ability to control the processes that dump core using tunable parameters in the /etc/conf/pack.d/kernel/space.c file. For more information, see the comments in the file; further documentation will be available in a future release. _________________________________________________________________________ WARNING Use extreme caution when modifying this file. Accidental changes may make your system unusable. _________________________________________________________________________ NTP subsystem update The NTP (Network Time Protocol) subsystem was updated in OpenServer Release 5.0.6 from NTPv3 to NTPv4. As part of this process, the xntpd and xntpdc binaries were removed and replaced with ntpd and ntpdc binaries. Other NTP binaries were also updated to newer versions. NTPv4 is compatible with NTPv3, and the same /etc/ntp.conf file is used, which is identical in most cases. For more information, see: + the new ntpd(ADMN) and ntpdc(ADMN) manual pages. However, see also ``NTP documentation''. + the Time Synchronization Server web site: http://www.eecis.udel.edu/~ntp/ Installing with Adaptec 2916x host adapters If you want to install OpenServer Release 5.0.6 on a device connected to an Adaptec 2916x SCSI host adapter or compatible devices, you must use the ad160 driver from the CD boot image or from the SCSI host adapter Boot Time Loadable Driver (BTLD) disk. The ad160 driver is not included on the primary installation disk, and you will receive "Host adapter not found" error messages if you try to boot from this disk. If you boot from the installation CD-ROM, the driver will be available for the installation process. If you boot from floppy disks, you must first install the ad160 driver from the SCSI host adapter BTLD disk as described in ``Installing boot-time loadable drivers'' in the OpenServer Handbook. For more information, see ``Boot devices and media'' in the Release Notes. Installing on Adaptec dual channel host adapters If you want to install OpenServer Release 5.0.6 on a device connected to an Adaptec 3916x Dual Channel SCSI host adapter or dual Adaptec 2916x SCSI adapters, your CD-ROM and hard drives should be on the primary bus of the first configured adapter. If the devices are attached to different channels or devices, the order of controllers may be changed after reboot and the devices may not be recognized. This is a known bug that will be addressed in a future driver release from Adaptec. Installing on NCR 815XS host adapters If you have installed OpenServer Release 5.0.6 on a system where the primary hard disk is attached to an NCR 815XS host adapter, the system might hang during the first attempt to boot from the disk with the following message displayed: F slhainit To work around this problem, power cycle the system and enter the following after the "boot:" prompt: defbootstr scsi.noscan The system should now boot successfully. For more information, see the bootstring(HW) manual page. Non-primary hard disk divisions not available Some divisions configured during installation on a second SCSI hard disk might not be available after installation and are displayed by divvy(ADM) as not named. To make those divisions available, use divvy after installation to name the divisions, but do not make any other changes with divvy. Then, install the updated division table to make all divisions available as configured. Video adapter might require accelerated video driver Most video adapters can be operated with the generic VESA video driver. A more limited range of video adapters can be operated with accelerated, hardware-specific drivers. When a hardware-specific driver exists, the SCOadmin Video Configuration Manager will identify it. Accelerated drivers usually perform much faster than the VESA driver. If you experience problems with the operation of a video adapter, try switching between its accelerated and VESA drivers. An adapter not behaving correctly with one driver might operate correctly with the other. Specifically, if you experience system hangs with the Number Nine SR9 AGP video adapter using the VESA driver, you should configure and use the accelerated video driver to avoid this problem. Remove SCODB before upgrading If SCODB, the kernel debugger, is linked into the kernel prior to an in- place upgrade, the upgrade fails with an error message similar to: undefined symbol - scodbinit To avoid this problem, before trying to upgrade to OpenServer, deactivate SCODB in the link kit by changing Y to N in the file /etc/conf/sdevice.d/scodb. If the system has already been upgraded, you can correct the problem by editing the file /etc/conf/cf.d/mdevice. but be careful not to damage the format of this file because you cannot reconstruct it without reinstalling the system. On the line for ``scodb'', change the second field from ``P'' to ``PI''. (Because of the risk involved in editing /etc/conf/cf.d/mdevice, it is safer to deactivate SCODB, as described above, before upgrading.) Upgrading to the Enterprise configuration from Host or Desktop During an upgrade installation of an OpenServer Release 5.0.6 Host or Desktop System to Release 5.0.6 Enterprise System, you are prompted to enter your Enterprise license. Supply the license information from your Release 5.0.6 Enterprise System Certificate of License and Authenticity (COLA); do not choose to install the 60-day evaluation license because there is no built-in evaluation license for OpenServer. If you select the 60-day evaluation license, after installation the Enterprise system is in an unlicensed state, the License Manager shows the Host or Desktop license, and the Software Manager shows the Host or Desktop software as installed. To clear these unnecessary entries from the License Manager and Software Manager and to ensure that your system is licensed correctly, performing the following steps after installation: 1. Remove the Host or Desktop license from the License Manager. 2. Remove the product database for the Host or Desktop software: rm -r /opt/P/SCO/product Replace product, with unixos for the Host software or with odtps for the Desktop software. 3. Change directory to /etc/conf/pack.d/kernel. 4. Run the brand(ADM) command using the Enterprise license from your Release 5.0.6 COLA to make sure all the appropriate files are updated on the system. If your COLA has a license data string, enter: brand -g -a "license_data" license_number license_code os.a For example: brand -g -a "k1;q1;m9zyxwv" NUM123ENT xexfmyub os.a If your COLA does not have a license data string, enter: brand -g license_number license_code os.a Then, relink the kernel and reboot the system. For more information, see ``Upgrading to the Enterprise configuration from Host or Desktop'' in the OpenServer Handbook. /etc/default/lang errors On a system installed in French or German, after reboot, you will see a series of errors similar to this: iserrno = 117 This error can be ignored and should not cause any problems. Configuration and startup changes for TCP/IP Important changes to TCP/IP configuration have been introduced in OpenServer Release 5.0.6 and Release Supplement 506A: + If you defer networking or do not enter DNS client configuration at installation, an /etc/resolv.conf is not created and you will not have TCP/IP network connections. To do, so you must run the Network Configuration Manager to configure network interfaces or run the Client Manager to configure DNS client services after installation. For more information, see: - Chapter 1, ``Configuring network connections'' in Configuring Network Connections - ``Configuring TCP/IP client services'' in the Networking Guide + Router daemons (routed, gated and irdd) are no longer started by default at installation. They must be started explicitly by editing the /etc/default/tcp file. For more information, see: - the tcp(SFF) manual page - Chapter 5, ``Configuring Internet Protocol (IP) routing'' in the Networking Guide Changes to the contents of /etc/resolv.conf Beginning in OpenServer Release 5.0.6, the /etc/resolv.conf file might be created for you during a fresh installation; however, if you examine this file, you might notice that the domain line is missing, which is intentional because the domain line is redundant with the search line. While the domain keyword is still legal, if the domain line appears after the search line, the search line is ignored. To prevent confusion or misunderstanding, the /etc/resolv.conf file is now created without the domain line. Other configuration information placed in the /etc/resolv.conf file during installation includes: + primary nameserver + secondary nameserver + hostresorder (local first, BIND second) The /etc/resolv.conf file is created only if nameserver addresses and the system domain name were entered during initial installation. For more detailed instructions on resolver configuration, see the resolv.conf(SFF) manual page. DOS session requires ansi terminal type If you start a DOS session from a tty running the ``scoansi'' terminal type, DOS does not work correctly. If you exit the DOS environment and set the terminal type to ``ansi'', then DOS works correctly. Merge upgrade Currently, it is not possible to upgrade existing Windows installations from Winsock networking to the new support for VNET (Network Neighborhood) networking. If you want VNET networking with existing Merge(TM) and Windows(r) accounts, back up the accounts' user data files and reinstall Windows with the VNET option selected at installation time. See the Merge documentation for instructions on installing Windows under Merge. _________________________________________________________________________ WARNING Do not use the fix_vnet function in Merge. Use of this function can result in the need to reinstall Windows and perhaps Merge as well. _________________________________________________________________________ A patch for Merge that will enable the fix_vnet function will be available in the near future from the Support website: http://www.sco.com/support/ Documentation notes and errata The following documentation notes apply to Release Supplement 506A: + ``Restarting the calendar server with IQM_LANGUAGE'' + ``NTP documentation'' + ``Network configuration at installation'' + ``DNS documentation'' + ``APIs and the high-precision clock'' + ``netstat manual page'' + ``awk manual page'' + ``recon manual page'' Restarting the calendar server with IQM_LANGUAGE The steps given in ``Calendars'' in the OpenServer Handbook to restart the calendar server with the initial LANG setting are not correct. Below are the correct steps: 1. Change directory to /usr/lib/sco/oadb and remove all the data files in the caldata directory with: cd /usr/lib/sco/oadb rm caldata/* 2. Enter: DBKEY=6373 IQMFILE=/usr/adm/ISL/iqm_file . $IQMFILE LANG=$IQM_LANGUAGE export DBKEY IQMFILE LANG 3. Change directory to /usr/lib/scosh/utilbin and rebuild the database with: cd /usr/lib/scosh/utilbin ./calbuild You should now be able to administer the calendar database. To make this change permanent on your system, you must also: 1. Edit the file /etc/rc2.d/P95calserver and find the line: DBKEY=6373; export DBKEY 2. Before that line, add: IQMFILE=/usr/adm/ISL/iqm_file . $IQMFILE LANG=$IQM_LANGUAGE export IQMFILE LANG This will enable the calendar server to start using the locale that was set at installation time, regardless of the system locale setting. NTP documentation The ntpd(ADMN) and ntpdc(ADMN) man pages conform to NTP version 4. However, they have not been completely updated nor has other NTP documentation. The most current documentation is available at the NTP web site: http://www.eecis.udel.edu/~ntp/ntp_spool/html/index.htm Network configuration at installation Step 23 of the ``Installation and upgrade checklist'' in the OpenServer Handbook incorrectly states that routed is started whether or not DNS client configuration is specified at installation. Router daemons are no longer start by default and must be started explicitly by editing the /etc/default/tcp file. For more information, see: - the tcp(SFF) manual page - Chapter 5, ``Configuring Internet Protocol (IP) routing'' in the Networking Guide DNS documentation Chapter 6, ``Configuring the Domain Name Service'' in the Networking Guide has not been updated in this Release Supplement 506A release. However, the current Name Server Operations Guide for BIND is available in plain text and PostScript(r) versions; see the /info/bind directory of the media distribution or the ISC home page. APIs and the high-precision clock The clock(HW) manual page that describes the high-precision clock used for OpenServer Release 5.0.6 and later releases should include the following information about API support for this feature. The following information should be added to this manpage: As of Release Supplement 506A for OpenServer Release 5.0.6, a subset of APIs that use the kernel clock have been modified to utilize the high-precision clock. These are: select(S) has microsecond precision, adjusted for kernel entry and exit times, time-sharing delays, and so forth. usleep(S) has microsecond precision (uses select(S)). nap(S) has microsecond precision, with one-millisecond granularity. sleep(S) has microsecond precision, with one second granularity. gettimeofday(S) returns microsecond precision. settimeofday(S) accepts and implements microsecond precision. adjtime(S) accepts and implements microsecond precision ftime(S) returns millisecond precision. The following functions do not fully take advantage of the high-precision system clock as of Release Supplement 506A for OpenServer Release 5.0.6: poll(S) has 10-20 millisecond precision. alarm(S) has 10-20 millisecond precision. setitimer(S) has 10-20 millisecond precision. ualarm(S) has 10-20 millisecond precision (uses setitimer(S)). timer_settime(S) has 10-20 millisecond precision. netstat manual page The netstat(TC) manual page and usage message incorrectly list -M and -N options, which have not been implemented. awk manual page The version of awk(C) included in Release Supplement 506A for OpenServer Release 5.0.6 has been extended to support the -We and -Wexec options from mawk, a GPL awk interpreter by Michael D. Brennan. The new syntax is: awk [ -F ] [ -v = ] ... {{-f | -e '' } ... | -We | '' } { = | } ... The description of the new arguments is: -We and -Wexec special means of passing the name of a srcfile, indicating that it is the last option on the command line and that the next argument, if any, is the name of a sourcefile. Thus the following two commands are identical: awk -We srcfile [arg ...] awk -f srcfile -- [arg ...] awk, like many utilities, allows the use of "--" to terminate the option list. -We is mostly used in an executable awk program file that uses the #! mechanism documented on the exec(M) manual page. For awk, the #! line typically looks like this: #!/usr/bin/awk -f Such a line passes the following arguments to awk: -f srcfile [args ...] where [args ...] are any arguments with which the program is invoked. If only filenames are passed, this works properly. However, if the first argument begins with '-', it appears to awk as though it is an argument that should be interpreted according to awk's command line syntax. This prevents an awk program from using POSIX-style options, which are introduced with '-'. The -We construct avoids these problems. If a program begins with: #!/usr/bin/awk -We the following is passed to awk: -We srcfile [arg ...] which is equivalent to: awk -f srcfile -- [arg ...] The -We version is used because the #! mechanism does not allow for the latter syntax. Because of the implicit "--", awk does not attempt to interpret any arguments as options to itself. For example, passing the -q option to "#!/usr/bin/awk -f" will abort with an error. But passing -q to the following runs correctly: #!/usr/bin/awk -We With the -We option, -q is stored in ARGV[1], where it can be interpreted by the awk program as required. -Wexec is a synonym for -We. recon manual page recon(C) has been extended to include logging capabilities with the -i, -o, -a, and -u options. The new syntax is: recon [-ahlSux] [-ttimeout | -cchar-times] [-mmin-time] [-i] [-o] [-T] [-pptyname] [command_line] The meaning of the new options is: -a Append information to the rather than overwriting it. Used with the -i and -o options. Note that, when specifying both the -i and -o options and using the same for both, you must use -a or the input and output will overwrite each other. -u Write data from the -i and -o options to the immediately without buffering by recon. This lets another process that is monitoring the log files see the tty input and/or output immediately. Unbuffered logging is less efficient, so use this option only when necessary. Note that, when specifying both the -i and -o options to use the same , you must use -u if you want the input and output to appear in the in the same order as they appeared. -i and -o Log all input (-i) or output (-o) to the specified . "Input" is data sent to the application(s) run by recon as though it had been typed at a keyboard. Typically it is the real keyboard input typed by the user. "Output" is data output by the application being run by recon. The -o option is functionally equivalent to the script(TC) utility. -i and -o can both be specified to log both input and output, and and can be the same filename. If you specify both -i and -o to use the same , you should also use the -a option or the input and output will overwrite each other. The -u option is also advisable so that the input and output will appear in the same order as they occurred. Note, however, that it may be difficult to differentiate between the input and output from the contents of the . ---------------------------------------------------------------------- Bug fixes included in Release Supplement 5.0.6a: The following list includes bug report numbers and corresponding descriptions of the changes and corrections that Release Supplement 506A for OpenServer Release 5.0.6 (RS506A) makes to an OpenServer Release 5.0.6 system: ---------------------------------------------------------------------- Bug-ID: SCO-559-1088 A parsing error was corrected in uucp(C). This problem caused error messages of "uucp: illegal syntax" and "uucp: failed completely [11]". This problem was introduced in OpenServer Release 5.0.6. ---------------------------------------------------------------------- Bug-ID: SCO-559-1183 uucp(C) acted as if its "-r" flag was always set, that is, it failed to immediately invoke uucico(ADM) to start a transfer. This problem was introduced in OpenServer Release 5.0.6. ---------------------------------------------------------------------- Bug-ID: SCO-236-1634 uuxqt(ADM) recognizes a new configuration option, "UUXQT_SAVE_JOBS=YES" in the new file /usr/lib/uucp/Default. When enabled, uuxqt checks the exit status of each job that it runs. Jobs which exit with non-zero exit status are moved to the /usr/spool/uucp/.Corrupt directory rather than being deleted. ---------------------------------------------------------------------- Bug-ID: BEL-27-84 Parsing of additional arguments after the user's name by getty(M) was corrected. Arguments of the form "var=value" are entered into the logged-in user's environment; arguments without "=" are entered as "L0=arg0", "L1=arg1", and so on. ---------------------------------------------------------------------- Bug-ID: SCO-247-281 A 20-second delay when control-D is hit at the getty(M) prompt was removed. ---------------------------------------------------------------------- Bug-ID: SCO-236-1705 The configurable modem dialer atdialer(C) was modified to log debug information via syslog(SLIB) rather than directly to the system console. The serial(HW) driver and getty(M) were enhanced so that background tasks from a previous login session do not interfere with a modem's ability to hang up, accept a subsequent connection, and login a new session. ---------------------------------------------------------------------- Bug-ID: SCO-97-1164 The serial(HW) driver has been enhanced to support the line control ioctls TIOCMGET, TIOCMSET, TIOCMBIC and TIOCMBIS. ---------------------------------------------------------------------- Bug-ID: LTD-245-1688 dlvr_audit(ADM) incorrectly sent messages to its message queue even when auditing was disabled and auditd(ADM) was not running. This caused problems if another process was using the same message queue identifier. ---------------------------------------------------------------------- Bug-ID: SCO-247-295 A security problem was corrected in dlvr_audit(ADMN). ---------------------------------------------------------------------- Bug-ID: SCO-247-292 Security problems were corrected in scohelp(XC) and the scohelp API. ---------------------------------------------------------------------- Bug-ID: SCO-247-294 A security problem was corrected in talkd(ADMN). ---------------------------------------------------------------------- Bug-ID: SCO-559-1099 Security problems were corrected in the online documentation server, scohttp(ADM). ---------------------------------------------------------------------- Bug-ID: LTD-246-1354 Tcl script errors in bshrink(ADM) were corrected. ---------------------------------------------------------------------- Bug-ID: SCO-231-508 irdd(ADMN) did not correctly switch to the alternate router when the primary router failed. ---------------------------------------------------------------------- Bug-ID: SCO-231-513 A potential panic in dlpid(ADM) was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-247-300 A potential core dump in the ftp(TC) client "site" and "quote" commands was fixed. ---------------------------------------------------------------------- Bug-ID: SCO-236-1663 The ftp_api(SLIB) FTP application programming interface was modified to correctly track whether it currently has an FTP command socket open. ---------------------------------------------------------------------- Bug-ID: SCO-232-473 The ftp(TC) client no longer displays transfer rates in scientific notation. ---------------------------------------------------------------------- Bug-ID: SCO-236-1582 lpd(ADMN) was enhanced to support the printcap(SFF) output filter capability, "of=filter-script", for output to remote printers. ---------------------------------------------------------------------- Bug-ID: SCO-236-1588 A new divvy(ADM) flag, "-l", allows filesystem labels to be managed. ---------------------------------------------------------------------- Bug-ID: SCO-236-1728 A potential core dump in cron(C) was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-559-1093 cron(C) now ignores SIGXFSZ. Previously it could be killed by this signal if the file /usr/lib/cron/log grew larger than the system-wide ulimit. ---------------------------------------------------------------------- Bug-ID: SCO-236-1735 Problems were corrected in x286emul(C). These problems caused certain XENIX 286 executable programs to hang or crash. ---------------------------------------------------------------------- Bug-ID: SCO-236-1743 A missing "bel=" entry in the ANSI console terminfo entry was preventing programs such as vi(C) from sounding the bell. ---------------------------------------------------------------------- Bug-ID: SCO-247-297 The vi(C) "wrapmargin" option interacted badly with the "." (repeat last command) command. When a repeated insertion caused text to wrap, the wrapped text was executed as vi commands. This was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-247-298 A new "textwidth" option was added to vi(C) (inspired by `vim'). This acts similarly to "wrapmargin" at an absolute column number instead of an offset relative to the screen or window's right margin. ---------------------------------------------------------------------- Bug-ID: SCO-247-299 The "showmatch" option in vi(C) was modified so that matches are highlighted for one second or until further typed input is received. ---------------------------------------------------------------------- Bug-ID: SCO-247-303 prc_sync(ADM) was modified to close its log file descriptor before running scripts. ---------------------------------------------------------------------- Bug-ID: SCO-247-304 The file(C) "-c" option was modified to exit with non-zero status when the checked "magic" file contains errors. ---------------------------------------------------------------------- Bug-ID: SCO-247-305 /etc/yp/lckpwdf, part of the Network Information Service (NIS) service, was modified to prevent it from potentially sending a spurious signal to the init(M) process. ---------------------------------------------------------------------- Bug-ID: SCO-247-306 who(C) was modified so the "-f" and "-x" flags may work together. ---------------------------------------------------------------------- Bug-ID: SCO-559-1107 custom(ADM) was modified to understand that version number "8.11.0" is larger than "8.9.3". ---------------------------------------------------------------------- Bug-ID: SCO-559-1086 Sendmail was updated to version 8.11.0. ---------------------------------------------------------------------- Bug-ID: SCO-559-1102 A defect in the cp(C) "-p" flag was corrected. When copying a set-user- or set-group-ID file over a file which already had the correct permissions, the set-ID bit would be lost. ---------------------------------------------------------------------- Bug-ID: SCO-559-1134 A timing problem was corrected in telnetd(ADMN). This problem caused the temporary file /etc/auth/system/ttys-t not to be deleted; the spurious ttys-t file then caused 30-second delays during all subsequent user logins. ---------------------------------------------------------------------- Bug-ID: SCO-559-1180 rlogind(ADMN) and telnetd(ADMN) were modified to correctly handle systems with more than 1000 pseudo-ttys. ---------------------------------------------------------------------- Bug-ID: SCO-559-1117 In OpenServer 5.0.6, setting "CONSOLE=tty01" in /etc/default/login prevented all users (not just "root") from connecting via rlogin, telnet or ftp protocols. ---------------------------------------------------------------------- Bug-ID: SCO-559-628 Defining a system console with the "CONSOLE=" setting in /etc/default/login now correctly prevents "root" logins via rlogin and telnet protocols. ---------------------------------------------------------------------- Bug-ID: SCO-559-1118 w(C) and uptime(C) would stop displaying system uptime after 248 days. They are now able to display up to 497 days, after which the system's internal uptime counter rolls over to 0. The rollover is harmless and only affects displayed uptime statistics. ---------------------------------------------------------------------- Bug-ID: SCO-559-1135 recon(C) now correctly handles conditions where its standard input is not a terminal device, and no longer mistakenly passes the master side of its pseudo terminal to commands it executes. ---------------------------------------------------------------------- Bug-ID: SCO-559-1136 awk(C) now supports the "-We" flag (inspired by `mawk'). See the updated manual page. ---------------------------------------------------------------------- Bug-ID: SCO-559-1137 The scoadmin Address Allocation Manager previously failed with an unhelpful error message when attempting to select "Pools -> Control" if aasd(ADMN) was not running. ---------------------------------------------------------------------- Bug-ID: SCO-559-1138 The scoadmin Address Allocation Manager previously would get confused after renaming an address pool. ---------------------------------------------------------------------- Bug-ID: SCO-559-1150 netconfig(ADM) was modified to more correctly edit TCP/IP configuration files to reflect values assigned via DHCP. It no longer writes transient netmask and broadcast values into /etc/default/tcp, and it now edits /etc/tcp to create an idle network interface which dhcpc(ADMN) can use. ---------------------------------------------------------------------- Bug-ID: SCO-559-1164 The mechanism by which multiple router daemons may be started has been changed. Multiple router daemons are required only for specific (usually advanced) purposes. In /etc/default/tcp, lines of the form "ROUTERDAEMON0=command arg", from 0 through 9, are executed at an appropriate point during TCP/IP startup. ---------------------------------------------------------------------- Bug-ID: SCO-559-1184 When dd(C) was used to write to a file opened with the O_APPEND flag, whose initial length was non-zero, and which had not yet been written to, it truncated the output file to an incorrect length. Example: echo goodbye > test.out (echo hello | dd) >> test.out cat test.out ---------------------------------------------------------------------- Bug-ID: SCO-559-1204 Bug-ID: SCO-559-1205 Bug-ID: SCO-559-1206 The scoadmin Internet Manager options for controlling anonymous FTP were inoperative in OpenServer 5.0.6. ---------------------------------------------------------------------- Bug-ID: SCO-559-565 An icon for mounting and unmounting the first CD has been added to the xdt3(XC) X.desktop. ---------------------------------------------------------------------- Bug-ID: SCO-559-919 more(C) has been replaced with the current version (358) of the open source pager "less", which provides many enhancements. One specific problem fixed since OpenServer 5.0.6: previously, more dumped core on receipt of a SIGWINCH signal (when a window size changed). ---------------------------------------------------------------------- Bug-ID: SCO-236-1727 malloc(S) was modified to gracefully handle requests for negative amounts of memory (by returning a NULL pointer, indicating failure). ---------------------------------------------------------------------- Bug-ID: SCO-236-1673 The C2 auditing subsystem was enhanced to allow the auditing of actions by a normal user who has used su(C) to become "root". This is controlled by the new kernel variable "audit_root" in the new file /etc/conf/pack.d/aud/space.c. ---------------------------------------------------------------------- Bug-ID: SCO-247-290 The automatic calculation of NHBUF has been made identical on single- and multi-processor systems. If the NHBUF kernel parameter is 0, it is now automatically set to the next power of 2 larger than the specified or automatically calculated value of NBUF. ---------------------------------------------------------------------- Bug-ID: SCO-559-1219 hw(ADM) was enhanced to recognize Intel Pentium 4 CPUs. ---------------------------------------------------------------------- Bug-ID: SCO-559-1012 Bug-ID: SCO-559-1163 Processor microcode updates have been included for newer Intel Pentium III and Pentium 4 processor models. ---------------------------------------------------------------------- Bug-ID: SCO-559-1067 Script errors were corrected in the video configuration scripts for NeoMagic MagicGraph, S3 Savage and S3 VirGE video chipsets. ---------------------------------------------------------------------- Bug-ID: SCO-231-514 A potential panic in the console driver's set-function-key facility was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-559-1069 A panic caused by attempting to exec login(M) was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-559-1078 A panic caused by the bootstring "wd.debug" was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-559-1097 A panic was corrected in the `ipl' (Network Address Translation) driver. The panic could be triggered by the new DHCP client, dhcpc(ADMN). ---------------------------------------------------------------------- Bug-ID: SCO-559-1101 A panic in the Sdsk(HW) SCSI hard disk driver, which happened when several hard disks or partitions were being opened and closed at the same time, was corrected. ---------------------------------------------------------------------- Bug-ID: SCO-559-1120 During a catastrophic kernel general protection fault, it was possible for the system to keep running in a potentially corrupted state instead of panicing like it was supposed to do. ---------------------------------------------------------------------- Bug-ID: SCO-247-302 The dptr(HW) host adapter driver was modified to access EISA I/O ports only on EISA machines, PCI I/O ports only on PCI machines, thus reducing the probability of a hang at "F dptr" during system boot. ---------------------------------------------------------------------- Bug-ID: SCO-559-1122 The Intel "eeE" network adapter driver was updated to Intel version 1.5.0. ---------------------------------------------------------------------- Bug-ID: SCO-559-1000 The IBM "trps" network adapter driver was updated to IBM version 2.14. _________________________________________________________________________ Sendmail 8.11.0 Supplement for OpenServer 5.0.6a _________________________________________________________________________ The Sendmail 8.11.0 Supplement provides Sendmail Release 8.11.0 for OpenServer(TM) systems. This document assumes that you are familiar with sendmail for OpenServer. For more information on these topics, consult the OpenServer manual pages and guides, which are accessible on-line with every OpenServer distribution using SCOhelp. The following updated sendmail documentation is included with Release Supplement 506A for OpenServer Release 5.0.6 systems: o the sendmail(ADMN) manual page o Chapter 5 "sendmail administration" in the Mail and Messaging Guide If you have questions regarding this supplement or the product on which it is installed please contact your software supplier. This document covers the following topics: o Highlights of this supplement o System requirements o Installing the supplement o Installing the supplement across the network o Removing the supplement o Affected files Highlights of this supplement This supplement includes the following Sendmail security enhancements: o Added vigilance for set*uid(), setgid(), setgroups(), initgroups(), and chroot() calls. o Outgoing (client-side) SMTP Authentication mechanisms limited to those specified in AuthMechanisms to prevent information leakage. NOTE: We do not recommend use of PLAIN for outgoing mail as it sends the password in clear text to possibly untrusted servers. See cf/README's DefaultAuthInfo section for additional information: http://www.sendmail.org/m4/readme.html o Safe file checks now backtrack through symbolic links. This ensures that the files cannot be compromised due to poor permissions on the parent directories of the symbolic link target. o Only root, TrustedUser, and users in class t can rebuild the alias map. o All file descriptors (besides stdin, stdout, and stderr) are closed before restarting sendmail. o AutoRebuildAliases (D) option deprecated; see also Affected files For more information, see the complete Sendmail 8.11.0 Release notes at the Sendmail Consortium website: http://www.sendmail.org/ System requirements This supplement can be installed on the following OpenServer releases: o OpenServer Release 5.0.6 with Release Supplement 506A You do not need to remove any supplements before installing the Sendmail 8.11.0 Supplement. Installing the supplement You can install the Sendmail 8.11.0 Supplement from distribution media (such as a CD-ROM or a floppy disk) or from media images on a software server or web site. NOTE: You must install Release Supplement 506A for OpenServer Release 5.0.6 systems before installing the Sendmail 8.11.0 Supplement. To install the supplement across the network, see this cover letter's section entitled ``Installing the supplement across the network''. To install the supplement: 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 Install New. 4 When prompted for the host (machine), select the current host and then Continue. 5 In the Select Media window: o If you are loading this release supplement from a media image, click on Media Device and select Media Images, then Continue. (You may need to pull down the scroll bar before you see the Media Images option.) In the Enter Image Directory window, enter the absolute pathname for the directory in which the media images reside; for example: /tmp Click on OK. o If you are loading this release supplement from a CD-ROM or floppy disk, select the appropriate drive and then Continue. 6 In the Install Selection window, select the Sendmail 8.11.0 Supplement. Click on Install. There is a short delay while the installation takes place. 7 In the Installation Complete window, click on OK. The Software Manager should list the supplements you selected. The patched software is now installed. 8 Exit the Software Manager by selecting Host, then Exit. Installing the supplement across the network You can install the supplement from one OpenServer Release 5.0.6 machine onto another across a TCP/IP network. To do so, you need a software server, which you can create as described in Chapter 21, "Installing and managing software over the network" in the Network Administration Guide. This server has a user account called swadmin. Use the Software Manager to install or load the Sendmail 8.11.0 Supplement on the software server. (See this cover letter's section entitled "Installing the supplement ".) To install the supplement onto a local machine 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 patch. Select From Another Host. You will need to provide the name of the software server, as well as the password of the swadmin user on the software server. Removing the supplement To remove the Sendmail 8.11.0 Supplement: 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 title of the supplement you are removing. 4 From the Software menu, select Remove Software. In the confirmation window, verify that you selected the right supplement, then click on Remove. There is a short delay, then the Removal complete window appears. Click on OK. The Software Manager should no longer list the supplement you removed. 5 When you have finished removing and installing software, exit the Software Manager by selecting Host, then Exit. Affected files The Sendmail 8.11.0 Supplement changes the following files. If you are updating sendmail, you might need to backup these files before installing the new supplement: /usr/lib/sendmail.d/sendmail.src Sendmail 8.11.0 Supplement provides a new version of this default configuration file. If you have customized sendmail.src in a previous release, you must back up this file and apply any modifications to the new file. /usr/lib/sendmail.cf The sendmail startup script /etc/init.d/sendmail now rebuilds the aliases database before startup. This obsoletes the function of the AutoRebuildAliases (D) option in the sendmail.cf file, where it is commented out by default. You might need to save other customizations to the sendmail.cf file. ----------------------------------------------------------------------- Document Version: 8.11.0a 5 February 2001 ____________________________________________________________________________ USB Supplement for OpenServer 5.0.6a ____________________________________________________________________________ The USB Supplement provides Universal System Bus (USB) support for OpenServer(TM) systems. If you have questions regarding this supplement or the product on which it is installed please contact your software supplier. This document covers the following topics: * Highlights of this supplement * System requirements * Installing the supplement * Installing the supplement across the network * Removing the supplement * Affected files * Configuring USB devices * Known limitations ---------------------------------------------------------------------------- Highlights of this supplement This USB release includes support for USB hubs, keyboards, mice, and mass storage devices. For more information, see the usb(HW) manual page when Release Supplement 506A for OpenServer Release 5.0.6 systems is installed. Further device support, including bootable devices, will be included in a future release. ---------------------------------------------------------------------------- System requirements This supplement can be installed on the following OpenServer releases: * OpenServer Release 5.0.6 with Release Supplement 506A You do not need to remove any supplements before installing the USB Supplement. ---------------------------------------------------------------------------- Installing the supplement You can install the USB Supplement from distribution media (such as a CD-ROM or a floppy disk) or from media images on a software server or web site. ---------------------------------------------------------------------------- NOTE: You must install Release Supplement 506A for OpenServer Release 5.0.6 systems before installing the USB Supplement. The USB Supplement is a software patch. For more information about managing patches, see "About software patches" in the OpenServer Handbook. To install the supplement across the network, see this cover letter's section entitled ``Installing the supplement across the network''. ---------------------------------------------------------------------------- To install the supplement: 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 Install New. 4. When prompted for the host (machine), select the current host and then Continue. 5. In the Select Media window: o If you are loading this release supplement from a media image, click on Media Device and select Media Images, then Continue. (You may need to pull down the scroll bar before you see the Media Images option.) In the Enter Image Directory window, enter the absolute pathname for the directory in which the media images reside; for example: /tmp Click on OK. o If you are loading this release supplement from a CD-ROM or floppy disk, select the appropriate drive and then Continue. 6. In the Install Selection window, select the USB Supplement. Click on Install. There is a short delay while the installation takes place. 7. In the Installation Complete window, click on OK. The Software Manager should list the supplements you selected. The patched software is now installed. 8. Exit the Software Manager by selecting Host, then Exit. ---------------------------------------------------------------------------- Installing the supplement across the network You can install the supplement from one OpenServer Release 5.0.6 machine 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 Networking Guide. This server has a user account called swadmin. Use the Software Manager to install or load the USB Supplement on the software server. (See this cover letter's section entitled "Installing the supplement ".) To install the supplement onto a local machine 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 patch. Select From Another Host. You will need to provide the name of the software server, as well as the password of the swadmin user on the software server. ---------------------------------------------------------------------------- Removing the supplement To remove the USB Supplement: 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 title of the supplement you are removing. 4. From the Software menu, select Remove Software. In the confirmation window, verify that you selected the right supplement, then click on Remove. ----------------------------------------------------------------------- CAUTION: Removing a supplement (patch) in the current OpenServer release corresponds to rolling it back and unloading it in earlier OpenServer releases. If you need to keep a copy of a patch loaded, click on More Options in the Confirm Selected Software window. Then, specify Leave Loaded, and click on Remove. Some effects of certain supplements are irreversible because of the nature of the correction (for example, restoring correct permissions on system directories). However, removing the supplement will remove the patch name from the system. ----------------------------------------------------------------------- There is a short delay, then the Removal complete window appears. Click on OK. The Software Manager should no longer list the supplement you removed. 5. When you have finished removing and installing software, exit the Software Manager by selecting Host, then Exit. ---------------------------------------------------------------------------- Affected files The USB Supplement changes the following files: /etc/conf/pack.d/kernel/os.a adds a call to usb_daemon() /etc/conf/cf.d/mevent adds entries for the 6 DSP's /usr/lib/event/devices adds entries for USB keyboard and mouse /usr/lib/mkdev/mouse adds code for adding USB devices /etc/default/scsihas adds an entry for usbha, for mass storage /usr/include/sys/usb this is a new header directory /usr/include/sys/usb/sco_port.hthis is the first USB header file shipped /usr/bin/usbtree new USB device display command There are six kernel Driver Software Packages (DSPs): uhci the host controller code usb the core USB protocol stack and daemon usbhathe psuedo SCSI controller for mass storage devices umsa the mouse class driver ukbd the keyboard class driver umassthe mass storage class driver ---------------------------------------------------------------------------- Configuring USB devices This section provides information about: * ``USB BIOS support'' * ``USB boot time messages'' * ``Configuring a USB keyboard'' * ``Configuring a USB mouse'' * ``Configuring a USB mass storage device'' * ``Preparing additional USB removable media'' * ``Monitoring USB devices'' USB BIOS support USB support is provided by controllers embedded on the motherboard. USB UHCI controllers (see ``Controller interface support'') are currently available from two vendors: Intel(TM) and VIA Technologies. The setup of these USB controllers during the boot process, also know as "Power On Self Test" (POST), is critical to USB subsystem operation. Many differences have been observed between BIOS vendors -- such as AMI, Phoenix and Award -- with corresponding behavior in the embedded controllers. You must therefore review each host's USB setup before trying to use USB software. To enter your system's setup menu, enter the appropriate key sequence (usually the key) during the boot process. Consult your hardware documentation for the location of the USB controls in your system's setup menus. ---------------------------------------------------------------------------- NOTE: Under normal circumstances, the USB controller must be enabled during system setup. However, if USB does not function properly after enabling it in setup, try disabling USB in setup. This has been found to remedy the problem in some systems. ---------------------------------------------------------------------------- USB boot time messages Boot time messages provide useful information about USB subsystem status. The following sample boot messages indicate: %usb 0xEF80-0xEF92 17 - USB Rev 1.1 Intel Chipset USB is configured at IOBase 0xEF80, is using IRQ 17, supports USB Specification 1.1, and uses an Intel USB Chipset. %usb 0xEF80-0xEF92 17 - USB Rev 1.1 VIA Chipset USB is configured and uses an VIA USB Chipset. WARNING: UHCI: invalid PCI line 255, USB disabled BIOS support for USB is not enabled. To continue, enable USB in setup. Configuring a USB keyboard No configuration is necessary to enable an attached keyboard on the USB bus. ---------------------------------------------------------------------------- NOTE: The USB keyboard will only be enabled if there is no PS2 keyboard found during boot and if USB legacy keyboard support is an option in USB setup. With USB legacy keyboard enabled in setup (during POST), regular 8042 keyboard controller signals are remapped to the connected USB keyboard. ---------------------------------------------------------------------------- Configuring a USB mouse To configure a USB mouse, use the Hardware/Kernel Manager or mkdev mouse command as described in ``Adding mice and bitpads'' in the OpenServer Handbook. After selecting a USB mouse from a list of supported devices, you are prompted to associate multiscreens and terminals with the device. When you have finished, you must relink the kernel and reboot for your changes to take effect. If you wish to use usemouse(C) or another application or utility that uses pseudo-ttys, you must add a suitable number of pseudo-tty devices to the system using the mkdev ptty command. For more information, see the mkdev(ADM) manual page. After reboot, the USB mouse will work with scologin. You can also test the new mouse configuration with the usemouse(C) program by entering: usemouse -c "vi /tmp/install.sh" Configuring a USB mass storage device Because USB mass storage support is integrated through the SCSI subsystem, USB mass storage devices can be added like SCSI disks, as described in ``Configuring a SCSI hard disk'' in the OpenServer Handbook. To configure a USB mass storage device, you must: 1. configure the USB device; that is, associate the device with the appropriate host adapter driver. 2. prepare the initial USB removable media. The installation procedure described here assumes a simple single filesystem configuration. See ``Adding hard disks'' in the OpenServer Handbook for additional configuration options. ---------------------------------------------------------------------------- NOTE: Only one USB mass storage device per system is supported in this USB release. Only Zip mass storage devices have been tested for this USB release; other removable media devices have not been tested. During this installation, it is assumed that writable media is inserted in the drive. The results of this installation will prepare the currently mounted media for filesystem use. Once that media is removed and virgin media inserted, the media preparation process must be repeated. To prepare additional virgin media, see ``Preparing additional USB removable media'' Do not repeat these initial configuration steps; doing so may disable your USB mass storage device. ---------------------------------------------------------------------------- Configuring the USB host adapter driver Use the Hardware/Kernel Manager or the mkdev hd command to configure the USB host adapter as described in ``Configuring a SCSI hard disk'' in the OpenServer Handbook. 1. Enter the following information when prompted: prefix of the SCSI host adapter usbha 'usbha' SCSI host adapter that supports this device 0 SCSI Bus 0 Target ID 0 LUN (Logical Unit Number) 0 2. Confirm the information you entered: Host Adapter Adapter Type Device Number ID LUN BUS ---------------------------------------------- usbha Sdsk 0 0 0 0 3. After relinking and rebooting the new kernel as prompted, you must prepare the media as described in the next section. Preparing the initial USB media Use the Hardware/Kernel Manager or the mkdev hd command to prepare your USB media following the instructions for SCSI devices in ``Installing a hard disk'' in the OpenServer Handbook. 1. Enter the same device information as requested during driver configuration: Host Adapter Adapter Type Device Number ID LUN BUS ---------------------------------------------- usbha Sdsk 0 0 0 0 2. Proceed to partition the drive. When prompted, select 2. Use Entire Disk for UNIX. 3. A partition table similar to the following is displayed: Current Hard Disk Drive: /dev/rdsk/1s0 +-------------+----------+-----------+---------+---------+---------+ | Partition | Status | Type | Start | End | Size | +-------------+----------+-----------+---------+---------+---------+ | 1 | Active | UNIX | 1 | 6079 | 6079 | +-------------+----------+-----------+---------+---------+---------+ Total disk size: 6144 tracks (65 reserved for masterboot and diagnostics) Confirm this display to continue. 4. Device information similar to the following is displayed: scsi version = 7 vendor = IOMEGA product = ZIP 100 Enter q to confirm and continue. 5. To lay out the filesystems and swap area, enter n to name a division. 6. When prompted, enter: division number 0 division name zip100 (or relevant name of your choice) 7. A divvy table similar to the following is displayed: +-------------------+------------+--------+---+-------------+------------+ | Name | Type | New FS | # | First Block | Last Block | +-------------------+------------+--------+---+-------------+------------+ | zip100 | HTFS | yes | 0 | 0| 96255| | | NOT USED | no | 1 | -| -| | | NOT USED | no | 2 | -| -| | | NOT USED | no | 3 | -| -| | | NOT USED | no | 4 | -| -| | | NOT USED | no | 5 | -| -| | | NOT USED | no | 6 | -| -| | d1257all | WHOLE DISK | no | 7 | 0| 97263| +-------------------+------------+--------+---+-------------+------------+ 96256 1K blocks for divisions, 1008 1K blocks reserved for the system Confirm this display to continue, and enter i[nstall] to install the division set-up shown. 8. When you are informed that hard disk initialization is complete, verify that the filesystem has been created using the newly created raw device file for fsck(ADM): # fsck /dev/rzip100 The display should be similar to the following: HTFS File System: zip100 Volume: zip100 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Synchronous Write Log ** Phase 6 - Check Free List Bitmap 2 files 15 blocks 93230 free 9. Mount the block device as a filesystem: # mount /dev/zip100 /mnt The device is now configured and the mounted filesystem is ready for use. Preparing additional USB removable media After initial configuration of your USB mass storage device and removable media, use the fdisk and divvy commands to prepare additional virgin media: 1. Create a new disk partition on the removable media: # fdisk -f /dev/rhd*0 Replace the asterisk with the appropriate device number for your system. 2. Create divisions on the new disk partition: # divvy -m /dev/hd*a Enter the division number (usually 0) and a division name (for example, zip100 or other name of your choice). 3. Verify that the filesystem has been created using the newly created raw device file for fsck(ADM): # fsck /dev/rzip100 4. Mount the block device as a filesystem: # mount /dev/zip100 /mnt For more information, see the fdisk(ADM) and divvy(ADM) manual pages. Monitoring USB devices Once USB is running, the usbd daemon will show up in the process tree. To display process information about usbd, enter: ps -ef | grep usbd usbtree is a USB runtime status utility that reports USB targets found on the USB bus. ---------------------------------------------------------------------------- Known limitations USB BIOS legacy support We have observed great variety in the levels of USB support in host Setup from one computer to another. The range includes: * no USB support * USB controller only * USB controller and keyboard only * USB controller, keyboard, and mouse only * USB controller enables ports 0 & 1, ports 2 & 3, or all ports (note four USB root hub ports on this Intel configuration) Controller interface support This USB release supports the Universal Host Controller Interface (UHCI) protocol specification. Open Host Controller Interface (OHCI) and Enhanced Host Controller Interface (EHCI) specifications are not supported. Consult your hardware documentation for USB controller interface(s) supported on your system. Compaq system support If you are installing the USB supplement on a Compaq system, we recommend installing only on systems with UHCI hardware support. Problems have been noted on Compaq systems with other controller interfaces. Ross OHCI chipset is not supported If a Ross Technology chipset is detected on your system, USB support is disabled. USB keyboard does not support scodb The USB keyboard is not supported for use with scodb, the kernel debugger tool. Bus power management does not handle power-free devices correctly USB provides for shared power devices on a single bus. That is, some USB function devices (such as hubs) may have their own power supply or may take a share of the power available form the USB bus itself. The lookup and management of this power sharing process is not always handled correctly. This is a bug and will be fixed in a future release. USB 1.1 specification does not support USB 2.0 devices Ordinarily, any USB device may be connected to the USB bus where it will be enumerated, activated, and become ready for use. Some USB 2.0 specification devices have been found to not work properly. ---------------------------------------------------------------------------- Document Version: 5.0.6a 26 February 2001 _____________________________________________________________________________ (c) 2001 The Santa Cruz Operation, Inc. All rights reserved. This publication is protected under copyright laws and international treaties. (c) 1976-2001 The Santa Cruz Operation, Inc.; (c) 1989-1994 Acer Incorporated; (c) 1989-1994 Acer America Corporation; (c) 1990-1994 Adaptec, Inc.; (c) 1993 Advanced Micro Devices, Inc.; (c) 1990 Altos Computer Systems; (c) 1992-1994 American Power Conversion, Inc.; (c) 1988 Archive Corporation; (c) 1990 ATI Technologies, Inc.; (c) 1976-1992 AT&T; (c) 1992-1994 AT&T Global Information Solutions Company; (c) 1993 Berkeley Network Software Consortium; (c) 1985-1986 Bigelow & Holmes; (c) 1988-1991 Carnegie Mellon University; (c) 1989-1990 Cipher Data Products, Inc.; (c) 1985-1992 Compaq Computer Corporation; (c) 1987-1994 Computer Associates, Inc.; (c) 1986-1987 Convergent Technologies, Inc.; (c) 1990-1993 Cornell University; (c) 1985-1994 Corollary, Inc.; (c) 1990-1994 Distributed Processing Technology; (c) 1991 D.L.S. Associates; (c) 1990 Free Software Foundation, Inc.; (c) 1989-1991 Future Domain Corporation; (c) 1994 Isogon Corporation; (c) 1991 Hewlett-Packard Company; (c) 1994 IBM Corporation; (c) 1990-1993 Intel Corporation; (c) 1989 Irwin Magnetic Systems, Inc.; (c) 1988-1991 JSB Computer Systems Ltd.; (c) 1989-1994 Dirk Koeppen EDV- Beratungs-GmbH; (c) 1989-1991 Massachusetts Institute of Technology; (c) 1985-1992 Metagraphics Software Corporation; (c) 1980-1994 Microsoft Corporation; (c) 1984-1989 Mouse Systems Corporation; (c) 1989 Multi-Tech Systems, Inc.; (c) 1991 National Semiconductor Corporation; (c) 1990 NEC Technologies, Inc.; (c) 1989-1992 Novell, Inc.; (c) 1989 Ing. C. Olivetti & C. SpA; (c) 1989-1992 Open Software Foundation, Inc.; (c) 1988-1994 Platinum Technology, Inc.; (c) 1993-1994 Programmed Logic Corporation; (c) 1989 Racal InterLan, Inc.; (c) 1990-1992 RSA Data Security, Inc.; (c) 1987-1994 Secureware, Inc.; (c) 1990 Siemens Nixdorf Informationssysteme AG; (c) 1991-1992 Silicon Graphics, Inc.; (c) 1987-1991 SMNP Research, Inc.; (c) 1987-1994 Standard Microsystems Corporation; (c) 1984-1994 Sun Microsystems, Inc.; (c) 1987 Tandy Corporation; (c) 1992-1994 3COM Corporation; (c) 1987 United States Army; (c) 1979-1993 Regents of the University of California; (c) 1993 Board of Trustees of the University of Illinois; (c) 1989-1991 University of Maryland; (c) 1986 University of Toronto; (c) 1988 Wyse Technology; (c) 1992-1993 Xware; (c) 1983-1992 Eric P. Allman; (c) 1987-1989 Jeffery D. Case and Kenneth W. Key; (c) 1985 Andrew Cherenson; (c) 1989 Mark H. Colburn; (c) 1993 Michael A. Cooper; (c) 1982 Pavel Curtis; (c) 1987 Owen DeLong; (c) 1989-1993 Frank Kardel; (c) 1993 Carlos Leandro and Rui Salgueiro; (c) 1986-1988 Larry McVoy; (c) 1992 David L. Mills; (c) 1992 Ranier Pruy; (c) 1986-1988 Larry Wall; (c) 1992 Q. Frank Xia. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of The Santa Cruz Operation, Inc. Business/21, dbXtra, DiSCOver, Internet Way of Computing, IWoC, Multiscreen, ODT, Open Desktop, Optimized For Internet Computing and its logo, Panner, SCO, SCO ACE, SCO CIFS Bridge, SCO Doctor, SCO Doctor for Networks, SCO Global Access, the SCO logos, SCO MPX, SCO MultiView, SCO Nihongo OpenServer, SCO OK, the SCO OK logo, OpenServer, SCO Open Server, SCO Portfolio, SCO POS System, SCO Premier Motif, SCO TermLite, SCO ToolWare, SCOtopia, SCO Vision97, SCO VisionFS, SCO Visual Tcl, Skunkware, Tarantella, the Tarantella logo, The Business Choice, The Santa Cruz Operation, UnixWare, Universal Server, VP/ix and Zones are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. APC, SoftCare and SoftTech are service marks of The Santa Cruz Operation, Inc. Deskterm, Deskworks, IXI, IXI Desktop, the IXI logo, IXI Panorama, Wintif, and X.desktop are trademarks or registered trademarks of IXI Limited, a subsidiary of The Santa Cruz Operation, Inc. X.tra is a service mark of IXI Limited. Codon, Devkit.Vision, Esprit, Kodon, PC- Connect, SQL-Retriever, SuperVision, Super.Vision, TermVision, Term.Vision, Vision Builder, Visionware, Visionware Direction, the Visionware logo, Visionware SQL-Retriever, Visionware Super.Vision, the XV logo, XVision, and X-Visionware are trademarks or registered trademarks of Visionware Limited, a subsidiary of The Santa Cruz Operation, Inc. X/Open and UNIX are registered trademarks and the X Device is a trademark of The Open Group in the United States and other countries. Cheyenne and ARCserve are registered trademarks of Cheyenne Software, Inc. Netscape, Netscape Navigator, Netscape Communications Server, Netscape Commerce Server, Netscape LiveWire, Netscape Proxy Server, Netscape FastTrack Server, Netscape Enterprise Server, Netscape SuiteSpot, Netscape Catalog Server, Netscape News Server, Netscape Mail Server, and Netscape Navigator Gold are trademarks or registered trademarks of Netscape Communications Corporation. NFS was developed by Computer Associates, Inc. (formerly Lachman Associates, Inc. and Legent Corporation) based on LACHMAN SYSTEM V NFS. LACHMAN is a trademark of Legent Corporation. NFS is a trademark of Sun Microsystems, Inc. TCP/IP was developed by Computer Associates, Inc. (formerly Lachman Associates, Inc. and Legent Corporation) based on LACHMAN SYSTEM V STREAMS TCP, a joint development of Lachman Associates and Convergent Technologies. MPX was developed by Corollary, Inc. VP/ix is a product developed and licensed by Phoenix Technologies, Ltd/INTERACTIVE Systems Corporation. XRemote is a registered trademark of Network Computing Devices, Inc. Oracle is a registered trademark of Oracle Corporation, Redwood City, California. Sun, Sun Microsystems, Java, Java Workshop, and Java Studio are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries, and are used under license. Adobe is a trademark of Adobe Systems Incorporated and is registered in the U.S. Patent and Trademark Office. Reliant is a registered trademark of Siemens Pyramid Information Systems, Inc. (formerly Pyramid Technology Corporation). Real bubble logo, RealNetworks, RealSystem, RealAudio, RealVideo, RealPlayer, Basic Server Plus, RealEncoder, and RealPublisher are trademarks or registered trademarks of RealNetworks, Inc. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners. The Santa Cruz Operation, Inc. and SCO Skunkware are not related to, affiliated with or licensed by the famous Lockheed Martin Skunk Works(r), the creator of the F-117 Stealth Fighter, SR-71, U-2, Venturestar(TM), Darkstar(TM), and other pioneering air and spacecraft. The SCO software that accompanies this publication is commercial computer software and, together with any related documentation, is subject to the restrictions on US Government use as set forth below. If this procurement is for a DOD agency, the following DFAR Restricted Rights Legend applies: RESTRICTED RIGHTS LEGEND: When licensed to a U.S., State, or Local Government, all Software produced by SCO is commercial computer software as defined in FAR 12.212, and has been developed exclusively at private expense. All technical data, or SCO commercial computer software/documentation is subject to the provisions of FAR 12.211 - "Technical Data", and FAR 12.212 - "Computer Software" respectively, or clauses providing SCO equivalent protections in DFARS or other agency specific regulations. Manufacturer: The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, CA 95060. The copyrighted software that accompanies this publication is licensed to the End User only for use in strict accordance with the End User License Agreement, which should be read carefully before commencing use of the software. Document Version: 5.0.6A 5 February 2001 ----------------------------------------------------------------------------