






                                                                   CPL


                                                   UTX/32 Release 2.1B


                                                Software Release Notes


                                                              May 1989



         324-005500-300


























































LIMITED RIGHTS LEGEND

____________________________________________________________

This manual is supplied without representation or warranty
of any kind.  Gould Inc. therefore assumes no responsibility
and shall have no liability of any kind arising from supply
or use of this publication or any material contained herein.


PROPRIETARY INFORMATION

The information contained herein is proprietary to Gould CSD
and/or its vendors, and its use, disclosure or duplication
is subject to the restrictions stated in the Gould CSD
license agreement Form No. 620-06 or the appropriate third-
party sublicense agreement.


RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the Government is subject
to restrictions as set forth in subdivision (c) (1) (ii) of
the Rights in Technical Data and Computer Software clause at
52.227.7013

Gould Inc., Information Systems
6901 West Sunrise Boulevard
Fort Lauderdale, Florida  33313

UTX/32, MICROSel, MPX-32, MULTISel, SelBUS, SelCONNECTION,
SelPAC, and PowerNode are trademarks of Gould Inc.

CONCEPT/32 is a registered trademark of Gould Inc.

UNIX is a registered trademark of AT&T Bell Laboratories.

Ethernet is a trademark of Xerox Corporation.

NFS is a trademark of Sun Microsystems, Inc.

Portions of the UTX/32 Operating System and UTX/32 Crypt
Modules are proprietary to AT&T Bell Laboratories, and
portions are proprietary to Gould CSD.
Copyright 1989 by Gould Inc.
All Rights Reserved
Printed in the U.S.A.
























CONTENTS
____________________________________________________________

1   OVERVIEW

Summary of Contents
Documentation Conventions

2   CONTENTS OF THIS RELEASE

Binary Distribution
  Model Numbers
  Revision Date
Source Distribution
  Model Numbers
  Revision Date
Crypt Module Distribution
Software Update Service
Documentation Delivered With This Product

3  PRODUCT INFORMATION

Product Description
Release History
Package Format
Distribution Tape Format
Disk Space Requirements
Installation Environment Requirements
ACS Microcode Update Files

4  DIFFERENCES BETWEEN UTX/32 RELEASE 2.1A AND RELEASE 2.1B

Diskless Sun Support
SPR Resolutions

5  UPDATING YOUR SYSTEM TO RELEASE 2.1B

Files from /etc
Files and Directories From /usr/lib
Files from /usr/lib/uucp
Directories

6  PRODUCT HINTS

Support For Real Time Programming
Support For COFF Executables
  Implications for User Programs
  Implications for UTX/32 Utilities
Memory Classes
No Swap Kernel
Terminal Interface
Ethernet Driver
System Call Numbers and New System Calls












System V Utilities
User Commands
Language Tools and Libraries
System Configuration and Installation
  /sys/Makefile and /sys/Makefile.exec
  Makedev
  Support for Alternate Root Devices
  Dynamic Allocation of Swap Partitions
  Miniroot File System
  Expanding the Size of the Root File System
  Tools for Creating a Distribution Tape
  /sys/obj/CON.DIST
  /usr/gould and /gould
Gould Common FORTRAN
System Administration
  tboot and dboot
  prep and sprep
  User IDs and Group IDs
  /etc/shutdown
  Timezone Support
Timer Services

7   KNOWN PROBLEMS

Kernel
Device Drivers
Direct Files
Utilities
Miscellaneous
Documentation Errors
  FORTRAN 77 Reference Manual

8   SPRs RESOLVED IN RELEASE 2.1B

Listing of Resolved SPRs
Online Viewing of SPRs
UTX/32 Problem Reporting
  By Telephone
  With SPR Forms
  Using Electronic Mail Using gouldspr
























1  OVERVIEW
____________________________________________________________


   This document, the UTX/32 Release 2.1B Software Release
   Notes (SRN), is provided to customers purchasing or
   upgrading to Release 2.1B.  It describes changes to the
   UTX/32 operating system from Release 2.1A to Release 2.1B
   as well as providing other release-specific information.

   NOTE: Release 2.1B is the second general release of the
   enhancements and improvements included in Release 2.1.
   For purposes of clarity, this document refers to both
   releases.

   The documents for Release 2.1B consist of those for
   Release 2.1 (they bear the 2.1 release number), Release
   2.1A, and change packages and revisions for Release 2.1B.
   Thus, some of the documents refer to Release 2.1 as the
   current release, but the information they contain is
   otherwise current.

   IMPORTANT:  Read the SRN before attempting to install or
   use the Release 2.1B software.  Besides providing an
   overview of the release, this document contains critical,
   late-breaking information about the system that is not
   documented elsewhere.  In this sense, the SRN supplements
   the entire Release 2.1 documentation set.

SUMMARY OF CONTENTS

   This document contains the following information:

   +  Overview of this document

   +  Contents of this Release

   +  Product Information

   +  Differences Between Releases 2.1A and 2.1B

   +  Updating Your System to Release 2.1B

   +  Product Hints

   +  Known Problems

   +  SPRs Resolved in this Release








UTX/32 Software Release Notes                                      1-1








DOCUMENTATION CONVENTIONS

   NOTE:  The documentation conventions concerning type
   fonts apply to only the hardcopy version of this Software
   Release Notes documents.

   These are the documentation conventions for this
   document:

Prompts

   The following prompts are used in this document:

   #    Superuser prompt

   $    Bourne shell prompt

   %    C shell prompt

Nonprinting and control characters

   Nonprinting characters obtained by striking special keys
   are displayed within angle brackets.  For example, <DEL>
   indicates the delete key, <CR> a carriage return.

   In this guide, a <CR> is assumed at the end of every
   command line unless otherwise stated.  The <CR> is
   displayed only if nothing else is entered on the line or
   if the sequence of keystrokes would otherwise be unclear.

   Control characters are represented using the caret
   notation.  For example, ^D indicates <CTRL>-d.  In
   examples, control characters are shown as echoing on the
   terminal screen.  Whether they echo on your terminal
   depends on its settings; refer to the stty(1) manpage.

Boldface

   Command and utility names, file names, pathnames, and
   words from code are printed in boldface.

   Example:

   The nroff command is used to format text.

   Exception: When such a term is long and all uppercase, it
   is not printed in boldface.








1-2                                                           Overview








Line printer and line printer bold

   Displays of code and user sessions are printed in line
   printer font.  In displays of interactive user sessions,
   text typed by the user is printed in line printer bold.

   Example:

   $ ls
   file1     file2     file3

Italics

   Variable expressions that must be replaced with a value
   are printed in italics.  Square brackets ([ ]) around an
   italicized variable expression signify that specifying
   the value is optional.

   Example:

   % cd [directory]

   Italics are also used to introduce new terms, for titles
   of documents or manual pages, and occasionally for
   emphasis.  When manual pages are cited, the manual
   section number is given in parentheses and is not
   italicized.

   Examples:

   UTX/32 manual pages are often referred to as manpages.

   Refer to the mount(8) manpage.

Ellipses

   Vertical or horizontal ellipses (. . .) indicate that
   information has been omitted.

   Example:

   % rsh fang
      .
      .
      .
   % logout










UTX/32 Software Release Notes                                      1-3








   2  CONTENTS OF THIS RELEASE
   ____________________________________________________________

   Information on the various UTX/32 Release 2.1B
   distribution components is given in this chapter, as are
   model numbers.  The following are the components of the
   distribution:

   +  Program binary tapes
   +  Program source tapes
   +  BSD Pascal compiler binary tapes
   +  BSD Pascal compiler source tapes
   +  Crypt modules binary tapes
   +  Crypt modules source with binary tape
   +  Software Update Service (SUS)
   +  Documentation

BINARY DISTRIBUTION

   UTX/32 Release 2.1B program binaries are distributed on
   four tapes:

   +  1200 foot tape containing the miniroot/boot tape

   +  2400 foot tape containing a single multivolume dump
      image of both the BSD /usr.POWERNODE files and the
      System V /usr.POWERNODE/5* files

   +  1200 foot tape containing the remainder of the single
      dump image

   +  600 foot tape containing the BSD Pascal compiler

      NOTE:  The BSD Pascal tape has a model number, but it
      cannot be ordered separately.  BSD Pascal Revision 2.1
      was not updated for UTX/32 Release 2.1B and will not
      be redistributed to customers who received the BSD
      Pascal binary with their UTX/32 Release 2.1/2.1A
      deliverables.

   The three tapes and the UTX/32 document set are delivered
   with the new purchase of one of the model numbers listed
   below.

   When first purchasing a binary distribution, you
   automatically receive six months of warranty service,
   which includes any update tapes released during that
   period.  After the warranty period expires, the Software
   Update Service must be purchased to receive any further
   updates.  (Refer to the Software Update Service section
   below for Software Update Service information.)




UTX/32 Software Release Notes                                      2-1









Model Numbers

   The following list contains model numbers for the  binary
   distribution.

                   Binary Distribution Tapes

                      Tape                 Model Number

        Binary Single System for PN60xx    1467-0703
        Binary Single System for PN90xx    1467-1703
        Educational Binary Single System   1467-3703E
          (PN60xx or PN90xx)
        BSD Pascal Compiler Binary         1434-0703


Revision Date

   May 1989

