SCO UnixWare 2.1.3 Installation and Release Notes About this book 1 How this book is organized .......................................... 1 Related documentation ............................................... 2 Typographical conventions ........................................... 2 How can we improve this book? ....................................... 3 Chapter 1 Introduction 5 Single UNIX Specification ........................................... 6 Chapter 2 Installation 7 Carrying out a full installation .................................... 7 Chapter 3 Updating your system 9 Preparing to install ................................................ 9 FTP installation of update213 ...................................... 10 Downloading from an FTP server .................................. 10 Installing update213 from FTP ................................... 11 CD-ROM installation of update213 ................................... 12 Contents of the update on the Installation CD-ROM ............... 12 Installing update213 from the Installation CD-ROM ............... 13 Chapter 4 After installation 15 Add-on packages .................................................... 15 Installing add-on packages ...................................... 16 Removing add-on packages ........................................ 17 Removing update packages ........................................... 17 Chapter 5 Documentation release notes 19 Multiple instances of applications ................................. 19 Setting MEMRANGE ................................................... 20 Chapter 6 Software release notes 23 BIOS extension ..................................................... 23 FTP transfer on ................................................... 23 BIND ............................................................... 23 TCP/IP RIP-2 ....................................................... 24 New tunables ....................................................... 24 System panic dump generation .................................... 25 UNIX95 .......................................................... 25 TCP/IP keepalive ................................................ 25 Encryption Utilities ............................................... 26 Appendix A Enhancements and fixes 27 Enhancements in the update213 package .............................. 27 Appendix B Compatibility 31 Source code ........................................................ 31 Commands and utilities ............................................. 32 Sockets ............................................................ 34 ksh93 versus ksh88 ................................................. 35 /u95/bin ........................................................... 36 Appendix C Single UNIX Specification 39 The X/Open specification ........................................... 39 The POSIX.2 shell (ksh93) .......................................... 40 Compliant compilation environment .................................. 40 X/Open curses ...................................................... 41 Single UNIX Specification manual pages ............................. 41 Enabling the Single UNIX Specification during installation ......... 42 Enabling the Single UNIX Specification after installation .......... 42 Setting RSTCHOWN ................................................ 42 Setting the default shell ....................................... 43 Setting the login shell ......................................... 43 Disabling the Single UNIX Specification ............................ 43 Resetting RSTCHOWN .............................................. 44 Resetting the default shell ..................................... 44 Resetting the login shell ....................................... 44 Appendix D Installing the Installing the drivers from CD-ROM ................................. 45 Creating an IHV diskette from CD-ROM ............................ 45 Installing hba213 drivers from CD-ROM ........................... 46 Installing nic213 drivers from CD-ROM ........................... 46 Installing the drivers from FTP .................................... 47 Creating an IHV diskette from FTP ............................... 47 Installing hba213 drivers from FTP .............................. 47 Installing nic213 drivers from FTP .............................. 47 Appendix E SCO online services information 49 World Wide Web (WWW) ............................................... 49 SCO's Online Support ( ............................................. 50 ompuServe ....................................................... 51 Anonymous FTP ................................................... 51 Anonymous UUCP .................................................. 52 Ftpmail ......................................................... 53 InfoFax ......................................................... 53 ------------------------------------------------------------------------------ © 1983 - 1998 The Santa Cruz Operation, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, California, 95060, USA. Copyright infringement is a serious matter under the United States and foreign Copyright Laws. 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. SCO, the SCO logo, The Santa Cruz Operation, and SCO UnixWare are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. UNIX is a registered trademark of The Open Group, in the USA and other countries. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners. SCO® UnixWare® 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. If any copyrighted software accompanies this publication, it 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: 2.1.3 24 April 1998 ------------------------------------------------------------------------------ About this book This book provides the information you need to get your SCO® UnixWare® 2.1.3 system up and running. It includes instructions for installing update213 on existing UnixWare systems and for installing fresh systems. The FTP and CD-ROM installation channels are described in detail. You will find the information you need more quickly if you are familiar with: + ``How this book is organized'' + ``Related documentation'' + ``Typographical conventions'' Although we try to present information in the most useful way, you are the ultimate judge of how well we succeed. Please let us know how we can improve this book. How this book is organized After introducing the SCO UnixWare 2.1.3 product, this book describes how to: + carry out a full installation + upgrade an existing UnixWare system + administer update and add-on packages after installation The next two chapters list known release issues for: + documentation + software The appendixes describe: + enhancements in the SCO UnixWare 2.1.3 package + source code, command utility, shell and sockets compatibility + conformance to the Single UNIX Specification + installing the HBA and NICS drivers + SCO online support services ------------------------------------------------------------------------------ Related documentation The SCO UnixWare 2.1.3 documentation may reference the Release 2.1 SCO UnixWare Installation Handbook, which remains valid for the SCO UnixWare 2.1.3 product. Note, however, that the Release Notes that accompanied that title are supplemented by these SCO UnixWare 2.1.3 Installation and Release Notes. Typographical conventions This publication presents commands, filenames, keystrokes, and other special elements as shown here: Example: Used for: lp or lp(1) commands, device drivers, programs, and utilities (names, icons, or windows); the letter in parentheses indicates the reference manual section in which the command, driver, program, or utility is documented /new/client.list files, directories, and desktops (names, icons, or windows) root system, network, or user names filename placeholders (replace with appropriate name or value) keyboard keys Exit program? system output (prompts, messages) yes or yes user input ``Description'' field names or column headings (on screen or in database) Cancel button names Edit menu names Copy menu items File != Find != Text sequences of menus and menu items open or open(2) library routines, system calls, kernel functions, C keywords; the letter in parentheses indicates the reference manual section in which the file is documented $HOME environment or shell variables SIGHUP named constants or signals ``adm3a'' data values employees database names orders database tables buf C program structures b_b.errno structure members How can we improve this book? What did you find particularly helpful in this book? Are there mistakes in this book? Could it be organized more usefully? Did we leave out information you need or include unnecessary material? If so, please tell us. To help us implement your suggestions, include relevant details, such as book title, section name, page number, and system component. We would appreciate information on how to contact you in case we need additional explanation. _________________________________________________________________________ NOTE For answers to technical questions, please contact your software vendor or your support representative. Technical Publications is not qualified to give technical support. _________________________________________________________________________ To contact us, write to us at: Technical Publications Attn: Customer Feedback Team The Santa Cruz Operation, Inc. PO Box 1900 Santa Cruz, California 95061-9969 USA or email us at: techpubs@sco.com or ... uunet!sco!techpubs Thank you. ------------------------------------------------------------------------------ Chapter 1 Introduction This document supplements Release 2.1 of the SCO UnixWare Installation Handbook. It describes the SCO UnixWare 2.1.3 release and the SCO UnixWare 2.1.3 update package, ``update213''. It also provides information about the SCO UnixWare 2.1.3 Host Bus Adapter (``hba213'') driver package and the Network Interface Card support image (``nic213''). Installed as an incremental update, the update213 package provides enhancements and fixes for SCO UnixWare 2.1, 2.1.1 and 2.1.2. Installed as a new system, it replaces and supersedes the 2.1, 2.1.1 and 2.1.2 releases. It also contains optionally installable SCO UnixWare add-on products and contains the fixes previously only available by installing Program Temporary Fixes (PTFs). For more details, see Appendix A, ``Enhancements and fixes''. SCO UnixWare 2.1.3 is available on CD-ROM. In addition, the core update213 package is available from the SCO FTP server. For details, see Chapter 3, ``Updating your system''. Detailed procedures for installing SCO UnixWare 2.1.3 are given in Chapter 2, ``Installation''. SCO recommends that you review these notes for information that may affect your system before attempting to install either a fresh system or the update package. Single UNIX Specification SCO UnixWare 2.1.3 contains X/Open(TM) Single UNIX(r) Specification (referred to hereafter as ``UNIX95'') capabilities and has been branded as a UNIX95-compliant product. The UNIX95 environment provided with SCO UnixWare 2.1.3 is optional. With UNIX95 enabled, your system should fulfill the requirements of a UNIX95- compliant product. Applications developed in this environment are portable to a wide range of UNIX systems. For more information about SCO UnixWare 2.1.3 UNIX95 and how to enable it, see Appendix C, ``Single UNIX Specification''. ------------------------------------------------------------------------------ Chapter 2 Installation You may start with a full installation of SCO UnixWare 2.1.3, or else update any existing installation of SCO UnixWare 2.1, 2.1.1 or 2.1.2. To update any of these existing systems, refer to Chapter 3, ``Updating your system''. The remainder of this chapter describes how to carry out a full installation. _________________________________________________________________________ NOTE Note that if there is anything valuable on your system, SCO recommends that you perform a full system backup before following the procedures described in this chapter. _________________________________________________________________________ Carrying out a full installation The steps required to carry out a full installation of SCO UnixWare 2.1.3 are as follows: 1. Insert the SCO UnixWare 2.1.3 Installation diskette. 2. Reboot your system and follow the on-screen instructions. A detailed description of the installation procedure is provided in Chapter 2, ``Installing the SCO UnixWare Operating system'', of the Release 2.1 SCO UnixWare Installation Handbook. However, the following changes to that documentation are necessary: + The ``Host Bus Adapter diskette'' (in Step 11 of that procedure) should be substituted with ``UnixWare 2.1.3 Host Bus Adapter diskette''. + Step 15 uses the ``UnixWare 2.1.3 Network Installation Utilities diskette''. For troubleshooting information, see Chapter 1, ``Before you begin'', and Appendix H, ``Troubleshooting'', of the Release 2.1 SCO UnixWare Installation Handbook. _________________________________________________________________________ NOTE Be careful when deselecting the default packages as some of them are required for successful installation of the Internet Services. _________________________________________________________________________ Go to Chapter 4, ``After installation'' for details of add-on packages and additional products. ------------------------------------------------------------------------------ Chapter 3 Updating your system This chapter describes the update process for existing installations of SCO UnixWare 2.1, 2.1.1 and 2.1.2. For details of a fresh installation, see Chapter 2, ``Installation''. The update may either be downloaded from an FTP site, or from CD-ROM. Note, however, that the CD-ROM medium supplies add-on packages such as Internet Services that are not included when downloading only the update213 package from the FTP site. Preparing to install _________________________________________________________________________ NOTE Before installing the update213 package, SCO recommends that you create a full system backup. See also Chapter 1 of the Release 2.1 SCO UnixWare Installation Handbook. Although the installation and removal of update213 have been thoroughly tested, these procedures involve replacing key pieces of the underlying system software. If, for example, there is a power outage during installation, having emergency recovery media can facilitate restoration of your system. When installing update213, you should install in single-user mode or make sure no one else is using the system while you carry out the installation. This is recommended since networking and other software is replaced during the installation procedure. _________________________________________________________________________ The installation makes a copy of the files to be updated. The amount of free disk space that is required for these copies depends on the software that you currently have installed on your system. By default, the files are stored in /var/sadm/bkup/update213, but to save space on your hard disk, you may choose to save the backup on either diskettes or tape. _________________________________________________________________________ NOTE SCO recommends not using diskettes as up to 15 could be required. _________________________________________________________________________ It is not necessary to remove add-on packages before applying update213, as these will be properly updated without the need for removal. Any further add-on packages should be applied before applying update213, as this avoids reinstalling update213 and saves on installation time. To have a more detailed ``debug'' log created when installing SCO UnixWare 2.1.3, create a readable (mode 444) /var/sadm/installdbg file before installing update213. An installdbg.log file is then created with detailed installation debugging information. FTP installation of update213 This section describes the following: + downloading from an FTP server + installing the update213 package If you wish also to install the hba213 and nic213 drivers, refer to Appendix D, ``Installing the HBA and NICS drivers''. Downloading from an FTP server You can download part or all of update213 from an FTP server. To download SCO UnixWare 2.1.3 packages and images: 1. Log in to the FTP server as an anonymous user and provide your email address when prompted for a password: ftp ftp.sco.com name: anonymous Password: your email address 2. Set FTP binary mode: binary 3. Change to the update213 directory: cd UW21/upd213 4. Download the files you want, using the get command, as follows: upd213.pt1 Part 1 of update213 package. upd213.pt2 Part 2 of update213 package. upd213.pt* If there are more than two parts to the update213 package, download these as well. hba213.img Image of the hba213 packages diskette. nic213.img Image of nic213 drivers diskette. boot213.img Image of the boot diskette. upd213.txt File containing chksum information. eng213.txt English version of these Installation and Release Notes. fr213.txt French version of these Installation and Release Notes. de213.txt German version of these Installation and Release Notes. it213.txt Italian version of these Installation and Release Notes. es213.txt Spanish version of these Installation and Release Notes. ja213.txt Japanese version of these Installation and Release Notes. decvr.txt German version of the Cover Letter. engcvr.txt English version of the Cover Letter. frcvr.txt French version of the Cover Letter. itcvr.txt Italian version of the Cover Letter. escvr.txt Spanish version of the Cover Letter. jacvr.txt Japanese version of the Cover Letter. If a file transfer fails, repeat the get command to retry the download. 5. Compare checksums of the downloaded files with the checksums given in the upd213.txt file to verify a successful download. Installing update213 from FTP To install an update213 package downloaded from the FTP site, carry out the following steps: 1. If the upd213.pt* files are not already on the system where you want to install update213, make them available there (via tape, FTP, NFS, etc.). 2. cat the upd213.pt* files together and pipe them to the pkgadd utility, as follows: cat upd213.pt* | uncompress > upd213.str cat upd213.str | pkgadd -d- The package installation script prompts you from this point on. _________________________________________________________________________ NOTE During the update213 installation, you are offered an option to enable UNIX95. You should only enable UNIX95 if you have a need for a conforming environment. See Appendix B, ``Compatibility'' and Appendix C, ``Single UNIX Specification'' for details. During the update213 installation, when the binaries are being loaded onto the system, the following message may appear: UX:pkginstall: WARNING: filename This message can be ignored. It is an information message displayed by pkginstall(1M) when a hard link is being broken. _________________________________________________________________________ If you wish to go on to install the hba213 and nic213 drivers, refer to Appendix D, ``Installing the HBA and NICS drivers''. CD-ROM installation of update213 This section describes the following: + the contents of the Installation CD-ROM + installing the update213 package If you wish also to install the hba213 and nic213 drivers, refer to Appendix D, ``Installing the HBA and NICS drivers''. Contents of the update on the Installation CD-ROM The Installation CD-ROM contains the directory UW213. The Installation CD-ROM also contains an image of the SCO UnixWare 2.1 system. UW213 contains the following subdirectories and files: PKGS Contains the following: update213 The update213 package. hba213 The hba213 drivers with a subdirectory for each driver package. IMAGES Contains the following diskette images: nic213.img Image of the nic213 drivers. Use this to create an IHV diskette. hba213.img Image of the hba213 drivers. boot213.img Image of the boot diskette. DOCS Contains plain text copies of these Installation and Release Notes, in the following versions: eng213.txt English fr213.txt French de213.txt German it213.txt Italian es213.txt Spanish ja213.txt Japanese Installing update213 from the Installation CD-ROM To install update213 from the Installation CD-ROM using the pkgadd(1M) command, carry out the following steps: 1. Insert the CD-ROM into your CD-ROM drive and mount it as follows. mount -Fcdfs -r /dev/cdrom/device_name mount_point For example: mount -Fcdfs -r /dev/cdrom/c0b0t5l0 /mnt 2. Issue a pkgadd command to install update213. For example: pkgadd -d /mnt update213 The package installation script prompts you from this point on. _________________________________________________________________________ NOTE During the update213 installation, you are offered an option to enable UNIX95. You should only enable UNIX95 if you need a conforming environment. See Appendix B, ``Compatibility'' and Appendix C, ``Single UNIX Specification'' for details. _________________________________________________________________________ _________________________________________________________________________ NOTE During the update213 installation, when the binaries are being loaded onto the system, the following message may appear: UX:pkginstall: WARNING: filename This message can be ignored. It is an information message displayed by pkginstall(1M) when a hard link is being broken. _________________________________________________________________________ If you wish to go on to install the hba213 and nic213 drivers, refer to Appendix D, ``Installing the HBA and NICS drivers''. ------------------------------------------------------------------------------ Chapter 4 After installation This chapter provides information about removing update packages or images, and installing or removing add-on packages. _________________________________________________________________________ NOTE All procedures should be performed in single-user mode as superuser. _________________________________________________________________________ _________________________________________________________________________ NOTE If you did not create a back-up when installing update213, you can not pkgrm update213. _________________________________________________________________________ Add-on packages The following is a list of add-on packages updated by the update213 package: + Advanced Commands (``cmds'') + AST Manhattan SMP Support Utilities (``ast'') + Base System (``base'') + BSD Compatibility (``bsdcompat'') + C++ Compilation System (``C++'') + Compaq Support Utilities (``compaq'') + Desktop Manager (``desktop'') + Encryption Utilities (``crypt'') + Enhanced Application Compatibility (``acp'') + French Language Extension (``frle'') + German Language Extension (``dele'') + Graphics Display Support (``display'') + Graphics Utilities (``dtxt'') + Internet Utilities (``inet'') + Italian Language Extension (``itle'') + Japanese Language Extension (``jale'') + Kernel Debugger (``kdb'') + Motif Development Package (``mdev'') + Network File System Utilities (``nfs'') + Network Interface Card Support (``nics'') + Network Management (``netmgt'') + Network Support Utilities (``nsu'') + NetWare UNIX Client (``nuc'') + OA&M (``oam'') + Optimizing C Compilation System (``ccs'') + OS Multiprocessor Support (``osmp'') + Printer Support (``lp'') + Server Utilities (``server'') + Spanish Language Extension (``esle'') + Traditional Manual Pages (``manpages'') + SCO UnixWare 2.1 NetWare Services (``nwsrvr'') + SCO UnixWare 2.1 Japanese NetWare Services (``nwsrvrJ'') + VERITAS File System (``vxfs'') + VERITAS Volume Manager (``vxvm'') Installing add-on packages There is no need to remove the update213 package before adding an add-on package. If you install update213, and then later install an add-on package, you must reinstall update213 so that you pick up the latest enhancements and fixes for the add-on package. This is known as an ``overlay installation''. The update213 installation procedure offers an option to back up files before they are modified during installation. In the case of an overlay installation, the files from the add-on packages to be modified are backed up. SCO recommends that you always back up the files before you install or reinstall update213. The update contains incremental modifications to the base products as well as to optionally installable SCO UnixWare add-on packages. You must: 1. Install SCO UnixWare 2.1.3. 2. Install the add-on package. 3. Re-install SCO UnixWare 2.1.3. This update only updates the package-related files. _________________________________________________________________________ NOTE If the Advanced Commands (``cmds'') package is not already on your system and you want ksh93 or the Single UNIX Specification (UNIX95) environment, you must install it before applying update213. _________________________________________________________________________ Removing add-on packages To remove an add-on package that has been modified by update213, the recommended procedure is as follows: 1. Remove the update213 package, as described in ``Removing update packages''. 2. Remove the add-on package. 3. Reinstall the update213 package. If you attempt to remove the add-on package without removing update213 first, the add-on package is not fully removed. Removing update packages You can remove the update213 package using the pkgrm(1M) command. For example: pkgrm update213 The package installation script prompts you from this point on. If there are package dependencies that prevent you from removing a package, they are identified when you attempt to remove the package. You must first remove all dependent packages before you can successfully remove one of the SCO UnixWare 2.1.3 packages. ------------------------------------------------------------------------------ Chapter 5 Documentation release notes This chapter lists the modifications that need be made to components of the SCO UnixWare 2.1 documentation set. Multiple instances of applications The SCO UnixWare 2.1 documentation states that multiple instances of an application may be installed, and that on installing a second (or nth) package instance, the instance component of the package identifier is automatically incremented. It goes on to state that, subsequently, using this identifier, each instance can be removed from the system independently of any other instances. This is incorrect. To increment package instances, you begin by installing the package (using the pkgadd(1M) utility), called for example ``package''. Then, you create a second image of the package called ``package.1'', and install that version. This provides a variant of the package instance handling functionality described in the SCO UnixWare 2.1 documentation, because the identifiers are different. However, it is not then possible to remove one instance without also removing all of the others, as pkgrm(1M) does not correctly use the VERSION parameter (in the package characteristics file) to distinguish one instance from another. Accordingly, the following modifications should be made to Chapter 8 (``Packaging Your Software Applications'') of SCO UnixWare Software Development Tools: + In the section entitled ``Installation Parameters'', the description of PKGINST should be removed. + ``Step 2. Defining a Package Instance'' in the section entitled ``Basic Steps of Packaging'' should also be removed. + The pointer to this documentation given in the second item of the list in ``Basic Steps of Packaging'' should also be removed. The following manual pages in the Release 2.1 SCO UnixWare Command Reference should also be modified. In all cases, references to the inst component of the pkginst command line argument should be ignored. + installf(1M) + pkgadd(1M) + pkgask(1M) + pkgchk(1M) + pkginfo(1) + pkgmk(1) + pkgparam(1) + pkgrm(1M) + pkgtrans(1) + removef(1M) Similarly, the following manual pages supplied by the SCO UnixWare System Files and Devices Reference should be amended as described: + admin(4) References to the instance parameter should be ignored. + depend(4) References to the (arch)version field should be ignored. + pkginfo(4) References to the MAXINST parameter should be ignored. Setting MEMRANGE Step 3 of ``Panics or Resets While Booting From Install Diskette'' in Appendix H (``Troubleshooting'') of the SCO UnixWare Installation Handbook states that MEMRANGE should be set as follows: MEMRANGE=0-640K:256,1M-nM:16896 This contradicts the boot(4) manual page which states that the flags recognized for MEMRANGE are 256, 512 and 8704. The entry in the Installation Handbook is incorrect, and should read as follows: MEMRANGE=0-640k:256,1M-16M:512,16M-nnM:8704 ------------------------------------------------------------------------------ Chapter 6 Software release notes This chapter describes issues relating to the update213 software. Where possible, remedial action is suggested. BIOS extension If the BIOS extension is configured to support large scale disks (larger than 1024 cylinders), there are problems with emergency recovery. This is due to the emergency diskette which clears the partition table. As a result, the fdisk(1M) utility cannot restore saved partition geometry as a smaller number of cylinders is reported. SCO recommends that you disable the fdisk feature in the BIOS/hdd-controller configuration. FTP transfer on SCSI computers The FTP transfer of large files sometime fails on SCSI boxes with an Adaptec Host Bus Adapter (AHA-2940) configured in synchronous mode. To improve FTP transfer, reconfigure the SCSI controller to asynchronous mode. BIND This supplement includes named(1M), named-xfer and associated binaries from BIND 4.9.6. They have been released to address the security problems documented in the recent CERT advisory. See also the BIND operators guide (BIND-OP-Guide.ps) found in /var/adm. Please note that BIND 4.9.6 is more particular about the contents of your zone files and will stop errors missed by older versions of named. To update BIND 4.9.6: 1. Run BIND 4.9.6 on any primary name server you manage. 2. Check syslog (or osmlog) for any named warnings. 3. Clean up the zone files. 4. Move BIND 4.9.6 out onto the other UnixWare name servers you maintain. The BIND homepage is available at the following URL: http://www.isc.org/bind.html See syslogd(1M) for further details. TCP/IP RIP-2 This supplement contains TCP/IP RIP-2 functionality. This allows subnets to be used in routing policy decisions. This enables different subnet masks to be used on physically connected networks and allows packets to be successfully routed between different parts of the network. Most computer internetworks use the same class of addressing, with an implicit netmask, depending only on the class of the network address used. This limits the physical number of connections that can be made to such a network, and if physical space is limited it can cause a shortage of network addresses to occur. One way to avoid this shortage is to split a network into subnets of the same class of addresses. This allows several subnets to be used as the primary allocation method for network addresses. The maximum number of physical network addresses available within one of these subnets can be chosen by careful planning when designing the subnet layout. The physical number is limited by the number of bits used in the subnet mask. A full discussion of the routing choice and setup is beyond the scope of this text. However, this topic is covered in most reference materials on network management. New tunables This topic describes the new tunables in update 213. _________________________________________________________________________ NOTE Changing any default settings is NOT RECOMMENDED. _________________________________________________________________________ If these values are changed, the UnixWare kernel must be rebuilt to incorporate these changes. To do this, use the following command as root: /etc/conf/bin/idbuild -B After this command has been executed a system reboot will be needed to install the new kernel. See idbuild(1M) for more details. System panic dump generation These tunable parameters are associated with system panic dump generation. See crash(1M) for details. SYSDUMP_SELECTIVE The flag value that determines if the system will dump all pages (0), or selectively dump only pages mapped in the kernel (1). The default value is 1: to generate a selective dump, occupying much less space, rarely losing information. SYSDUMP_POLL The flag value that determines if the system will dump relying upon the disk interrupt (0), or poll for I/O completion (1). The default value is 1: to poll with disk interrupt disabled, lest it is shared with other devices which might stop the dump. UNIX95 PROCSET_ZOMBIES The FIPS PUB 151-2 NIST-PCTS specification requires kill(2) applied to a zombie process (or to a set of processes all of which are zombies) to succeed instead of failing with ESRCH: tune PROCSET_ZOMBIES from 0 to 1 for that behavior. TCP/IP keepalive These tunables are in /etc/conf/pack.d/tcp/space.c. If a connection is idle (no segments received) for TCP_TV_KEEP_INIT amount of time, but not yet established, then the connection is dropped. Once the connection is established, if the connection is idle for TCP_TV_KEEP_IDLE time (and keepalives have been enabled on the socket), the connection is probed. The peer is forced to send a segment by sending: This segment is (deliberately) outside the window, and should elicit an ACK segment in response from the peer. If there is no response to the first probe, a maximum of TCP_TV_KEEPCNT probes will be sent at TCP_TV_KEEPINTVL intervals. If, despite the keepalive initiated segments, there is no response from the peer, the connection is dropped after TCP_TV_KEEPCNT probes. Encryption Utilities _________________________________________________________________________ NOTE This information is applicable to U.S. and Canadian customers only. _________________________________________________________________________ International versions of the Encryption Utilities (``crypt'') are updated automatically by update213. If you use (or wish to use) domestic Encryption Utilities, please call SCO at (800) SCO-UNIX and request the UnixWare Encryption Utilities Update 2.1.3. ------------------------------------------------------------------------------ Appendix A Enhancements and fixes This appendix provides information about the Program Temporary Fixes (PTF) system. _________________________________________________________________________ NOTE You may already have PTFs installed on your system. Do not attempt to re-apply any of them after you have installed SCO UnixWare 2.1.3. _________________________________________________________________________ After you install SCO UnixWare 2.1.3, the PTFs which are currently installed on your system are still reported if you issue a pkginfo(1) command, even though the enhancements and fixes in SCO UnixWare 2.1.3 may supersede them. The installation procedure ``locks down'' the PTFs if they already exist on your system. You cannot remove them. This ensures that files which were installed and edited by the PTFs, and subsequently modified by update213, hba213 or nic213, are not disturbed. Enhancements in the update213 package SCO UnixWare 2.1.3 includes fixes and enhancements resulting from Modification Requests (MRs) and PTFs. The PTFs included in update213 are: ptf2100 SMTP and popper email fixes ptf2165 lp(1) command patch ptf2193 HBA with Siemens C7XX SCSI Controller ptf2202 Floppy Driver Patch ptf2211 Patch for cpp -D and -U options. ptf2215 adss Patch for Fixing Driver Hang on MP System ptf2223 sysdump fix for MP systems. ptf2228 ATAPI Upgrade for IDE Driver ptf2230 Patch for m320 mouse driver. ptf2236 Motif library patch (CR 7982). ptf2240 libthread patch. ptf2243 Year 2000+ update. ptf2248 MediaMgr Restore Selects Correct Number of Files ptf2255 STREAMS driver update. ptf2261 SCSI tape driver update. ptf 2270 Correct Security Problem with setgid bit ptf3001 ODI Core Drivers Supplement ptf3003 ADSL HBA Driver Patch ptf3004 NWS Kernel Tunable Supplement ptf3005b Netmgt Shared Memory Supplement ptf3006 Motif Library Patch ptf3007 Updated ADSL Driver ptf3008 Libthread Patch Supplement ptf3009 Updated ATAPI Driver ptf3011 English Locales for NUC Supplement ptf3014 Video Driver Update ptf3015 UnixWare Year 2000 Supplement ptf3017 Video Driver Supplement ptf3019b Intel EtherExpress PRO/100B Driver Supplement ptf3024 MediaMgr Restore Selects Correct Number of Files ptf3025 pcnfsd(1M) Security Supplement ptf3026 Floppy Driver Patch ptf3028 Performance Enhancements for UnixWare 2.1 ptf3034 Streams Driver Update ptf3037 m320 Mouse Driver Supplement ptf3039 make and ar Accept Longer Lines and Files Names ptf3040 pkgremove Fix for ABI Compliance of UnixWare 2.1 ptf3043 cp(1), mv(1) and ln(1) fix for corruption and system slow down. ptf3046 libsocket.so Performance Supplement ptf3049 async Driver Supplement ptf3052 crash(1M) Utility Supplement ptf3057 priocntl(1) Utility Update ptf3060b make(1) Utility Supplement ptf3063 exec(2) System Call Security Supplement ptf3072 SCSI Disk Target Driver Supplement ptf3087 Enhanced procfs Driver ptf3088 SIGCLD Signal Mapping Supplement ptf3089 NFS Attributes Supplement ptf3093 urestore(1M) Permissions Supplement ptf3096 cron(1) Utilities Enhancement Supplement ptf3098 SDI Target Driver Supplement ptf3107 Single UNIX Specification Supplement ptf3111 LLC Src and Dest SAP Decoupler Supplement ptf3112 IDE Disk Setup Enabler Supplement ptf3116c IDE Driver Supplement ptf3120 UnixWare TCP/IP RIP-2 Supplement ptf3123 Networking Maintenance Supplement ptf3124c ADSL Driver Supplement ptf3131b Intel Processor Supplement ptf3138c Veritas Maintenance Update Supplement ptf3140 vi(1) Editor Supplement ptf3141b Video Driver Supplement ptf3142 Sybase Dataserver Supplement ptf3150 kma Driver for Statistics Reporting Supplement ptf3152c Multiple I/O APICs Supplement ptf3163 3Com 3C90x Driver Supplement ptf3165 High Volume rlogin(1) Sessions Supplement ptf3181 Dynamic Loadable Modules Supplement ptf3182 Network Printing Supplement ptf3190 4GB Boot Supplement ptf3209b Emergency Recovery Disk Supplement ptf3216 UnixWare ``dow_iowait'' Supplement ptf3219 UnixWare ``a_wss'' Supplement ptf3234 Optimizing C Compilation System Supplement ptf3238b UnixWare SNMP Supplement ptf3254 SCO UnixWare PCI Device Supplement ptf3259 sendmail(1M) Release 8.8.5 ptf3260 Ultra SCSI Disk Installation Supplement ptf3280l Network Maintenance Supplement ptf3288 3Com 3C509 Driver Supplement ptf3343 Intel Pentium Pro and Pentium II Microcode Driver ptf3357 Intel Pentium Erratum Supplement Full details of these PTFs can be found at the following FTP site: ftp://ftp.sco.com/UW21 ------------------------------------------------------------------------------ Appendix B Compatibility This appendix contains information about source code, command and utility, sockets and ksh93 compatibility. Source code The following is applicable for any system that has update213 installed, regardless of whether the X/Open Single UNIX Specification (UNIX95) is enabled. Many header file changes were required to comply with UNIX95. Many of these changes add new symbols and restrictions on the namespace. The symbols added for alignment to the specification are, by default, made visible when the header file is included. Compilation errors may be encountered if symbols in the header files conflict with symbols already declared in your source code. Many of these conflicting identifiers are function declarations that did not exist before, or function declaration parameter types that were changed to conform with UNIX95 (for example, char * to void *). The following are examples of the more common conflicts you may encounter during source recompilation: + The random function external declaration was added to . An error occurs if this function is already declared locally. Often it is sufficient to use the function declared in and remove the local declaration. + In some cases, new identifiers in a header file require the local declaration of the identifier and all references to it to be renamed. + The declaration for mmap(2) in /usr/include/sys/mman.h was changed from caddr_t to a void *. This may cause the following error if mmap is declared locally: identifier redeclared: mmap. The proposed resolution is to remove the local declaration of mmap. + The following fields of iovec_t in /usr/include/sys/uio.h are redefined: _________________________________________________________________________ From To _________________________________________________________________________ caddr_t iov_base void *iov_base int iov_len size_t iov_len The change to iov_base causes failures when arithmetic operations are performed on it without casting it to a data type that can be used in arithmetic operation. + The member names of the internal FILE structure defined in have changed to begin with a leading double underscore. Any application that directly references these members instead of using the standard I/O interfaces that are supplied in the Standard C Library result in a compilation error. Some of the new header files are from the BSD Compatibility package (``bsdcompat''). Traditionally, these header files have been located in /usr/ucbinclude. These are now included in /usr/include as part of the standard header file distribution. These files are as follows: + /usr/ucbinclude/ndbm.h + /usr/ucbinclude/strings.h The putmsg(2) streams system call returns ENXIO when a hangup is generated downstream. This behavior is different from SCO UnixWare 2.1.3 where EIO was generated. EIO is only generated now if the file descriptor, fd, refers to a streams-based pipe, and the other end of the pipe is closed. This behavior is the same as the EPIPE error condition. Commands and utilities The following is applicable for any system that has update213 installed, regardless of whether the Single UNIX Specification (UNIX95) is enabled. + -- operand delimiter: Standard utilities that accept a list of operands use -- to terminate the list, allowing portable applications to distinguish the operand list from any additional options a particular implementation may support. See XCU, section 1.9 ``Utility Description Defaults.'' Examples of utilities using -- as a delimiter are: dirname, pack, unpack, nohup, od, pg, printf, spell, strings, and xargs. + patch: The patch utility now exits with exit status 1 if any rejections occur. The previous version exited with the number of rejections. + strings: The strings utility previously exited after encountering a file access error. Now, it continues processing the subsequent file(s) instead of exiting immediately. + xargs: Exit status values have changed. The command exits with 127 if the utility on the command line could not be found, and with 126 if it could be found, but not executed. The previous version exited with status 1 in both cases. + rm: User input is required where none was needed before. Using -r to remove a write protected directory when stdin is a terminal and -f is not specified, you are prompted to confirm that the directory and its contents should be removed. Using -ri prompts twice before removing the directory, even if it is empty. The compatibility note for the rm command does not apply to the /usr/bin version of rm. The /usr/bin/rm command is the SCO UnixWare 2.1 version. The note applies only to the UNIX95-compliant rm command in /u95/bin. + awk: To comply with XPG4, awk processes variable assignments on the command-line after the BEGIN function is called. awk now rejects out of sequence ranges (for example, [f-a]). The value of $0 within the END block has changed. Instead of being empty, it now retains the value of the last input record. Previously, within an END block, print $0 would behave the same as a print statement by itself and print a blank line. Because $0 now contains the contents of the last input line within the END block, applications must use print ``'' instead of using a print statement by itself to print a blank line. Also, the awk close function was changed to return a value indicating success or failure. An undocumented feature of the previous awk was that a call to close did not require parentheses to be effective. Now, a ``call'' to close, without parentheses, silently has no effect because it is not a true function call. This can cause old awk scripts to run out of file descriptors. + sed: The way that sed's l command displays non-printable characters was changed to match the POSIX.2 standards. Specifically, these characters are displayed using escape sequences like those in the ANSI C standard, falling back on three octal digits for others (for example, 01 for ASCII A). + crontab: For UNIX95 compliance, cron must execute crontab and at jobs with the POSIX.2 shell. Since /usr/bin/sh is not the POSIX.2 shell, cron was changed to use a different shell for certain users. The user's shell from /etc/passwd is used provided that shell ends in ``sh''. Otherwise it uses /usr/bin/sh. Sockets The update213 package includes a UNIX95 compliant version of the sockets library. This library (/usr/lib/libsocket.so.2) is provided in addition to the sockets library originally delivered with SCO UnixWare 2.1 (/usr/lib/libsocket.so.1). For an application to take advantage of the standard API and enhanced capabilities of the UNIX95 socket library, the application must be linked with the UNIX95 library. The command line: c89 -o foo foo.c -l xnet -l c causes the compilation system to compile the source file foo.c and link the resulting object file with the UNIX95 library. Note that you cannot link new applications to use libsocket.so.1. Using cc . . . -l socket . . . will link libsocket.so.2. The following list describes the major differences between UNIX95 and SCO UnixWare 2.1.3 sockets. See the X/Open System Interface Definition, Issue 4 Version 2 and X/Open Networking Services, Issue 4 for more detail. + Error Handling: A number of new errors have been added and some existing error checks have been rearranged. In some cases, different errno values than the ones used by the SCO UnixWare 2.1.3 library are set by the UNIX95 library for the same condition. + Socket Options: The Transport Provider interface has been changed to allow setting options in the TS_UNBND and TS_DATA_XFER (not just in the TS_IDLE) state. + Address Length: The computation of address lengths for UNIX domain sockets was changed to yield the actual length of pathnames, not the maximum length. + Nonblocking Sockets: Connection attempts on nonblocking UNIX domain sockets continue to set errno to EINPROGRESS, but now they also go on to complete the connection. + MSG_WAITALL Flag: The new MSG_WAITALL flag is supported in the receive functions recv, recvfrom, and recvmsg (see the recv(3N) manual page). These calls now block until the receive buffer is full. + System Calls: The following system calls now go through the UNIX95 sockets library so that behavior specific to socket can be provided: close(2), fstat(2) (see the stat(2) manual page), lseek(2), read(2), readv (see the read(2) manual page), write(2), and writev (see the write(2) manual page). ksh93 versus ksh88 The following is applicable only if you use ksh93 or have UNIX95 enabled. There are some minor incompatibilities between ksh93 and ksh88, which are documented in this section. Cases that are clearly bugs in ksh88, and features that are completely upward compatible, are not included. + Functions, defined with name() with ksh93 are compatible with the POSIX.2 standard, not with ksh88. No local variables are permitted, and there is no separate scope. Functions defined with the function name syntax maintain compatibility. Function traces are also affected. + ! is now a reserved word. As a result, any command by that name no longer works with ksh93. + The -x attribute of alias and typeset -f is no longer effective, and the ENV file is only read for interactive shells. You need to use FPATH to make function definitions visible to scripts. + A built-in command named command has been added that is always found before the PATH search. Any script which uses this name as the name of a command (or function) is not compatible. + The output format for some built-ins has changed: set, typeset and alias now have single quotes around values that have special characters. The output for trap, without arguments, has a format that can be used as input. + With ksh88, a dollar sign followed by a single quote ($') was interpreted literally. Now it is an ANSI-C string. You must quote the dollar sign to get the previous behavior. Also, a $ in front of a double-quote ($") indicates that the string needs to be translated for locales other than C or POSIX. The $ is ignored in the C and POSIX locale. + With ksh88, tilde expansion did not take place inside ${...}. With ksh93, ${foo-~} causes tilde expansion if foo is not set. You need to escape the ~ for the previous behavior. + Some changes in the tokenizing rules were made that might cause some scripts with previously ambiguous use of quoting to produce syntax errors. + Programs that rely on specific exit values for the shell (rather than 0 or non-zero) may not be compatible. The exit status for many shell failures has been changed. + Built-ins in ksh88 were always executed before looking for the command in the PATH variable. This is no longer true. Thus, with ksh93, if you have the current directory first in your PATH, and you have a program named test in your directory, it is executed when you type test; the built-in version is run at the point /bin is found in your PATH. + Some undocumented combinations of argument passing to ksh builtins no longer work because ksh93 is getopts-conforming with respect to its built-ins. For example, typeset -8I previously would work as a synonym for typeset -i8. + Command substitution and arithmetic expansion are now performed on PS1, PS3, and ENV when they are expanded. Thus, ` and $( as part of the value of these variables must be preceded by a \ to preserve their previous behavior. + The ERRNO variable has been dropped. + If the file name following a redirection symbol contains pattern characters they are only expanded for interactive shells. + The arguments to a dot script are restored when it completes. + The list of tracked aliases is not displayed by alias unless the -t option is specified. + The POSIX.2 standard requires that test ``$arg'' have an exit status of 0, if and only if $arg is null. However, since this breaks programs that use test -t, ksh93 treats an explicit test -t as if the user had entered test -t 1. + The ^T directive of emacs mode has been changed to work the way it does in gnu-emacs. + ksh88 allowed unbalanced parentheses within ${name op val} whereas ksh93 does not. Thus, ${foo-(} needs to be written as ${foo- which works with both versions. + kill -l in ksh93 lists only the signal names, not their numerical values. + Local variables defined by typeset are statically scoped in ksh93. In ksh88 they were dynamically scoped, although this behavior was never documented. + To conform to the POSIX.2 standard, the value of the variable given to getopts is set to ``?'' when the end-of-options is reached. /u95/bin The following commands are in /u95/bin because the changes they introduced for UNIX95 compliance are not compatible with UnixWare 2.1 behavior. The commands in this category are: + renice + find + more + rm + tr These commands are accessed by default for customers configured to use the UNIX95 user environment. Users not using UNIX95 will by default access the UnixWare 2.1 versions of these commands. Also in this directory are: + A link from mkdir to /usr/bin/mkdir. + use_builtin. + The help file more.help. The modified ksh93 binary (called sh to conform with UNIX95) is also in this directory. ------------------------------------------------------------------------------ Appendix C Single UNIX Specification The following sections provide information about the Single UNIX Specification (UNIX95), its shell, compilation environment and manual pages. Procedures are also given for enabling or disabling UNIX95. The X/Open specification The Single UNIX Specification (UNIX95) encompasses five X/Open Common Applications Environment (CAE) specifications: + System Interface Definitions, Issue 4, Version 2 (XBD) + System Interfaces and Headers, Issue 4, Version 2 (XSH) + Commands and Utilities, Issue 4, Version 2 (XCU) + Networking Services, Issue 4 + X/Open Curses, Issue 4 _________________________________________________________________________ NOTE The development utilities in XCU are not required for the UNIX95 brand. The utilities are supported by SCO UnixWare, but they are not considered conformant in SCO UnixWare 2.1.3. _________________________________________________________________________ For an overview of UNIX95, and information about its history and business implications, browse the X/Open web site at: http://www.xopengroup.org/ The POSIX.2 shell (ksh93) UNIX95 requires that a user's login shell must be a POSIX.2-compliant shell, and that it must be accessed as sh. The POSIX.2-compliant shell used is the 1993 version of the Korn shell (ksh93 Version D) with SCO enhancements. ksh93 provides many new and expanded capabilities including improvements for associative arrays, floating point arithmetic, internationalized messages, command and file completion, pattern matching and new builtins and reference variables. See The New KornShell Command and Programming Language, by Morris I. Bolsky and David G. Korn, Prentice Hall PTR, 1995 for information about ksh93. If you have the ``manpages'' package installed, you can display the English manual page for ksh93 by typing the following at the command line: man ksh93 _________________________________________________________________________ NOTE If you do not want to enable UNIX95, you can still use ksh93 by setting your login shell to /u95/bin/ksh93. In fact, using this shell satisfies many (but not all) of the runtime requirements for UNIX95 conformance. To preserve SCO UnixWare 2.1.3 compatibility for non-UNIX95 users, ksh88 continues to be available in /usr/bin/ksh. See Appendix B, ``Compatibility'' for differences between ksh93 and the 1988 version of the Korn shell (ksh88) which was provided in the ``cmds'' package for SCO UnixWare 2.1.3. _________________________________________________________________________ Compliant compilation environment To use the UNIX95 namespace of identifiers and prototypes in header files, the _XOPEN_SOURCE macro must be defined in each source file prior to including any header file. This exposes those definitions aligned with POSIX.1 and POSIX.2. In addition, the _XOPEN_SOURCE_EXTENDED macro must be defined as ``1'' prior to inclusion of any headers. Use the c89 interface to the standard C compilation system. This utility allows you to take advantage of the standard API and the X/Open curses and POSIX.2 socket libraries. You can view the c89 manual page by using the man(1) command. X/Open curses SCO UnixWare 2.1.3 provides the X/Open curses library. Although X/Open curses is not formally a part of UNIX95, it is provided to assist software developers in migrating toward an anticipated specification. After installing update213, your system will have two curses libraries available, the SCO UnixWare 2.1.3 version, and the new X/Open version. The version of curses provided with SCO UnixWare 2.1.3 is still accessed in the same way. The new X/Open curses library can be linked in either of the following two ways: + Enter the following: cc -o foo foo.c -l stdcurses Then use the following: # include # include + Enter the following: c89 -o foo foo.c -l curses Then use the following: # include # include Single UNIX Specification manual pages Over 100 manual pages have been created or revised to reflect changes due to UNIX95, and they are included with update213. The new manual pages overlay existing pages with the same name in the manpages package, but contain information for both UNIX95 and non-UNIX95 users. The English manual pages are available using the man command. If the manpages package is not available on your current system and you want to be able to display these pages using the man command, you should install the ``manpages'' package before installing update213. The manpages package is available on your SCO UnixWare 2.1.3 installation media. The Japanese manual pages are available as plain text and PostScript(r) files in /usr/share/jaman. Enabling the Single UNIX Specification during installation During the update213 installation, you are offered an option to enable UNIX95 (alternatively, you can enable it later). Because this specification defines behavior that is sometimes different from that of previous SCO UnixWare systems, you should review these notes carefully and understand the impact on your system before choosing this option. Generally, you should enable UNIX95 only if you have a need for a conforming environment. If you choose to enable UNIX95 during the installation, the RSTCHOWN tunable is turned on, /u95/bin/sh becomes the default shell, and new users added to the system are UNIX95 compliant. _________________________________________________________________________ NOTE Although new users are compliant, you must manually specify the /u95/bin/sh shell for existing users who want to conform. See ``Setting the login shell'' for instructions. _________________________________________________________________________ POSIX specifies two types of chown behavior and SCO UnixWare supports both types, but turning on RSTCHOWN satisfies additional FIPS and XPG standards that mandate that a user cannot give ownership of files away. The installation script for update213 edits the file /etc/profile and makes two changes: the environment variable POSIX2 is set to ``on'', and /u95/bin is prepended to the PATH environment variable. The file /etc/profile is executed as part of the login sequence for all users whose login shell (the shell listed in /etc/passwd) is /u95/bin/sh. After installing update213, every UNIX95 user has the above environment variables set as shown in their environment when they log in to the system. Enabling the Single UNIX Specification after installation If you did not enable UNIX95 during the update213 package installation, you can enable it after installation by performing the following steps: 1. Set the RSTCHOWN tunable to 1. 2. Set the default shell to /u95/bin/sh. 3. Set the login shell to /u95/bin/sh. 4. Reboot the system. Setting RSTCHOWN To set the RSTCHOWN tunable to 1: 1. Double-click on the Admin_Tools icon in your SCO UnixWare Desktop window. 2. Double-click on the System_Tuner icon. 3. Select File System Parameters. 4. Scroll to, and click on RSTCHOWN. 5. Move the gauge from 0 to 1 (all the way to the right), and click on OK. 6. Select ``No'' when asked if you want to rebuild the kernel now. 7. Click on OK when advised that the kernel will be rebuilt when the system is rebooted. Setting the default shell To set the default shell: defadm useradd SHELL=/u95/bin/sh Setting the login shell This procedure varies depending on whether you are setting the login shell for a new or existing user, and whether you are performing the task from the command line or the Desktop. + If you add a new user using the useradd(1M) command, /u95/bin/sh is used by default. No further action is necessary. + Use the usermod(1M) command to set /u95/bin/sh for an existing user. For example: usermod -s /u95/bin/sh login _________________________________________________________________________ NOTE You need to do this for existing users even if you enabled the UNIX95 during the update213 installation process. _________________________________________________________________________ + If you use User Setup from the Desktop, select Show Other Options and specify the shell as /u95/bin/sh. This is necessary for both new and existing users when using the Desktop. Disabling the Single UNIX Specification To disable UNIX95, perform the following steps: 1. Reset the RSTCHOWN tunable to 0. 2. Reset the default shell to /usr/bin/sh or /usr/bin/ksh. 3. Reset the user's login shell to /usr/bin/sh or /usr/bin/ksh. 4. Reboot the system. Resetting RSTCHOWN Follow the procedure described in ``Setting RSTCHOWN'', but move the gauge from 1 to 0. Resetting the default shell To reset the default shell, enter the following: defadm useradd SHELL=/usr/bin/sh _________________________________________________________________________ NOTE Use /usr/bin/ksh if you want to reset the default to the ksh88 shell. _________________________________________________________________________ Resetting the login shell For each existing UNIX95 user, use the usermod(1M) command to reset /usr/bin/sh or /usr/bin/ksh as their login shell. To obtain a UNIX95-conformant system, after installing the SCO UnixWare 2.1.3 update you will need to obtain and install update213, then as part of your setup you should add /u95/bin to the PATH of /etc/default/login. PPP dialin accounts set up by the Internet Manager are created with an incorrect shell. To work around this problem, run the following commands as root before configuring any dialin PPP connections: rm -f /usr/lib/ppp/ppp ln -s /usr/lib/mstppp/Login /usr/lib/ppp/ppp Incoming PPP connections to an SCO UnixWare 2.1 system running SCO PPP from Morning Star will cause the following message to appear in the logfile /usr/lib/mstppp/Log: UX:sh (dialin): ERROR: /usr/internet/etc/siofio: Not found This can be ignored. (To eliminate the problem, edit the files /usr/lib/mstppp/dialin and /usr/lib/mstppp/exec.dialout and delete all references to /usr/internet/etc/siofifo.) ------------------------------------------------------------------------------ Appendix D Installing the HBA and NICS drivers This chapter describes the CD-ROM and FTP-based procedures for installing the HBA and NICS drivers that accompany the update213 package. The chapter also explains the creation of Independent Hardware Vendor (IHV) diskettes. An HBA or NICS IHV diskette is required when installing Host Bus Adapter or Network Interface Card drivers. It is also useful if you want to install SCO UnixWare 2.1.3 HBA or NIC drivers during a new SCO UnixWare 2.1.3 installation. Installing the drivers from CD-ROM This section describes the CD-ROM installation procedures for the drivers, and for creating an IHV diskette from this channel. Creating an IHV diskette from CD-ROM To create an HBA or NICS IHV diskette from CD-ROM, carry out the following steps. 1. Insert a formatted 1.44MB diskette into diskette drive 1. You can format the diskette using: format /dev/rfd0 2. Insert the CD-ROM into CD-ROM drive 1 and mount the drive. For example: mount /dev/cdrom/c0b0t5l0 /mnt 3. Copy the nic213 image from the CD-ROM to a diskette. For example: dd if=/mnt/UW213/IMAGES/nic213.img of=/dev/fd0 4. Unmount the CD-ROM drive. For example: umount /mnt 5. Remove the diskette and label it. Installing hba213 drivers from CD-ROM To install the hba213 package from CD-ROM using the pkgadd(1M) command, carry out the following steps: 1. mount(1M) the CD-ROM as shown in the procedure detailed in ``Installing update213 from the Installation CD-ROM''. For example: mount -Fcdfs -r /dev/cdrom/c0b0t5l0 /mnt 2. Issue the pkgadd command to install the HBA driver you want. For example: pkgadd -d /mnt/UW213/PKGS/hba213 device_driver where device_driver is adsl, adss, c7xx, c8xx, ida, ide, iiop, flashpt, and so on. 3. Use the unmount utility (see the mount(1M) manual page) to remove the CD-ROM: umount mount_point For example: umount /mnt 4. Reboot the system. _________________________________________________________________________ NOTE The SCO UnixWare 2.1.3 supplementary CD-ROM contains the SCO UnixWare 2.1, 2.1.1, 2.1.2 and 2.1.3 Host Bus Adapter packages. Those users who specifically require the original SCO UnixWare 2.1, 2.1.1 or 2.1.2 Host Bus Adapter diskettes can use the command dd(1M) to transfer the diskette images from the IMAGES directory on the supplementary CD-ROM to a formatted floppy disk. _________________________________________________________________________ Installing nic213 drivers from CD-ROM The nic213 package must be installed from an IHV diskette using the Network Interface Card Configuration (niccfg) utility. To install the nic213 drivers: 1. Invoke niccfg. 2. Choose the ``Install Driver From IHV Diskette'' option on the Summary Screen. See ``Creating an IHV diskette from CD-ROM'' for details of IHV diskettes. 3. Follow the online instructions. Instructions for using the niccfg utility are given in the Release 2.1 SCO UnixWare Installation Handbook. For general information, see the ``Installing a New or Updated Driver from Diskette'' section in Appendix E. Installing the drivers from FTP This section describes the FTP installation procedures for the drivers, and for creating an IHV diskette from this channel. Creating an IHV diskette from FTP To create an HBA or NICS IHV diskette from an image downloaded from the FTP site, carry out the following steps. 1. Insert a formatted 1.44MB diskette into diskette drive 1. 2. Copy the nic213 image to the diskette. For example: dd if=/pathname/nic213.img of=/dev/fd0 where pathname is the full pathname of the directory that contains the image. Installing hba213 drivers from FTP To install an hba213 image downloaded from the FTP site, carry out the following steps: 1. Create an HBA diskette from the downloaded image file. See ``Creating an IHV diskette from FTP'' for details of IHV diskettes created from FTP. 2. Insert the HBA diskette into the diskette drive, and issue the pkgadd command to install the HBA driver you want: pkgadd -d diskette1 device_driver device_driver is adsl, adss, c7xx, c8xx, ida, ide, iiop, flashpt, and so on. 3. Reboot the system. Installing nic213 drivers from FTP The nic213 package must be installed from an IHV diskette using the Network Interface Card Configuration (niccfg) utility. To create an nic213 IHV diskette from an image downloaded from the FTP site, carry out the following steps: 1. Download image from the FTP site. 2. Insert a formatted 1.44MB diskette into diskette drive 1. 3. Copy the nic213 image to a diskette, as follows: dd if=/pathname/nic213.img of=/dev/fd0 pathname is the full pathname of the directory that contains the image. 4. Invoke niccfg. 5. Choose the ``Install Driver From IHV Diskette'' option on the Summary Screen. 6. Follow the online instructions. Instructions for using the niccfg utility are given in the Release 2.1 SCO UnixWare Installation Handbook. For general information, see that book's ``Installing a New or Updated Driver from Diskette'' section. ------------------------------------------------------------------------------ Appendix E SCO online services information When your success depends on having the right answers to product or technical questions, you can rely on SCO's online services 24 hours a day, 7 days a week. SCO provides these services to all SCO customers: + SCO's World Wide Web (WWW) site + SCO's Online Support (SOS) system + SCOFORUM on CompuServe + anonymous FTP + anonymous UUCP + Ftpmail + InfoFax World Wide Web (WWW) SCO's World Wide Web site is available at the following URL: http://www.sco.com It supplies the following: + About SCO + Press releases + What's New + Third Party Information + Datasheets on SCO products and services + Schedules for SCO Technical Training classes + Searchable Technical Articles database + Access to SCO's supplementary software distributions Availability is 24 hours a day, 7 days a week. The software or hardware required for access to the site is as follows: + Internet browser such as SCO Global Access or Mosaic. + Internet connection. SCO's Online Support (SOS) system SOS is a menu driven BBS program that provides a character-based, front end interface for ease of use. Any command is just a few keystrokes away. SCO's Online Support (SOS) system contains: + About SCO + Press releases + What's New + Searchable technical articles database + Third Party Information + Datasheets on SCO products and services + Schedules for SCO Technical Training classes + Access to SCO's supplementary software distributions To download these supplements, the third party communications package being used must support XMODEM. The software or hardware required for access to the facility is as follows: + terminal and modem + computer, modem, and a third party communications package + the cu(1C) command (for SCO UNIX systems) In addition to the hardcopy documentation provided with this version of SCO UnixWare 2.1.3, the following Postscript documents are available on the supplementary CD-ROM in the DOCS directory (see ``Contents of the update on the Installation CD-ROM'' for more information): + SCO Internet PPP from Morning Star User's Guide + Netscape FastTrack Server Administrator's Guide + Netscape FastTrack Server Programmer's Guide + Netscape Navigator Gold Authoring Guide + Netscape Navigator JavaScript Guide Phone numbers: v.32, v.32bis 8@ +408 426-9495 Telebit Trailblazer 1@ +408 426-9525 Internet access via telnet is available as follows: telnet sos.sco.com SCOFORUM on CompuServe An extensive set of ongoing CompuServe forums and technical information is available about SCO in the SCOFORUM area of CompuServe. Availability is 24 hours, 7 days a week. A CompuServe account is required in order to access this facility. For more information on acquiring a CompuServe account, call CompuServe on +800 848-8199. Once an account has been set up, log onto CompuServe and type GO SCOFORUM. Anonymous FTP SCO's anonymous FTP site provides access to SCO's supplementary software distributions. _________________________________________________________________________ NOTE For further information on what is available in each of the supplementary software distributions, download the README file located in FTP's root directory. _________________________________________________________________________ Availability is 24 hours, 7 days a week. The software or hardware required to access this service is the FTP program and an Internet connection. _________________________________________________________________________ NOTE The ftpd(1M) program that runs on the machine at ftp.sco.com requires that your Domain Name Server be registered with the Internet. _________________________________________________________________________ To access this service, carry out the following steps: 1. Enter the following: ftp ftp.sco.com 2. Log in as the user ``anonymous''. 3. Use your email address as the password. Anonymous UUCP If UUCP is configured, you can access the sosco (US) or scolon (UK) machines to download the supplementary distribution files located in the /usr/spool/uucppublic directory. An example entry for accessing sosco via UUCP is located in the /usr/lib/uucp/Systems file on the local machine. SCO's anonymous UUCP site provides access to SCO's supplementary software distributions. _________________________________________________________________________ NOTE For further information on what is available in each of the supplementary software distributions, download the /usr/spool/uucppublic/README file via UUCP. _________________________________________________________________________ Availability is 24 hours a day, 7 days a week. The software and hardware required to access this service is as follows: + UUCP installed and configured + modem Phone numbers: For Canada, USA, Pacific Rim, Asia and Latin America: v.32, v.32bis 5@ +408 425-3502 Telebit Trailblazer 1@ +408 429-1786 Machine name sosco Login name uusls (note the fourth character is the letter ``l'') No password For Europe/Middle East/Africa: v.32 +44 (0) 1923 222681 Dowty Trailblazer +44 (0) 1923 210911 Machine name scolon Login name uusls (note the fourth character is the letter ``l'') Password bbsuucp Ftpmail Ftpmail is an automated email service that acts as a gateway between electronic mail and FTP, executing FTP commands received by email, and sending back the requested files to the user by email. Availability is 24 hours a day, 7 days a week. The software and hardware required to access this service is an electronic mail package. Mail should be sent to ftpmail@sco.com. Leave the subject line blank, and give a one-line message of ``help''. InfoFax InfoFax is an unattended FAX-back service. InfoFax contains copies of the most commonly requested technical articles, educational offerings and product information. Availability is 24 hours a day, 7 days a week. The software or hardware required to access this service is as follows: + a touch tone phone + a FAX machine Phone: +408 427-6800 For a listing of available articles, request article 1000. ------------------------------------------------------------------------------ © 1998 The Santa Cruz Operation, Inc. All rights reserved.