SOURCE DISTRIBUTION

   Customers with a source license receive the following
   tapes:

   +  2400 foot tape containing a single multivolume dump
      image of the UTX/32 source

   +  1200 foot tape containing the remaining single dump
      image of the source

      NOTE:  The BSD Pascal tapes have model numbers, but
      they cannot be ordered separately.  BSD Pascal
      Revision 2.1 was not updated for UTX/32 Release 2.1B
      and will not be redistributed to customers who
      received the BSD Pascal tapes with their UTX/32
      Release 2.1/2.1A deliverables.

   +  the binary distribution tapes

   New source customers also receive  a 600 foot tape
   containing the source for the BSD Pascal compiler
   Revision 2.1.

   The UTX/32 source tapes, four UTX/32 binary tapes, and
   the UTX/32 document set are delivered with the new
   purchase of one of the model numbers listed below.








2-2                                           Contents of This Release









Model Numbers

   The following list contains the  model  numbers  for  the
   source distribution

                   Source Distribution Tapes

                     Tape                    Model Number

     Source Single System PN60xx or PN90xx   1467-2723
     Educational Source Single System        1467-3723E
       (PN60xx or PN90xx)
     BSD Pascal Compiler Binary              1434-0703
     BSD Pascal Compiler Source              1434-0723


Revision Date

   May 1989

CRYPT MODULE DISTRIBUTION

   The cryptographic algorithm implemented in UTX/32 cannot
   be exported outside the United States according to U.S.
   export laws.  Therefore, the crypt code is available only
   to domestic customers on a separate binary or source
   tape. This separation means that both the BSD and System
   V environments of the standard UTX/32 distribution lack
   the following options and functionality:

   +  The ed and ex editors do not support the encryption
      option (-x).

   +  The crypt library routines do not allow decoding,
      although they do allow encoding via a unidirectional
      hashing function.

   +  The crypt utilities are not available.

   +  The vi, edit, and view programs do not support the -x
      option, because these program files are links to ex.

   Documentation on the standard distribution reflects these
   missing options and functionality.

   The crypt module source and binary tapes include both BSD
   and System V versions of the ed and ex editors that do
   support the -x option, the crypt library routines that
   allow both encoding and decoding, and the crypt
   utilities.  Manual pages that document encryption options
   and functionality are also included.



UTX/32 Software Release Notes                                      2-3








   Differences between Release 2.0 and Release 2.1A and 2.1B
   crypt modules are described in Chapter 6, section
   /lib/libc.a and /usr/5lib/libc.a.

   Purchase of a 1467 UTX/32 source license is the
   prerequisite for purchasing crypt source.

                Crypt Module Distribution Tapes

                  Crypt Module       Model Number

              Binary Single System   1463-0703
              Source (with Binary)   1463-0723


SOFTWARE UPDATE SERVICE (SUS)

   The purchase of Software Update Service provides you with
   one year of UTX/32 updates.

   Use the following model numbers listed to order Software
   Update Service.

   NOTE: Source single system SUS includes binary SUS.  All
   1467 SUS models automatically include SUS for any
   required updates to 1434 BSD Pascal.

                    Software Update Service

                     Tape                    Model Number

     Binary Single System for PN60xx         1467-0753
     Binary Single System for PN90xx         1467-1753
     Source Single System (PN60xx, PN90xx)   1467-2753
     Educational Binary or Source            1467-3753E
     Crypt Module Binary or Source           1463-0753


DOCUMENTATION DELIVERED WITH THIS PRODUCT

   The documentation set listed below is a component of
   UTX/32 Release 2.1B.  For a more complete description of
   the documentation and a glossary of UNIX and UTX/32
   terminology, refer to the UTX/32 Release 2.1
   Documentation Guide.  Additional copies of documents can
   be ordered using the publication order numbers given
   below.

   NOTE:  In the following list, the acronym CP1 refers to
   change package 1.  New UTX/32 customers receive both the
   original versions and the change packages. SUS customers
   receive only the documentation updated for Release 2.1B,
   which is specified with an asterisk (*) in the following



2-4                                           Contents of This Release








   list.

               UTX/32 RELEASE 2.1B DOCUMENTATION

                      Document Title                          Pub. Order. No.
UTX/32 Release 2.1 Documentation Guide                        323-005530-000
UTX/32 Release 2.1 Real-Time User's Guide                     323-005550-000
UTX/32 Real-Time User's Guide (CP1)                           323-005550-001*
UTX/32 Release 2.1B BSD User's Reference Manual               323-005480-200*
UTX/32 Release 2.1 System V User's Reference Manual           323-005500-100
UTX/32 System V User's Reference Manual (CP1)                 323-005500-101*
UTX/32 Release 2.1 Input/Output Subsystem Guide               323-005430-100
UTX/32 Input/Output Subsystem Guide (CP1)                     323-005430-101*
UTX/32 Release 2.0 Network File System (NFS) Guide            323-005470-000
UTX/32 Network File System (NFS) Guide (CP1)                  323-005470-001
UTX/32 Release 2.0 Remote Job Entry (RJE) Guide               323-005460-000
UTX/32 Remote Job Entry (RJE) Guide (CP1)                     323-005460-001
UTX/32 Release 2.0 Assembler Reference Manual                 323-005450-000
UTX/32 Assembler Reference Manual (CP1)                       323-005450-001
UTX/32 Release 2.0 FORTRAN 77 Reference Manual                323-005540-000
UTX/32 FORTRAN 77 Reference Manual (CP1)                      323-005540-001
UTX/32 Release 2.1B BSD Programmer's Reference Manual         323-005490-200*
UTX/32 Release 2.1 System V Programmer's Reference Manual     323-005510-100
UTX/32 System V Programmer's Reference Manual (CP1)           323-005510-101*
UTX/32 Release 2.1B Special Files Reference Manual            323-005400-100*
UTX/32 Release 2.1B Software Release Notes                    324-005550-300*
UTX/32 Release 2.1B Installation Guide                        323-005410-200*
UTX/32 Release 2.1B Operations Guide                          323-005420-200*
UTX/32 Release 2.1B System Administrator's Reference Manual   323-005520-200*
UTX/32 Supplementary Documents: Getting Started               323-006290-000
UTX/32 Supplementary Documents: Communications for Users      323-006310-000
UTX/32 Supplementary Documents: Text Editors                  323-006320-000
UTX/32 Supplementary Documents: Document Preparation          323-006330-000
UTX/32 Supplementary Documents: Basic Utilities               323-006300-000
UTX/32 Supplementary Documents: Programming Tools             323-006170-000
UTX/32 Supplementary Documents: System Communications         323-006240-000
UTX/32 Supplementary Documents: System Programming            323-006220-000
UTX/32 Supplementary Documents: Programming Languages         323-006160-000
UTX/32 Supplementary Documents: System Management             323-006130-000
















UTX/32 Software Release Notes                                      2-5








   3  PRODUCT INFORMATION
   ____________________________________________________________

   PRODUCT DESCRIPTION
                                                           
   UTX/32 operating systems are implementations of the UNIX
   operating system on Gould hardware.  The UTX/32 kernel is
   based on 4.3BSD UNIX from the University of California at
   Berkeley.  AT&T Bell Laboratories System V interfaces are
   built on top of this kernel.  UTX/32 provides both BSD
   and System V working environments, which you can switch
   between or combine.

   UTX/32 adheres to industry-wide standards.  For example:

   +  UTX/32 complies with the Kernel and Base Extension of
      the System V Interface Definition (SVID).

   +  UTX/32 substantially adheres to the criteria for a
      portable operating system interface as described in
      Draft 12 of the IEEE Standard Portable Operating
      System Interface for Computer Environments, October
      12, 1987.

   UTX/32 provides kernel support for real time applications
   and system support of executables in both COFF format and
   a.out format.

   Existing interfaces have been changed as little as
   possible, and the system is able to execute existing
   binaries.  Existing programs that refer to the internal
   structure of executable files need to be modified.  In
   addition, a few kernel data structures have been changed
   and some symbols in the kernel have been removed;
   programs that find and use particular structures or
   symbols in the kernel may need to be modified.

   Release 2.1A was based upon Release 2.1, which was the
   first release of UTX/32 to include real time
   enhancements, but which had limited distribution.
   Release 2.1A included all of the real time enhancements
   developed for Release 2.1 and also included resolutions
   of many outstanding Software Problem Reports (SPRs).

   Release 2.1B is based upon Release 2.1A and includes
   support for Diskless Suns, as well resolutions of many
   outstanding SPRs.

RELEASE HISTORY

   The following is the release history of this product:





UTX/32 Software Release Notes                                      3-1








   DESCRIPTION          LEVEL      DATE
   Original Release     2.1        January 1988
   Maintenance Release  2.1A       July 1988
   Maintenance Release  2.1B       May 1989

PACKAGE FORMAT

   All UTX/32 Release 2.1B tapes are standard 1/2" 9-track
   magnetic tapes recorded at 1600 BPI (F class).

DISTRIBUTION TAPE FORMAT

   The boot tape, which is the first tape in the
   distribution, contains the following:

   +  The tape boot program.  As this program executes, it
      loads the remaining contents of the tape until it
      encounters the first double End-Of-File (EOF).

   +  An EOF.

   +  The tape boot kernel, which is a minimally configured
      kernel used only during installation and system
      configuration.

   +  An EOF.

   +  A Common Object File Format (COFF) image of a memory
      disk.  The COFF image's section header specifies the
      physical address at which the boot program loads the
      image.  The memory disk contains a miniroot file
      system.

   +  A double EOF.

   +  An image of a complete root file system, called the
      distribution root file system, in dump format.

   +  A double EOF.

   +  A tar image of this document.

   +  An EOF.

   The second and third tapes consist of a single dump image
   containing both the BSD /usr.POWERNODE files and the
   System V /usr.POWERNODE/5* files.

   The BSD Pascal tape consists of two tar images.






3-2                                                Product Information








DISK SPACE REQUIREMENTS

   A 160 Mbyte drive is required to provide for the default
   /, /usr, and swap partitions. The amount of additional
   disk space required is customer specific.

INSTALLATION ENVIRONMENT REQUIREMENTS

   The following are physical requirements for installation.
   (Refer to the UTX/32 Installation Guide for detailed
   installation instructions.)

   +  One 9-track tape drive

   +  One terminal

   +  Adequate disk storage available (minimum of 160
      Mbytes)

   +  MICROSel or PowerNode 60xx or 90xx, configured with a
      single CPU or CPU/IPU pair.

   +  4 Mbytes of physical memory

      NOTE:  8 Mbytes of physical memory will be required in
      future releases of UTX/32.

ALTERABLE CONTROL STORE (ACS) MICROCODE UPDATE FILES

   Customers with PN60xx or SelCONNECTION machines received
   a separate tape containing the ACS microcode update files
   appropriate for their particular system when they
   purchased their system or with their UTX/32 Revision 2.1A
   SUS distribution.

   ACS Microcode Update Revision 4.0 or later must be used
   with UTX/32 Release 2.1B.  The ACS Microcode Update
   Revision 5.01 contains the following microcode files:

   +  C60.904D (nonprotect bit)
   +  C60.904G (protect bit)

   Use the following model number to order ACS microcode
   updates if you do not have Revision 4.0 or later.

                  ACS Microcode Update Files

                     Tape        Model Number

                 ACS Microcode   1935-1403






UTX/32 Software Release Notes                                      3-3








          DIFFERENCES BETWEEN UTX/32

   4  RELEASE 2.1A and RELEASE 2.1B
   ____________________________________________________________


   The major differences between UTX/32 Release 2.1A and
   UTX/32 Release 2.1B are:

   +  Diskless Sun support
   +  SPR resolutions

DISKLESS SUN SUPPORT

   Release 2.1B allows a Gould machine to be a boot and file
   server for Diskless Suns running the Sun Operation
   System, Release 4.0 or later.  Refer to Chapter 9 in the
   UTX/32 Operating Guide, and the following manpages, for
   more information.

   +  bootparam(3X)
   +  ethers(3N)
   +  ethers(4)
   +  bootparams(7)
   +  bootparamd(8)
   +  create_root(8)
   +  extracting(8)
   +  fix_bootparams(8)
   +  INSTALL(8)
   +  make_dirs(8)
   +  mkfile(8)
   +  ndbootd(8C)
   +  opt_software(8)
   +  setup_client(8)
   +  setup_exec(8)
   +  sunboot(8)
   +  verify_tapevol_arch(8)
   +  xdrtoc(8)

SPR RESOLUTIONS

   A substantial number of SPRs have been resolved in this
   release.  Refer to Chapter 8, SPRs Resolved in This
   Release.











UTX/32 Software Release Notes                                      4-1








   5  UPDATING YOUR SYSTEM TO RELEASE 2.1B
   ____________________________________________________________


   If you have already installed an earlier release of
   UTX/32, review the information in this chapter to ensure
   that you can install your new system correctly and that
   you do not lose any files when doing your update.

   For more information on installing Release 2.1B, refer to
   the UTX/32 Release 2.1B Installation Guide.  Do not use
   any other version of the Installation Guide, because the
   installation procedures are release-specific.

   Do the following before installing UTX/32 Release 2.1B:

   1. Save all the files that you intend to reinstall on
      your Release 2.1B system.

      At the very least, create a tape containing backup
      copies of /etc/passwd, /etc/group, and /etc/fstab.
      You may want to use the contents of your old
      /etc/fstab file rather than the distributed version,
      but it is recommended that you merge your group and
      passwd files with their new counterparts as this
      release may include new assignments of user ids.

      When making this tape, remember that you may want to
      install the files in a directory on the 2.1B system
      other than the directory in which they exist on your
      current system, to avoid overwriting files with the
      same names.  Consequently, do not use absolute
      pathnames.  Use only the relevant part of the files'
      pathnames, or prepend a dot and slash (./), as in this
      example:

         % cd /etc
         % tar cv ./passwd

      When updating to Release 2.1B, you can use the saveoff
      script in the /etc/system_setup directory to identify
      files in the / and /usr file systems that need to be
      backed up.  This script searches / and /usr for files
      that have been modified since your current system was
      installed, generates a list of all such files, allows
      you to edit the list, and creates a tape containing
      the files.

      It is recommended that you save all of your users'
      home directories as well as the following files so
      that they can be merged after Release 2.1B is
      installed on your system.




UTX/32 Software Release Notes                                      5-1








FILES FROM /etc

   /etc/ddn_seclevels
   /etc/ddn_userclass
   /etc/dumpdates
   /etc/eservices
   /etc/exports
   /etc/fstab
   /etc/ftpusers
   /etc/gated.conf
   /etc/gateways
   /etc/gettytab
   /etc/group
   /etc/hostdb_method
   /etc/hosts
   /etc/hosts.equiv
   /etc/hosts.local
   /etc/inetd.conf
   /etc/modcap
   /etc/motd
   /etc/named.boot
   /etc/named.boot.master
   /etc/named.cache
   /etc/named.db
   /etc/named.hosts
   /etc/named.local
   /etc/named.rev
   /etc/networks
   /etc/passwd
   /etc/phones
   /etc/printcap
   /etc/profile
   /etc/protocols
   /etc/rarp.hosts
   /etc/rc
   /etc/rc.boot
   /etc/rc.local
   /etc/remote
   /etc/rmtab
   /etc/rpc
   /etc/services
   /etc/shells
   /etc/syslog.conf
   /etc/sund.conf
   /etc/termcap
   /etc/ttys
   /etc/utmp

FILES AND DIRECTORIES FROM /usr/lib

   /usr/lib/Mail.rc
   /usr/lib/aliases
   /usr/lib/aliases.dir


5-2                               Updating Your System to Release 2.1B








   /usr/lib/aliases.pag
   /usr/lib/crontab
   /usr/lib/sendmail.cf
   /usr/lib/sendmail.domain.cf
   /usr/lib/sendmail.hf
   /usr/lib/sendmail.leaf.cf
   /usr/lib/sendmail.root.cf
   /usr/lib/sendmail.st

FILES FROM /usr/lib/uucp

   /usr/lib/uucp/L-devices
   /usr/lib/uucp/L-dialcodes
   /usr/lib/uucp/L.aliases
   /usr/lib/uucp/L.cmds
   /usr/lib/uucp/L.sys
   /usr/lib/uucp/USERFILE
   /usr/lib/uucp/setup.tblms
   /usr/lib/uucp/uu.daily
   /usr/lib/uucp/uu.hourly
   /usr/lib/uucp/uu.weekly
   /usr/lib/uucp/uucp.daily
   /usr/lib/uucp/uucpsummary
   /usr/lib/uucp/uucpsummary.monthly
   /usr/lib/uucp/uurate
   /usr/lib/uucp/uutbl
   /usr/lib/uucp/uuusage

DIRECTORIES

   /usr/adm
   /usr/etc/yp
   /usr/lib/find
   /usr/lib/term
   /usr/lib/tmac
   /usr/local
   /usr/spool
   /usr/tmp

   2. As an extra precaution, it is best to keep your
      current system on a separate disk pack until you are
      sure that the 2.1B system has been installed
      correctly.  Therefore, install Release 2.1B onto a
      disk pack other than the one on which your current
      system is installed.

      If you do not have a separate disk pack on which to
      install Release 2.1B, make a complete system backup
      onto magnetic tape.  Then transfer the files you
      expect to install onto your 2.1B system to a separate
      tape.  Do not use the complete system backup tape when
      trying to restore the saved files from your current
      release because you could inadvertently install your



UTX/32 Software Release Notes                                      5-3








      previous release on top of Release 2.1B.

      Release 2.1B requires more disk space than previous
      releases.  Therefore, the system disk may need to be
      repartitioned using prep(8).  Unlike the prep
      contained in Release 2.1A, prep now creates default
      partitions of an appropriate size for system
      installation.  Minimum partition sizes are:

      Partition         Contents                  Size
         a           root partition            25,000 blocks
         b           swap partition            20,000 blocks
         d           /usr.POWERNODE            70,000 blocks
                     /usr.POWERNODE/src       120,000 blocks

      After completing the installation of the Release 2.1B
      standard distribution, restore the files that you have
      saved to tape.

      To do this, you can use the si (simple install) script
      or the merge_files script. Both can be found in the
      /etc/system_setup directory.  These scripts
      conditionally restore each file on the tape, prompting
      you before copying the file to your new system.  Refer
      to the si(8) manpage.






























5-4                               Updating Your System to Release 2.1B








   6  PRODUCT HINTS
   ____________________________________________________________


   This chapter contains useful information that is specific
   to the Gould implementation of UNIX.

SUPPORT FOR REAL TIME PROGRAMMING

   Real time programming support is available for UTX/32
   programs written in C and FORTRAN.  The UTX/32 real time
   environment is available within the UTX/32 BSD
   environment.  Because some of the real time features are
   standard System V features, UTX/32 makes them available
   in the BSD environment by including them in the real time
   C library, librt.a, and the real time FORTRAN library,
   librtf.a.  All real time features are documented
   completely in the UTX/32 Release 2.1 Real-Time User's
   Guide and the UTX/32 Release 2.1 Input/Output Subsystem
   Guide.  These documents point to the appropriate manual
   pages for any given functionality.

   Some shared memory system calls in the C real time
   library cannot be used from FORTRAN because they use
   pointer variables.  The message and semaphore system
   calls in the C real time library are difficult to use
   from FORTRAN because of their liberal use of structures
   and defined constants.  For these reasons, the following
   system calls in the C real time library are not
   accessible through the FORTRAN real time library:

   +  msgctl
   +  msgget
   +  msgrcv
   +  msgsend
   +  semctl
   +  semget
   +  semop
   +  shmat
   +  shmctl
   +  shmdt
   +  shmget

   Console input/output is unavoidably slow and resource
   consumptive in the real time environment.  To avoid
   degrading overall system performance, do not use the
   console as a regular terminal for everyday working
   purposes.  Use the console only when performing the
   administrative tasks for which it is intended.

   The real time libraries are currently unsupported in the
   System V environment.




UTX/32 Software Release Notes                                      6-1








SUPPORT FOR COFF EXECUTABLES

   Beginning with Release 2.1 and continuing in Releases
   2.1A and 2.1B, UTX/32 supports the Common Object File
   Format (COFF) for executable and object files as well as
   the earlier a.out format.  COFF is an extensible
   definition for object files.  An a.out file contains
   segments only for text, uninitialized data, and
   initialized data, whereas a COFF file contains these
   segments and can also contain additional, special purpose
   segments.

   All executables in UTX/32 releases prior to release 2.1
   were in the a.out format.  All Release 2.1B executables
   are in COFF.  The Release 2.1B language tools produce
   COFF output files.  However, executables in both formats
   run under Release 2.1B, so existing user programs in
   a.out format do not need to be recompiled, with some
   exceptions as noted in the next section, entitled
   Implications for User Programs.

   The Release 2.1B link editor, /bin/ld, can be invoked
   with COFF object files, a.out object files, or both as
   input.  Other language tools also work with object files
   in either format as input.

   The default name for executable object files produced by
   the language tools remains a.out, even though those files
   are in COFF format.

Implications for User Programs

   A Release 2.1B COFF file can be constructed so that parts
   of the process image are loaded into named shared memory
   objects at run time.  This feature is an important part
   of the support for global commons and named datapools in
   Gould Common FORTRAN programs.

   In previous releases of UTX/32, the internal format of an
   a.out file was defined by structures in several different
   include files.  The organization of these include files
   has been streamlined and modified to support the internal
   format of COFF files.  Refer to the a.out(4) manpage.

   Symbol table entries in COFF files are one word longer
   than those in a.out files.  The nlist library routine has
   been modified to return a common data structure for
   symbol table entries from either COFF or a.out files.  As
   a result, user programs that use the BSD version of nlist
   continue to work correctly on a.out files but must be
   recompiled if they are to work with object files of both
   formats.  User programs that use the System V version of
   nlist must be recompiled.  In addition, existing user


6-2                                                      Product Hints








   programs that directly read the symbol tables of
   executables must be modified, much as nlist has been
   modified, to handle both kinds of symbol table entries.
   Refer to the nlist(3) manpage.

   In previous releases of UTX/32, macros could be used to
   determine the starting addresses of the various
   components of an executable file.  In a COFF file,
   however, the starting addresses of its components must be
   determined by scanning the section headers, which cannot
   be done with simple macros.  User programs that use the
   existing macros must be modified accordingly.

Implications for UTX/32 Utilities

   UTX/32 includes utilities, such as adb, that examine and
   manipulate the contents of object files.  In previous
   releases, these utilities were capable of handling only
   a.out executables.  In Releases 2.1A and 2.1B, these
   utilities execute with object files of both formats.  The
   following utilities have been modified to this end:

   +  adb
   +  dbx
   +  diff
   +  file
   +  gethertz
   +  gprof
   +  lint
   +  lpr
   +  make
   +  more
   +  nm
   +  nroff
   +  prof
   +  ranlib
   +  size
   +  span
   +  strings
   +  strip
   +  symorder

   The following utilities work with both formats because of
   the changes to the nlist library routine:

   +  analyze
   +  arp
   +  conf
   +  dmesg
   +  gcore
   +  iostat
   +  ipc




UTX/32 Software Release Notes                                      6-3








   +  ipu
   +  kgmon
   +  lastcomm
   +  netstat
   +  nfstat
   +  prot
   +  pstat
   +  route
   +  rpc
   +  rwhod
   +  sa
   +  savecore
   +  selio_trace
   +  swap
   +  sysline
   +  systat
   +  trpt
   +  trsp
   +  vmstat
   +  w
   +  XNSrouted

MEMORY CLASSES

   In previous releases of UTX/32, physical memory was
   homogeneous.  The system could allocate any available
   physical page to hold a requested virtual page of a
   process.  There was no way to ask for, or refer to, a
   particular physical page.

   Release 2.1A and 2.1B systems can be configured with
   several different classes of special memory, including
   reflective memory and shadow memory.  You can now
   implement shared memory objects to use particular areas
   of physical memory.  The config utility now allows
   creation of such objects at system configuration time.
   The memory classes facility also supports global commons
   and datapools in Gould Common FORTRAN.

   The memory classes implementation is based on System V
   shared memory objects.  Though the System V shared memory
   implementation has been slightly modified to support
   memory classes, it is compatible with existing binary
   programs.  The shmid_ds data structure, which is returned
   by the shmctl system call, contains five new fields in
   Releases 2.1, 2.1A, and 2.1B.  However, to maintain
   binary compatibility, Release 2.1B shmctl returns only as
   much information as Release 2.0 shmctl.  It does not
   return the five new fields, which have been added to the
   end of the data structure.

   The change is completely transparent to existing
   executables.  When an executable compiled under Release


6-4                                                      Product Hints








   2.1B invokes shmctl, as in the following example, the
   last five fields of the shmid_ds structure are unaffected
   by the system call:

      int                 shmid;
      struct shmid_ds     buf;

      shmctl (shmid, IPC_STAT, &buf);

   Refer to /usr/include/sys/shm.h for the definition of the
   shmid_ds structure.  Also refer to the shmctl(2RT)
   manpage.

   Refer to Chapter 12, Memory Classes, in the UTX/32
   Release 2.1 Real-Time User's Guide for more information
   about memory classes.

NO-SWAP KERNEL

   The UTX/32 kernel can execute in a no-swap mode, that is,
   no paging or swapping operations occur.  All programs
   executing under a no-swap kernel must fit into physical
   memory.  This mode can be enabled at boot time or at
   system configuration time using the real-memory
   directive.

   When the kernel is not running in the no-swap mode,
   swapping of an individual process can be disabled by
   invoking the -K option to ld.  A process that has been so
   linked is not swapped during its execution.  Only a
   superuser can execute a program linked with -K.  Refer to
   the ld(1) manpage.

TERMINAL INTERFACE

   The terminal interface code, which was formerly based on
   BSD tty, is now based on System V termio.  To maintain
   compatibility with existing software, the new terminal
   interface code emulates BSD tty functionality, so both
   interfaces are now fully supported.  The kernel include
   file /usr/include/sys/ioctl.h has been modified in ways
   that should affect only the kernel, and the kernel
   include file /usr/include/sys/termio.h is new for this
   release.  The new software is fully compatible with
   Release 2.0 at the ioctl system call level.

   The kernel data structure struct tty has been changed.
   User programs should not be affected by this, because
   references to the tty structure are typically restricted
   to the kernel. However, if user programs exist that
   contain references to struct tty, they require
   recompilation.  Refer to the termio(7) and tty(7)
   manpages.



UTX/32 Software Release Notes                                      6-5








ETHERNET DRIVER

   The Ethernet driver now supports true scatter/gather
   Direct Memory Access (DMA), which greatly decreases
   software overhead.  The Network File System (NFS)
   software is inoperable if the driver executes in mode 0.
   Mode 0 is considerably slower than modes 1, 2, and 3, so
   its use is not recommended.

SYSTEM CALL NUMBERS AND NEW SYSTEM CALLS

   System calls are distinguished by unique system call
   numbers.  The system call numbers 331 to 350 have been
   reserved for customer use.  Because they are not used by
   standard UTX/32 system calls in this or any future
   release, you are assured of the portability of system
   calls you write.  These reserved numbers are specified,
   along with all other system call numbers, in
   /usr/src/src/sys/syscall/syscalls.all.

   When you add a system call to the UTX/32 kernel, at least
   four different files must be updated.  In previous
   releases, you were responsible for updating these files
   manually.  Release 2.1B includes a utility, distsys, that
   automates the updating of these files.  For information
   about distsys, refer to the file
   /usr/src/src/sys/syscall/distsys.man.

SYSTEM V UTILITIES

   The following utilities are included in the System V
   environment for Release 2.1 and later releases:

   cron    The System V cron facility automatically
           schedules events, such as system accounting, that
           can be executed manually from a shell.  A system
           administrator can regulate the commands that a
           user invokes through System V cron.  BSD cron
           does not interfere with System V cron, so a
           system administrator can install and execute both
           on a UTX/32 system.  Refer to the System V
           cron(1M), and crontab(1) manpages.

   lp      The System V lp spooler system controls line
           printer jobs.  It allows an lp administrator to
           maintain different physical line printer devices,
           as well as groups of line printers called classes
           and their associated job request queues.  The
           System V and BSD lp facilities cannot execute
           concurrently on a UTX/32 system.  Refer to the
           System V accept(1M), enable(1) lp(1), lpstat(1),
           lpadmin(1M), and lpsched(1M) manpages.



6-6                                                      Product Hints








   sdb     This utility is a symbolic debugger.  sdb can be
           used to debug System V C and F77 programs.  It
           provides a controlled environment for executing
           such programs and can be used to examine their
           object files and core files.  Refer to the System
           V sdb(1) manpage.

   UUCP    The System V UUCP facility provides a way to copy
           files between UNIX systems.  It also allows
           remote system command execution and provides a
           means for limiting the commands that can be
           remotely executed.  The System V and BSD UUCP
           facilities cannot execute concurrently on a
           UTX/32 system.  Refer to the System V uucp(1C)
           manpage.

USER COMMANDS

   The following sections describe commands that have been
   modified.

   stty    The stty command has been modified in both the
           BSD and System V environments because of changes
           to the terminal interface (termio) code in the
           kernel.

           In both environments, the default terminal
           interface is the BSD interface, which is a
           superset of the System V interface.  A user in
           the BSD environment can switch to the System V
           terminal interface by specifying either the
           attusr option or the -bsdusr (i.e., not bsdusr)
           option to the BSD stty command.  In the BSD
           environment, specifying the -attusr (not attusr)
           option restores the BSD terminal interface.

           A user in the System V environment can switch to
           the System V terminal interface by specifying the
           -bsdusr (not bsdusr) option to the System V stty
           command.  In the System V environment, specifying
           the bsdusr option restores the default (BSD)
           terminal interface.

           Refer to the BSD termio(7) and stty(1) manpages
           and the System V stty(1) manpage.

   mt      The mt command can now be used to set and display
           the software and hardware retry counts for
           magnetic tape drives.  Refer to the mt(1)
           manpage.

   ps      Both the System V and BSD ps commands display the
           real time priority of real time processes, the



UTX/32 Software Release Notes                                      6-7








           standard UTX/32 priority of nonreal time
           processes, and whether the segments of a process
           are locked into memory via plock.

           In releases prior to Release 2.1, there were no
           real time priorities, so only standard UTX/32
           priorities were displayed.  Refer to the BSD or
           System V ps(1) manpage.

   talk    Release 2.1B talk, which is based on 4.3BSD talk,
           is incompatible with the Release 2.0 version,
           which was based on 4.2BSD talk.  The two versions
           also use different daemons.  The old version
           appears on Release 2.1B as otalk for
           compatibility with Release 2.0, and it uses
           /etc/talkd as its daemon.  talk is the new
           version, and it uses /etc/ntalkd as its daemon.
           Refer to the talk(1) manpage.

   ar and ranlib
           ar invokes ranlib whenever an archive has been
           changed.  In Release 2.0 and previous releases,
           you had to invoke ar and ranlib separately.  The
           Release 2.1B ar cannot be used with those
           previous versions of ranlib, but existing ar
           images can still be used in Release 2.1B, without
           conversion or modification.  Refer to the ar(1)
           and ranlib(1) manpages.

LANGUAGE TOOLS AND LIBRARIES


   /lib/libc.a and /usr/5lib/libc.a
           In the standard distribution of Release 2.1B, the
           crypt library routines in /lib/libc.a and
           /usr/5lib/libc.a allow encoding, but they do not
           allow decoding.  In Release 2.0 these libraries
           contained no encryption routines.  Instead, the
           standard bidirectional version of these routines
           was used to create system executables (e.g.,
           /bin/passwd).  Then the routines were removed
           from the source and binary distributions.

           Only domestic customers can receive a separate
           source or binary tape that includes the crypt
           modules.  The changes  to crypt were made to
           allow UTX/32 to comply more fully with U.S.
           export laws regarding cryptographic devices.

   /usr/lib/libm.a
           The math library, /usr/lib/libm.a, has been
           modified and must be assembled using the Gould
           Macro Assembler/X32, asmx32 (model 1433-07),


6-8                                                      Product Hints








           which is available separately from Release 2.1B.
           If asmx32 is not installed on your system, do not
           attempt to remake the math library.

SYSTEM CONFIGURATION AND INSTALLATION

   For complete information about configuring a UTX/32
   Release 2.1B system, refer to the UTX/32 Release 2.1B
   Operations Guide.  For information about installing
   Release 2.1B, refer to the UTX/32 Release 2.1B
   Installation Guide.  If you are upgrading your UTX/32
   system to Release 2.1B, refer to Chapter 5 of this
   document first.

/sys/Makefile and /sys/Makefile.exec

   The structure of the kernel makefile, /sys/Makefile, now
   supports a new technique for automatically generating the
   binary distribution's kernel makefile.  On binary
   systems, the only difference is the appearance of the
   kernel makefile.  On source systems, other differences
   are important to customers who generate new binary
   distributions.

   A system administrator creates a new kernel by executing
   make in /sys/obj, the kernel object directory.
   /sys/obj/Makefile invokes make in /sys, its parent
   directory.  On a binary system, the kernel makefile
   recompiles the system configuration files generated by
   /etc/config and links them with the kernel object modules
   in /sys/obj.  On a source system, the kernel makefile
   recompiles the kernel source files and system
   configuration files, and then links the resulting object
   files.

   Source customers can modify the kernel and update the
   kernel makefile.  Source customers can also generate new
   binary distributions, so a source customer must be able
   to generate a binary only kernel makefile.  On a source
   system, /sys/Makefile.exec contains a binary only version
   of /sys/Makefile, the kernel makefile.  Under previous
   releases, /sys/Makefile.exec had to be generated
   manually.  Now, to generate /sys/Makefile.exec in /sys,
   invoke the following command:

      # make Makefile.exec

   /sys/Makefile produces /sys/Makefile.exec by invoking the
   C preprocessor on itself and passing the output through
   several filters.






UTX/32 Software Release Notes                                      6-9








Makedev

   The MAKEDEV shell script, which creates device entries in
   the directory /dev, has been modified to allow creation
   of SCSI disk and tape device entries.  By default, SCSI
   disk entries are named /dev/sdn and /dev/rsdn, and SCSI
   tape entries are named /dev/stn and /dev/rstn, where n =
   device number.  MAKEDEV also supports a new option
   (-sttomt) that allows systems with only SCSI tape drives
   to be configured with SCSI tape entries named /dev/mtn
   and /dev/rmtn.  If SCSI tape device entries are so named,
   utilities such as mt, tar, and dump can use SCSI tape
   devices as their default devices, rather than forcing
   users to specify explicitly the SCSI tape devices as
   arguments to these commands.  Refer to the makedev(8)
   manpage.

Support for Alternate Root Devices

   Prior to Release 2.1, UTX/32 had to be booted from the
   device on which the root file system was mounted.  With
   Release 2.1 and later, UTX/32 can be booted from other
   devices as well.  This alternate root device capability
   can be enabled at system configuration time or at boot
   time.

Dynamic Allocation of Swap Partitions

   Prior to Release 2.1, devices eligible for swapping were
   specified at system configuration time. With Release 2.1
   and later, any disk partition not used for other purposes
   can be used for swapping.  The prep utility sets a swap
   eligibility bit in a disk partition, and the swapon
   program checks that bit before dynamically allocating the
   partition for swapping.  The eligibility check can be
   bypassed by specifying the -f option to the swapon
   utility.  Refer to the swapon(8) manpage.

Miniroot File System

   When a UTX/32 system is booted from the standard
   distribution tape, a minimally configured UTX/32 kernel
   executes, and a small root file system is mounted on a
   memory disk device.  A system administrator can execute
   the programs in this miniroot file system to configure a
   standard UTX/32 environment.  The administrator can
   subsequently mount a complete root file system and boot a
   standard kernel.

   The miniroot file system contains executable images of
   commands such as prep and fsck.  The existence of prep in
   the miniroot supplants the need for sprep, the standalone
   prep program, that was distributed in previous releases


6-10                                                     Product Hints








   of UTX/32.

Expanding the Size of the Root File System

   The person installing UTX/32 Release 2.1B can easily
   expand the size of the root file system.  Being able to
   expand the size of the root file system helps users who
   often keep more than one version of the kernel on the
   root file system.  The procedure for this expansion is
   completely described in the UTX/32 Release 2.1B
   Installation Guide.

Tools for Creating a Distribution Tape

   Releases 2.1A and later include new tools for the
   creation of a distribution tape.  Refer to the build-
   miniroot(8), fs-to-coff(8), and make-boot-tape(8)
   manpages for details.  For a complete description of the
   procedure for creating a boot tape, refer to Appendix D,
   Creating a Boot Tape, of the UTX/32 Release 2.1B
   Operations Guide.

/sys/obj/CONF.DIST

   This file contains the configuration information for the
   tape boot kernel, which is minimally configured and
   executes only during the installation of a complete
   UTX/32 system.  Its distinguishing characteristic is that
   it specifies the configuration of a memory disk to allow
   the tape boot kernel to execute without standard disk
   drives.

/usr/gould and /gould

   UTX/32 2.1B includes two new directory structures, /gould
   and /usr/gould.  Unbundled Gould Common Languages
   products should reside in these directories.  The
   commands in /gould are used during installation of the
   operating system and during stand alone operations.  You
   can also install other unbundled products in /gould.

GOULD COMMON FORTRAN

   In Release 2.1B of UTX/32, neither the routines nor the
   manual pages for the Gould Common FORTRAN intrinsics
   (library routines) are available as part of the standard
   Release 2.1B.  They are provided only to users who
   purchase Gould Common FORTRAN separately.

SYSTEM ADMINISTRATION

   This section discusses modifications to administrative
   commands, files, and directories, as well as the changes



UTX/32 Software Release Notes                                     6-11








   that pertain to system configuration and installation.

tboot and dboot

   The tape boot program, tboot, is the first file image on
   the boot tape.  It loads the remaining contents of the
   tape until it encounters the first double EOF and
   executes the second file image on the tape, which is
   typically a UTX/32 kernel.  The disk boot program, dboot,
   actually consists of two programs.  The first performs
   part of the boot procedure and invokes the second, which
   continues the process.

   When tboot or dboot loads a UTX/32 kernel, it sorts the
   kernel's COFF sections, by file position, prior to
   executing the kernel.  Because the kernel contains no bss
   section, the file position for the bss section is set to
   zero.  This causes tboot and dboot to clear bss before
   loading the kernel's other sections.  Because of this,
   the order in which the boot programs print section sizes
   during initial program load is different from Release
   2.0.  Refer to the boot(7) manpage for details.

prep

   The new prep program provides the same functionality as
   in UTX/32 2.1A.  It also uses larger default sizes when
   creating a and d partitions.  These partitions are 85%
   full after installation of the root (/) and 90% full
   after the installation of /usr.POWERNODE file systems
   when created with the new default sizes of 25,000 and
   70,000 blocks, respectively, increased from 21,000 and
   54,000 blocks, respectively.  Refer to the prep(8)
   manpage.

   Because prep is one of the executables in the miniroot
   file system on the boot tape, the standalone disk
   preparation program sprep is no longer distributed as
   part of UTX/32.

User IDs and Group IDs

   In previous releases, user IDs and group IDs ranged from
   0 to 65535.  However, the NFS software uses a negative
   number to represent a null user ID (user nobody).
   Release 2.1B user and group IDs range from -32768 to
   32767, the signed range that can be represented with the
   same number of bits as the previous unsigned range.
   However, use of negative user IDs and group IDs is
   restricted to the kernel NFS code; users are not allowed
   to use negative user IDs or group IDs.  System calls that
   return EINVAL upon receipt of an out-of-range user ID
   have been modified to check for the correct range.  Also,


6-12                                                     Product Hints








   the top 200 user IDs, those ranging from 32568 to 32767,
   are reserved.  You are warned against assigning user IDs
   in this range.

/etc/shutdown

   The setuid root permission for /etc/shutdown has been
   removed from the shutdown load module.  Only the
   superuser can perform a shutdown.  If you would like to
   allow users in group operator to be able to shutdown,
   then you should change the permission on /etc/shutdown to
   4750.  Refer to the shutdown(8) manpage.

Timezone Support

   Because the rules for daylight savings time (DST) in
   various parts of the world are sometimes changed
   (invalidating the information compiled into system and
   user programs) and because it is time consuming to relink
   old programs with a new time function, a mechanism allows
   a site administrator to update or otherwise change DST
   rules for every program by changing one file.

   For information on these functions and their impact on
   user programs, refer to the UTX/32 Release 2.1B
   Operations Guide and the ctime(3C), tzfile(4), zdump(8),
   and zic(8) manpages.

TIMER SERVICES

   Before using the timer services, jumper the interval
   timer hardware on the IOP or MFP at address 0x7e00 to use
   the 600 nanosecond count rate.  Consult your hardware
   field representative for information about modifying the
   count rate.





















UTX/32 Software Release Notes                                     6-13








   7   KNOWN PROBLEMS
   ____________________________________________________________


   This chapter describes all of the critical problems found
   in UTX/32 Release 2.1B software and documents.  The
   problems listed in this chapter come from the SPR
   database and from internal review.

   This chapter contains lists of problems that require
   special attention or that have workarounds.  For many of
   these problems, solutions are known and are scheduled for
   release on maintenance updates.

   Many of the problems have an SPR number associated with
   them.  These numbers allow you to track the progress of
   the problems and solutions to them.  The problems not
   associated with an SPR number are noted for informational
   purposes only.

KERNEL

   +  [No SPR]  Because the 2.1, 2.1A, and 2.1B kernels are
      larger than the 2.0 kernel, a pre-2.1 CONFIGURATION
      file may produce a kernel that cannot fit within the 4
      Mbytes alloted to the UTX/32 kernel by Releases 2.1
      and later.  If your kernel is too large because of
      this problem, the following warning and panic messages
      appear when your 2.1B kernel is booted:

      Map exceeds maximum of 0x###### allowed by 0x######
      panic: Sys pt too small

      To make your kernel smaller to solve the problem,
      reduce the number of buffers (nbufs), the number of
      users (nusers), the number of files (nfiles), or other
      similar parameters until your kernel is smaller than 4
      Mbytes.

DEVICE DRIVERS

   +  [SPR 88000839, SPR 88000841]  A bug in the line
      printer device driver prevents the System V lp spooler
      from operating correctly when it is connected to the
      system line printer parallel port.  More than one
      outstanding request to the line printer device driver
      renders the line printer unusable.  Under some
      circumstances, if formfeeds and characters are sent to
      the line printer, only the first character and the
      first formfeed are printed.





UTX/32 Software Release Notes                                      7-1








DIRECT FILES

   +  [SPR 88000849, SPR 88000850]  dfmkfs can create file
      system maps containing unnecessary holes or nonoptimal
      blocks.  This is because of bugs in this command's bad
      block avoidance algorithm.  Also, dfmkfs may abort
      during attempts to add user-specified flaws with
      automatic flaw detection.  These problems can be
      circumvented by the use of flawless media.

   +  [SPR 88000851, SPR 88000854]  dffsck cannot recover
      lost disk blocks.  Loss of blocks reduces the amount
      of space available on a direct file system disk but
      causes no other problems.  Also, dffsck cannot correct
      multiply mapped blocks.  A direct file system
      containing multiply mapped blocks may need to be
      remade using dfmkfs.

   +  [No SPR]  If a user process fails to close all direct
      files explicitly before terminating, other processes
      using direct files may experience difficulties.
      Processes may be unable to open more direct files,
      although processes may continue to access direct files
      that were previously opened.  This situation occurs
      because cleanup of direct files on exit of a user
      process is incomplete in two ways:

      [] Although exit has been modified to close direct
         files automatically, it does not unlock the volume
         or shared memory.

      [] No cleanup occurs when a process is terminated by a
         signal.

   +  [No SPR]  Application programs that invoke direct file
      system services should catch and handle explicit
      termination signals, such as SIGINTR.  SIGKILL cannot
      be caught or handled by application programs.

   +  [No SPR]  When a process using direct files terminates
      abnormally, its direct files are not closed.  This can
      cause subsequent processes to hang if they attempt to
      open a direct file.  To avoid this problem, the direct
      file system should be dismounted (using dfumount) and
      remounted (using dfmount) any time a process
      terminates without explicitly closing all its direct
      files.

   +  [No SPR]  Due to performance considerations, variable
      geometry SCSI disks are not recommended for use with
      direct file system utilities.





7-2                                                     Known Problems








UTILITIES

   +  [SPR 88000855]  System V TCSBRK ioctl does not work
      properly.  The break is sent only intermittently.

   +  [SPR 88000863]  /bin/adb incorrectly disassembles some
      encodings.  These show up as actual machine
      instructions when they are in fact undefined
      instructions.  The following examples demonstrate this
      problem.

               OpCode   Disassembled   Actual
                        As             Instruction

               0066     bei            undef
               756c     bu             undef
               5f5f     callm          undef
               0068     eae            undef
               0064     es             undef


   +  [SPR 88000847]  When auditing of inode-related
      activity is enabled, audit trail entries do not
      correctly specify the device on which an accessed
      inode resides.  This behavior is evident when auditing
      is enabled for chdir, link, mount, and rename.

   +  [SPR 88000853]  The escape to the shell from
      /usr/bin/tip does not work.

   +  [SPR 89000534]  The adb addr$p option core dumps.  The
      SPR contains the source code change required to fix
      the problem.

   +  [SPR 89000535]  There has been a change in packaging
      and the sprs_resolved_2.1 file is not provided on the
      distribution tape.  A list of resolved SPRs is
      provided in Chapter 8 of this Software Release Notes
      document.  The list includes the SPR number, status,
      module, and the short title from the data base.  If
      you require specific details, you can obtain them
      directly from the data base.

      Because of this change, enter n at the following
      simple_install prompt:

         Do you want the sprs_resolved_2.1 file (y,n):

      The simple_install script must perform the setup for
      localtime as documented in the UTX/32 Installation
      Guide.  You can do this step before or after executing
      simple_install.



UTX/32 Software Release Notes                                      7-3








   +  [No SPR]  The pix module is not included in the BSD
      Pascal tape.

   +  [No SPR]  The pi and px programs cannot successfully
      execute any Pascal program on UTX/32 Release 2.1B.

MISCELLANEOUS

   +  [No SPR]  Before the dump image of the distribution
      file system can be read from the boot tape during the
      installation of Release 2.1B, the boot tape must be
      positioned at the end of the COFF image of the
      miniroot file system.  Errors in revision E of the
      buffered tape processor firmware prevent the tape boot
      program from correctly positioning the boot tape at
      the end of the image of the miniroot file system.
      When installing Release 2.1B from a buffered tape
      processor with revision E firmware, execute the
      following commands after UTX/32 boots from the
      distribution tape:

      # mt -f /dev/rmt12 rewi
      # mt -f /dev/rmt12 fsf 4

      You can specify a different device number, if for any
      reason you do not wish to use device rmt12.  Though it
      should be necessary to execute these commands only
      when using a buffered tape processor with revision E
      firmware, they correctly position the tape no matter
      what type of tape processor is being used.

   +  [No SPR]  An IOP firmware bug prevents the IOP
      interval timer from being updated correctly under
      certain circumstances.  The high-resolution timer
      services are affected by this bug when they are
      configured to run from the IOP interval timer.

      A firmware update is available to correct this
      problem.  Contact Customer Services for more
      information.

DOCUMENTATION ERRORS

FORTRAN 77 Reference Manual

   +  The error numbers for FORTRAN runtime errors listed in
      Appendix F of the UTX/32 FORTRAN 77 Reference Manual
      used to begin at 100.  However, the addition of System
      V functionality to UTX/32 has caused the number of
      system errors to increase beyond 100.  To avoid
      overlap between system error numbers and FORTRAN error
      numbers, the FORTRAN error numbers have been
      renumbered beginning at 200.



7-4                                                     Known Problems








   +  The use of the $ format descriptor as described in
      section 12.10.5 of the UTX/32 FORTRAN 77 Reference
      Manual has changed to accommodate null characters.  If
      format (a$$) is used, null characters are generated
      instead of being ignored, and the endofrecord mark
      (linefeed) is suppressed.  Changes were made to
      format.c and wrtfmt.c in libI77 to recognize the
      doubling of the $ format specifier.  Single uses of
      the $ format specifier, i.e., (a$), work as described
      in section 12.10.5.













































UTX/32 Software Release Notes                                      7-5








   8  SPRs RESOLVED IN RELEASE 2.1B
   ____________________________________________________________


   This section lists the Software Problem Reports (SPRs)
   filed against UTX/32 that were resolved during
   development of Release 2.1B.

   You can check on the status of any UTX/32 SPR by logging
   on to a system at Gould CSD in Fort Lauderdale.  This
   procedure is discussed in the section, Online Viewing of
   SPRs.

   To learn how to report new problems with UTX/32 Release
   2.1B software and documents, refer to the section, UTX/32
   Problem Reporting.  Some new reporting mechanisms are now
   available.

LISTING OF RESOLVED SPRs

   Table 8-1 lists SPRs whose resolutions have been
   incorporated in UTX/32 since Release 2.1A was
   distributed.

                           Table 8-1
       Software Problem Reports Resolved in Release 2.1B


                 Module &
SPR Number        Change                               Title
 85100092    span                All the data + text won't fit into near text.
             CURRENT REL

 85100515    admin               "admin -i" strips "null" characters from the
             DOC CHANGE          file.

 85100656    path                Security compromised by "." near beginning
             CODE/DOC            of root's $path (or $PATH).

 85100681    dbx                 Deleting and adding trace conditions causes
             CODE CHANGE         internal errors.

 85100687    dbx                 Interrupts meant for "dbx" get passed to the
             CODE CHANGE         program being debugged.

 85100701    as.o                Performance is slower than VAX when doing
             EXPL IN DIS         write and read sequentially.

 86100964    nroff               Epson FX80 terminal driving table for "nroff"
             CODE CHANGE         missing some escape codes.






UTX/32 Software Release Notes                                      8-1








                 Module &
SPR Number        Change                               Title
 87000097    cc(1) man page      "cc" man page has typo ..."original."
             DOC CHANGE

 87000129    delta               The "delta -g" option is not ignoring  the
             DOC CHANGE          specified delta.

 87000132    mesg                "mesg" (bsd environment) does not let you
             CODE/DOC            redirect error mesg. (Pos Fix)

 87000159    spell               Diagnostic produced when SV "spell" used.
             CODE CHANGE         "spellhist" not distributed.

 87000268    dump                "dump" frequently runs past the eot on long tapes.
             EXPL IN DIS

 87000275    boggle              "boggle" is not listing the words from
             CODE/DOC            /usr/dict/words.

 87000315    battlestar          "battlestar -r" yields Illegal instruction
             CODE CHANGE         and core is dumped.

 87000324    chgrp               Cannot "chgrp" on tftp to -2. Causes "unknown
             CODE/DOC            option" error message.

 87000363    src/sys/h/stat.h    Field st_dev returned incorrectly unless
             CODE/DOC            file is a disk file(misunderstanding).

 87000502    fwrite              Standard I/O library does not handle
             EXPL IN DIS         interrupted write calls properly.

 87000503    cc(1) man page      "cc -lm" produces Undefined: _pow.
             DOC CHANGE

 87000522    dbx                 "dbx" internal variables are not recognized,
             CODE CHANGE         i.e., $hexoffset and $frame.

 87000638    date                "date" does not allow suid use.
             CODE CHANGE

 87000781    /usr/5bin/cc        /usr/5bin/cc comparisons of a char to
             CODE CHANGE         negative int will never match.

 87000875    acctdusg            acct diskusage used units of 512 byte blocks
             CODE CHANGE         instead of 1024.

 87001174    MAKEDEV             MAKEDEV script doesn't handle controller
             CODE CHANGE         name "sb" for HSDs.






8-2                                      SPRs Resolved in Release 2.1B








                 Module &
SPR Number        Change                               Title
 87001220    nfs                 NFS transfer rates perceived lower than
             EXPL IN DIS         expected.

 87001226    yppasswd            Changing password with "yppasswd" fails to
             UNAB TO DUP         find entry in /etc/passwd file.

 87001253    heap_kmem.c         Nfsd daemons remain in state D under heavy
             EXPL IN DIS         NFS load.

 87001406    ypprint             yprint -s <ypmaster> error '. order number
             EXPL IN DIS         .' xfering mail aliases yp map

 87001467    yp*                 Yellowpages lookup core dumps when going to
             EXPL IN DIS         the database.

 87001575    sort                "sort" is slower under 2.0 than 1.2u02.
             CODE CHANGE

 87001586    -ms macros          -ms macro prints page #s center and right
             CODE CHANGE         when using BSD "thesis" format (.TM).

 87001597    biff                "biff" notification of mail for user on pty
             TEMP SOL            does not work.

 87001617    ncheck              "ncheck" hash table size too small.
             CODE CHANGE

 87001715    as.c                Modem ports should drop DTR and RTS when set
             CODE CHANGE         to off in /etc/ttys.

 87001725    trap.c              "dbx" of a short program causes the system to
             CODE CHANGE         panic, sv pipe causes Addr Spec.

 87001791    vi                  With auto write set, commands to switch to next
             CODE CHANGE         file may cause corruption of last
                                 line.

 87001792    atrm                PROT error if the "at" queues are empty
             CODE CHANGE         and "prot abort" is set.

 87001795    /usr/ucb/ex         "ex" fails to continue executing a here file
             DOC CHANGE          if there is a failure.

 87001815    adjtime             Anomaly in line freq clock if clock rate
             CODE CHANGE         doesn't divide rationally into 10000000.

 87002047    lpr                 "lpr" allows for removal of files
             CODE CHANGE         by other than root user.






UTX/32 Software Release Notes                                      8-3








                 Module &
SPR Number        Change                               Title
 87002117    as.c                panic: ioi: dtimeout - bad state.
             CODE CHANGE

 88000080    diff                "diff" fails when last line doesn't end with
             CODE CHANGE         a <CR> and last 2 chars are the same.

 88000226    as.c                8-line does not recognize that a port has
             CODE CHANGE         been dropped by a switch.

 88000232    pi/px               Boolean variables are always evaluated as
             CODE CHANGE         false even when true.

 88000318    kern_acct.o         Possible inappropriate reuse of inode/vnode
             CODE CHANGE         occurred on a heavily loaded system.

 88000332    exports             More secure if "rcp.mountd" were mod. to allow
             EXPL IN DIS         mounting of dir. rather than fs.

 88000382    tip(1c)             "tip" does not work sending files to device
             CODE CHANGE         that supports ^S/^Q.

 88000393    nfs                 NFS needs to allow some kind of limited
             CURRENT REL         super user access.

 88000416    /bin/login          "write" and "talk" do not work under u06, mode
             CODE/DOC            of login tty changed from 622 to 620.

 88000434    make SV             When SysV encounters a long dependacy it
             CODE CHANGE         aborts without an error message.

 88000446    RJE                 During initialization of RJE, inquiry sent,
             CODE CHANGE         expecting an ACK but get a NAK.

 88000473    RJE                 Add "haltio" in SIGTERM catcher, for
             DUPLICATE           shutdown of RJE subsystem (DUP 88002291).

 88000477    RJE                 Missing end of frame marker. Need to issue
             CODE CHANGE         another read.

 88000485    RJE                 RJE should issue a sense down to the SCM
             CURRENT REL         when a read fails to take approp action.

 88000628    nfsd                NFSD hang in disk wait state and the only
             EXPL IN DIS         way to get them back is to reboot.

 88000629    make                "make" doesn't always make a good kernel after
             CODE CHANGE         2.0u06 is installed.






8-4                                      SPRs Resolved in Release 2.1B








                 Module &
SPR Number        Change                               Title
 88000685    uusend              "uusend" core dumps because no verification of
             CODE CHANGE         successful open of pipe is done.

 88000739    /etc/netgroup       Mounting of remote files across net not
             UNAB TO DUP         controlled according to netgroup file.

 88000776    MAKEDEV             Ramdisk permission problem/solution
             CODE CHANGE         included.

 88000789    pmap_rmt.c          Yellow pages rup doesn't work with subnetting,
             CODE CHANGE         fix included in suppinfo.

 88000837    sv_sys2.c           SV commands may not display entire dir,
             CODE CHANGE         (large dir which has had numerous "rm"s).


 88000838    script              csh> script- suspend sequence locks
             CODE/DOC            up terminal.

 88000840    cpuipu.c            RT process running on IPU does not process
             CODE CHANGE         signals until rescheduled (TS).

 88000842    pstat,pstat.8       "pstat". Manpage and code need updating for RT
             CODE/DOC            features and IPU scheduling FLAGs.

 88000860    dk.c / sd.c         Locked inodes hang system, requiring
             CODE CHANGE         a reboot of the system (TS).

 88000869                        Direct I/O doesn't do IOCL conversions
             CODE CHANGE         correctly for HSD (class E device).

 88000870    iostat              Error in "iostat," only 'dk' drives are
             CODE CHANGE         supported because of hardcoding.

 88000871    refer               Several test run on "refer" do not work.
             CODE CHANGE

 88000924    rjestat             Report link down if retry limit exceeded.
             CODE CHANGE

 88000938    shutdown            Occassional problem with "shutdown -r"
             CODE CHANGE         failing to shutdown.

 88000963    RJE                 Improve throughput using select system call
             CODE CHANGE         versus alarm in rjexmit.c.

 88000964    f.gendad            The file f.gendad is revision D for the GBB
             CURRENT REL         microcode - upgrade to rev D+.






UTX/32 Software Release Notes                                      8-5








                 Module &
SPR Number        Change                               Title
 88001159    hsctimer            "hsctimer" - problem with 10ms granularity.
             PROB VER            Clock ALRM sleeps for long periods.

 88001171    /usr/ucb/ex         Protection violation with "ex."
             UNAB TO DUP

 88001276    makewhatis          /usr/lib/makewhatis: arg list too long.
             CODE CHANGE         Problem - workaround provided.

 88001288    vfs_bio.o           System has had randoms panic:free: freeing
             CODE CHANGE         free frag.

 88001311    rup                 "rup" without argument when using YP -->
             EXPL IN DIS         auth_unix:nfs_abort.

 88001312    mount               NFS messages - NFS server XXX not
             EXPL IN DIS         responding, still trying.

 88001382    group(4)            Doc states /etc/group 200 member max. BUFSIZ
             PROB VER            limit of 1024 prevents this amount.

 88001406    execve()            panic: exec EFAULT - execve() not checking
             CODE CHANGE         exit status of fuword() properly.

 88001407                        panic: bad rmfree - caused by the SV
             CODE CHANGE         messages code.

 88001408                        panic: pagein vread when heavily loaded -
             CODE CHANGE         aggravated by 2MB kernel, ptes trashed.

 88001459    idp_forward         panic: mcldup - XNS broadcast packet -
             CODE CHANGE         header information processed incorrectly.

 88001495    makefile            Error in makefile(2.0U06) prevents src
             EXPL IN DIS         customers from compiling src.(Workaround).

 88001607    gprof.1             Manpage for "gprof -b" option incorrectly
             DOC CHANGE          states capabilities of option.

 88001660    tabs                Problems using "tabs" and "tset", no
             DOC CHANGE          documentation reference to setting tabs.

 88001917    prep                "prep" is marking all single sector flaws as
             CODE CHANGE         multisector flaws on HSDPs.

 88001918    prep                One of the format options of "prep" not using
             CODE CHANGE         the Primary Defect List (SCSI).






8-6                                      SPRs Resolved in Release 2.1B








                 Module &
SPR Number        Change                               Title
 88002004    shutdown -l         "shutdown" under 2.1 does not have the option
             CODE CHANGE         to warn NFS users of a shutdown.

 88002219    fingerd.c           "fingerd" can be tricked to execute a remote
             CODE CHANGE         shell by overflowing stack (gets).

 88002228    ftpd.c              Globbing in assoc. with anonymous "ftp" allows
             CODE CHANGE         user to break out of chroot's dir.

 88002272    rje                 A job sent to the host is not being
             CODE CHANGE         acknowledged.

 88002273    rjefsm              Retry counters added for establishing a link
             CODE CHANGE         to the IBM.

 88002274    rje                 "squeue" directory has wrong permissions.
             CODE CHANGE

 88002276    rjedisp             Permissions must be set for "others".
             CODE CHANGE

 88002275    rjestat             /usr/bin/rjestat wrong permissions.
             CODE CHANGE

 88002281    rje                 "joglog" needs 666 permissions.
             CODE CHANGE

 88002282    rje                 Bad stats in "rjeinit."
             CODE CHANGE

 88002283    rje                 "shqer" does not die when the "rjehalt"
             CODE CHANGE         utility is initiated.

 88002285    rje                 Increase halt delay.
             CODE CHANGE

 88002286    rje                 Save response file.
             CODE CHANGE

 88002288    rje                 Ioctl call fails but does not let RJE user
             CODE CHANGE         know.

 88002291    rje                 "haltio" in SIGTERM handler needed.
             CODE CHANGE

 88002292    rje                 No SIGTERM handling in "shqer."
             CODE CHANGE







UTX/32 Software Release Notes                                      8-7








                 Module &
SPR Number        Change                               Title
 88002293    rje                 "rjestat" for queued files.
             CODE CHANGE

 88002294    rje                 System V call "ustat" is broken.
             CODE CHANGE

 88002295    rje                 "rjefsm" sigterm handling.
             CODE CHANGE

 88002296    rje                 Lower qdelay time in rje.h.
             CODE CHANGE

 88002303    sanalyze            "sanalyze" aborts with a illegal instruction.
             CODE CHANGE

 88002304    sanalyze            "sanalyze" giving "event not found" for common
             CODE CHANGE         events.

 89000023    config              Support for 5th IOP not in UTX/32 2.1. (SPR
             CODE CHANGE         88000726 did not fix problem).

 89000070    as.c                Ports hang. Stacktrace shows sleeping on
             CODE CHANGE         maintid. TD_WIOCTL is set in dstate.

 89000133    i_selio_e.c         "ioi_physr_e" only copies IOCB when virtual
             CODE CHANGE         address must be translated.

 89000151    /bin/passwd,        Security leak in /bin/chfn or "passwd -f."
             CODE CHANGE

 89000191    setslogdetails      "logging" spelled "loggin" in login.c.
             CODE CHANGE

 89000213    quota               Login slower on a system with numerous
             CODE CHANGE         mounted file systems - fix in "quota."

 89000496    dk.o                Mirroring multiple partitions in
             CODE CHANGE         background-> panic: dk_intr: unexpected.
                                 state=0



ONLINE VIEWING OF SPRs

   Gould CSD Customer Services maintains a database for
   UTX/32 SPRs.  To examine its contents, use a modem to log
   on to a UTX/32 system at Gould CSD in Fort Lauderdale.
   Dial (305) 797-5837 and log in as cstspr.  Be sure the
   modem is set to:




            8-8                                      SPRs Resolved in Release 2.1B








               +  1200 baud
               +  Full duplex
               +  8-bit characters
               +  One stop bit
               +  No parity

               Report any difficulties with the online database to 1-
               800-TECHAID.

            UTX/32 PROBLEM REPORTING

               There are now three ways to report problems with UTX/32
               Release 2.1B software and documents.

               +  call a toll-free telephone number
               +  fill out an SPR form
               +  use a utility that transmits SPRs via electronic mail

               The following sections give more information on the use
               of these methods.

            By Telephone

               To report a software or documentation problem by
               telephone, within the U. S. A., call a customer service
               representative at 1-800-TECHAID.  You are asked to
               provide the following information:

               +  The call number (if this is a follow-up call)
               +  Your name
               +  Company name
               +  System number
               +  Telephone number
               +  Machine type
               +  Operating system and revision number
               +  Product and revision number
               +  Problem description

               If possible, have an auto-answer modem connected to the
               appropriate UTX/32 system.  Customer Services personnel
               should then be able to provide remote hardware or
               software support.

            With SPR Forms

               A software or documentation problem can be reported by
               filling out an SPR form and sending the form with the
               appropriate supplemental information to the address
               indicated on the form.  Forms can be obtained from your
               local Gould CSD Office.






            UTX/32 Software Release Notes                                      8-9








            Using Electronic Mail Using gouldspr

               If the /usr/gould/bin/gouldspr utility and UUCP utilities
               have been installed on your system, you can use
               /usr/gould/bin/gouldspr to submit an SPR using electronic
               mail.  This menu-driven utility allows you to create and
               update SPRs, mail them to Customer Services, and view
               SPRs that have been generated at your site.  Refer to the
               gouldspr(1) manpage.

               To install /usr/gould/bin/gouldspr, perform the following
               steps:

               1. Be sure UUCP is installed on your system.  Refer to
                  the UTX/32 Release 2.1B Operations Guide for
                  information about installing UUCP.

               2. Be sure the directory /usr/gould/bin is in the users'
                  search paths.  The standard .login file distributed
                  with Release 2.1B contains a correct specification for
                  the search path, but if you are upgrading from an
                  earlier release, users must add this directory to
                  their search paths.

               3. You may want to use cron to send SPRs to Customer
                  Services on a regular basis.  To do this, create an
                  entry in /usr/lib/crontab or /usr/lib/crontab.local
                  such as the following:
                  crontab: 00 TT * * 1-5 uucp /usr/lib/uucp/uucico -r1 &

                  In the example above, TT is the time of day at which
                  SPRs are to be sent using uucico.  Refer to the
                  cron(8) manpage.

               4. Call Customer Services at 1-800-TECHAID and inform
                  them of your system name and ID number.  Please state
                  that you are providing the information for the
                  purposes of electronic submission of SPRs.

               5. When first invoked, the /usr/gould/bin/gouldspr
                  utility prints a message saying that the utility is
                  disabled until UUCP is installed.  Once the previous
                  steps have been completed, edit
                  /usr/gould/bin/gouldspr and delete the lines that
                  cause this message to be printed.  The lines to be
                  removed are clearly surrounded by comments.









            8-10                                     SPRs Resolved in Release 2.1B


