


         ------------------------   Preface  ------------------------



         Preface

         This document provides the information needed to install and
         run RX/V Release 1.1 on your Ridge 32 or Ridge 3200.

         The first subject covered is a brief description of the
         contents of RX/V Release 1.1.  This is followed by a
         detailed description of the release media format.  Detailed
         instructions on performing the actual installation of the
         release are provided.  Various tips on how to install
         additional packages as well as administrative pitfalls to
         avoid are covered following these instructions.  Summaries
         of problems fixed since RX/V Release 1.0, known outstanding
         problems and the documentation available for the release are
         provided.  The final topic covered is the proper procedure
         to follow to ask questions and report problems that you
         encounter in the use of RX/V Release 1.1.

         In addition, information is provided on RBUG and the device
         drivers supplied with the system software.

         Throughout this document there are samples of actual
         terminal sessions.  These examples are captured from work
         done on one of our development systems at Ridge Computers.
         The host name is tehama and its configuration is given in
         the table at the end of this section.  The sample console
         sessions appear like:


           1  This is output from the system.
           3  This is output followed byusertinput[]anduthen[more
           4  Thisuisba reallyslong line of text that has wrapped
              woulddlooksinwoneuofothe sample consolensessions.ut


         The number in italics is simply a line number used for
         reference purposes in the text.  Such a reference looks
         like:  {2}.  The line numbering is reset in each section.

         The fixed pitch text is output from the system.  The bold
         text is input typed by the user.  The [] character
         represents the RETURN key being pressed.
                    _____________________________________
                    |_________|__________________________|
                    |_________|__________________________|
                    |_________|__________________________|
                    | discs   | 2 unc0d0ois2ac300mbllers |
                    |_________|__________________________|
                    |  tape   | stwithrSTCa2925odriveler |
                    |_TABLE_1.|_Configuration_for_tehama_|



         004-5030              RX/V Release 1.1               Page  1








         ------------------------   Preface  ------------------------



         RX/V Release 1.1 Introduction

         RX/V Release 1.1 is an update to RX/V Release 1.0.  Its
         primary purpose is to provide new features and resolve
         outstanding customer problems.  This software is based on
         UNIXr System V Release 3.0 and System V Release 2.0 VAX
         11/780 Version 2.

         New features include:

                                                                   o a
                                                                     DR11
                                                                     driver
                                                                     for
                                                                     TEK
                                                                     412X
                                                                     displays
                                                                   o a
                                                                     tape
                                                                     driver
                                                                     for
                                                                     the
                                                                     Storage
                                                                     Technologies
                                                                     2925
                                                                     tape
                                                                     drive
                                                                   o support
                                                                     for
                                                                     up
                                                                     to
                                                                     8
                                                                     CIO
                                                                     boards
                                                                     -
                                                                   o the
                                                                     route(1m)
                                                                     and
                                                                     routed(1m)
                                                                     commands
                                                                   o the
                                                                     truncate(2)
                                                                     and
                                                                     ftruncate(2)
                                                                     system

         __r_______
             UNIX is a registered trademark of AT&T.
           - hardwareoinmthe form ofua new powerssupply.quire special




         Page  2               RX/V Release 1.1              004-5030








         -------------   RX/V Release 1.1 Introduction  -------------



                                                                     call
                                                                   o support
                                                                     for
                                                                     DTC
                                                                     connected
                                                                     serial
                                                                     printers
                                                                   o a
                                                                     utility,
                                                                     xsys,
                                                                     to
                                                                     display
                                                                     the
                                                                     hardware
                                                                     configuration
                                                                   o a
                                                                     utility,
                                                                     readlr,
                                                                     to
                                                                     display
                                                                     main
                                                                     memory
                                                                     ECC
                                                                     activity

         Optional software supported by this release include:

                                                                   o RISC
                                                                     optimized
                                                                     FORTRAN
                                                                     and
                                                                     Pascal
                                                                     compilers
                                                                   o TranScript
                                                                   o Documenter's
                                                                     Workbench
                                                                   o the
                                                                     enhanced
                                                                     symbolic
                                                                     debugger
                                                                     CDB

         As this is not a major release there are no printed manual
         updates being produced.  However, several corrections have
         been made to the online manual pages.  Where you have
         questions it is recommended that you consult the online
         manual pages.






         004-5030              RX/V Release 1.1               Page  3








         --------------    Release Media Organization  --------------



         Release Media Organization

         RX/V Release 1.1 is distributed on 1/4 inch cartridge tape.
         In addition to the RX/V distribution cartridge each system
         is shipped with a Standalone Utility System (SUS)
         distribution cartridge and one badblocks cartridge for each
         of the discs on your system.

         The SUS cartridge provides stand alone diagnostics and
         utilities which include the utilities to format the disc
         drive(s) on your RX/V system.  A complete description of the
         SUS distribution media is shipped with each SUS release.
         The use of the SUS to format discs appears later in the
         section on installation of RX/V.

         Badblocks cartridges contain the defective space information
         for disc drives.  The badblocks cartridge for a disc drive
         is needed any time the disc is to be formatted.  If the
         badblocks cartridge is lost or damaged, formatting your disc
         will be very time consuming taking many hours at best.

         While it is possible for a badblocks cartridge to contain
         information for any number of disc drives, there is usually
         only one badblocks image per cartridge.

         Standard Files

         The release cartridge contains a series of files.  Most of
         the files on the cartridge are actually pairs of files
         referred to here as bundles.  Each bundle is two separate
         cpio archives.  The first includes files used to control the
         installation of the second file.  Below is a list of the
         files (and their order on the media):

         release description
                   This file on the distribution cartridge contains a
                   copy of this document suitable for printing on a
                   line printer.


                     1  #cat /dev/rct/0 > /dev/lp[]

         tape boot
                   This program knows how to cold boot (i.e., no
                   image on disc) the system from 1/4 inch cartridge
                   tape.

         disc boot
                   This program is normally loaded from the disc when
                   the system is booted.  It knows how to load the
                   image of the kernel to be run.  It is placed on


         Page  4               RX/V Release 1.1              004-5030








         --------------    Release Media Organization  --------------



                   the disc by the tape boot program.

         raw root file system
                   This file contains a copy of the default root
                   partition.  This file provides a physical copy of
                   an RX/V root file system used for cold booting
                   RX/V Release 1.1.  This file consists of 16384
                   blocks of length 1024 bytes.

         raw miniroot file system
                   This file contains a copy of the mini root
                   partition.  The mini root provides enough
                   functionality to complete the installation of the
                   remainder of the cartridge.  It is used in
                   disaster recovery and to install RX/V Release 1.1
                   as an update to an earlier release of RX/V.  This
                   file provides a physical copy of a minimal root
                   file system.  This file consists of 4096 blocks of
                   length 1024 bytes.

         cpio bundle of /
                   These files contain the cpio archives for the root
                   partition.  This is normally only used to update
                   the software on your system.

         cpio bundle of /usr
                   This pair of files contains the cpio archives for
                   the usr (/usr) partition.

         cpio bundle of manual pages
                   These files contain the cpio archives for the
                   online manual pages.

         Remaining Files

         With the exception of the last bundle, the remaining bundles
         contain optional software and therefore may not appear on
         your distribution cartridge.  These bundles may appear in
         any order on the distribution cartridge.  In addition, there
         may be other optional bundles on your distribution
         cartridge.












         004-5030              RX/V Release 1.1               Page  5








         --------------    Release Media Organization  --------------



                    ___file_______________________________
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|
                    |_______|_____________________________|

                 Figure 1.  RX/V Release 1.1 Cartridge Format








































         Page  6               RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



         Installation Procedures

         This document discusses three different installation
         scenarios:

           1.  Installing RX/V from scratch.
           2.  Updating an existing RX/V system.
           3.  Installing optional software purchased separately from
               the system software.

         If your system was shipped as an RX/V system you should not
         need to install RX/V from scratch.  Systems are shipped with
         the latest release of RX/V and any options ordered already
         installed.

         In many of the installation instructions there is reference
         made to booting RBUG.  If you are not familiar with RBUG,
         see the section titled ``Booting RBUG'' near the end of this
         document to familiarize yourself with this procedure.

         If you are updating an RX/V Release 1.0 system you should
         skip forward to the ``Installing an RX/V Update''
         instructions.

         If you have a Parts and Accessories (P&A) distribution
         cartridge you should skip forward to the ``Installing P&A
         Cartridges'' instructions.

         If you want to install the RX/V software from scratch
         continue with the next section.

         Installing RX/V from Scratch

         The installation of RX/V Release 1.1 from scratch consists
         of several steps:

           1.  The disc drive(s) are formatted and prepared for RX/V
               use.
           2.  The root file system is installed.
           3.  The partitioning of the disc is established.
           4.  The /usr file system is installed.
           5.  Other packages, such as Documenter's Workbench or
               TranScript, are installed.
           6.  System files are customized for your installation's
               use.

         The following sections provide detailed explanations of
         these steps.





         004-5030              RX/V Release 1.1               Page  7








         ----------------   Installation Procedures  ----------------



         Disc Formatting

         If the disc(s) to be used for RX/V have already been
         formatted with SUS 4.1 or later then you can skip this
         section.

         Formatting the Primary Disc

           1.  Put the SUS distribution cartridge into the drive and
               set the drive locking handle in its upright position.
               You must have SUS 4.1 or later.  Do NOT use SUS 4.0.
               SUS 4.0 contains a serious error that can cause data
               loss if it is used to format your disc.  The cartridge
               rewinds when put into the drive.

           2.  Boot RBUG and use the c command to load SUS.  RBUG may
               respond with an error number such as 00000300.  This
               usually means that the cartridge tape drive is not yet
               reset.  Simply wait 10 to 15 seconds and try the
               command again.


                 2  RBUGs(08-May-87)sPC=00042000
                 4  Ridge Computers Stand-alone Utility System
                 6               Version 22-Jul-87


           3.  Invoke the dir command of SUS.  This will load the dir
               command and display the contents of the SUS
               distribution cartridge.  This step is necessary to get
               the dir command loaded for the next step.

                 7  SUS> dir[]
                 9        ==============
                11    no  file name          size(byte)
                13     2  DISCUTIL           143457
                15     4  DISPDIAG            14609
                17     6  SMDDIAGL            43457
                19     8  DR11DIAG            51761
                21    10  HEXDUMP              2385


           4.  Insert the badblocks cartridge for the disc that is
               about to be formatted into the cartridge tape drive
               and set the drive locking handle in its upright
               position.

           5.  Now invoke the dir command again.  This time note the
               name(s) of the files on the cartridge.




         Page  8               RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



               Most badblocks cartridges contain one file named
               BADBLOCKS.  You may have a cartridge with multiple
               badblocks files.  If so, the files are usually named
               bb.nnnnn where nnnnn is the manufacturers serial
               number for the disc drive.


                23  SUS> dTape Directory
                25    no  file=name=====     size(byte)
                27     1  BADBLOCKS             900


           6.  Put the SUS distribution cartridge into the drive and
               set the drive locking handle in its upright position.

           7.  Using the discutil command of SUS load the discutil
               program.  The discutil program takes about three
               minutes to load from the SUS distribution cartridge.
               By default the discutil program uses unit number 0 on
               the lowest numbered controller.  This is usually the
               appropriate disc in this step.

               See the SUS release notes for a complete list of
               discutil commands.

               If the version number displayed by discutil is less
               than 4.1, do not continue.  Locate a newer SUS
               cartridge and then return to the beginning of this
               section.

                28  SUS> discutil[]
                30  Disc Utility System for RX/V or ROS
                32          Version 4.1 22-Jul-87


           8.  Turn discutil's safety option off by issuing the
               safety command.

                33  DU> safety[]
                34  Safety is now off.

           9.  Format the disc using the format command of discutil.
               The actual formatting of the disc will take about two
               minutes for every 150 megabytes of capacity.

               If the disc does not contain valid disc skewing
               information discutil will ask for the values while
               suggesting default values {36-39}.  It is advisable to
               use the standard skew values.  These values differ
               from one disc model to another.



         004-5030              RX/V Release 1.1               Page  9








         ----------------   Installation Procedures  ----------------




                36  DiscfPaget3]Contains Invalid Disc Skewing
                37  hitoreturnnto enter the default standard values
                39   Enter Track to Track Skew: (4) []
                41  HeadattonHeadscSkew = 0
                43  Doayoutwantato usewthese standard values ? (y)
                44  Track 0
                46  Track 50.
                48          .
                50  Track 800
                51

          10.  Insert the badblocks cartridge for the disc that was
               just formatted into the cartridge tape drive and set
               the drive locking handle in its upright position.

          11.  Read the badblocks information using the rbb command
               of discutil.  If the cartridge has more than one file
               on it, or the badblocks file is not named BADBLOCKS,
               you must give that file name as an argument to the rbb
               command.  For an example of this you can look at step
               10 in the next section.


                52  DU> rbb[]

          12.  Format the Volume Table of Contents (VTOC) using the
               mvtoc command.  SUS asks for the serial number of the
               disc drive, which can be found on the badblocks
               cartridge label or on the manufacturers label on the
               disc drive.  This establishes volume header
               information such as track-to-track skew, serial
               number, and defective space mapping.


                54  DEntertdisc drive serial number = 32279[]
                56   Confirm ? (y) y[]


         Formatting Other Discs

         You should repeat the last three steps for each disc in your
         configuration.  To change units on the primary controller
         use the discutil unit command.  To change controllers use
         the discutil device command.

         If you do not know the device addresses of the disc
         controllers on your system exit discutil and use the what
         command of SUS.




         Page  10              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




           2  DU> q[]
           4  This program reads the IO boards in the system.
           6   Device number: 00 - 0F is CIO BOARD
           8   Board Type: 41 IOData: 41FF0000
          10   BoardeType:e03 IOData:M120000FFISC
          12   Device number: 14 is SMD HARD DISC
          14   Board Type: 03 IOData: 1400FFFF
          16   BoardeType:e20 IOData:t20F00000APE
          17

         The example that follows shows formatting unit number 2 on
         the second controller.  The badblocks cartridge for this
         disc contains more than one badblocks image.

           1.  Put the SUS distribution cartridge into the drive and
               set the drive locking handle in its upright position.

           2.  Invoke the dir command of SUS.  This will load the dir
               command and display the contents of the SUS
               distribution cartridge.  This step is necessary to get
               the dir command loaded for the next step.


                19  SUS> dTape Directory
                21    no  file=name=====     size(byte)
                23     1  SUSYSTEM           264508
                25     3  DIRCUTIL           145009
                27     5  DISPUTIL            34049
                29     7  TAPEDIAG            46353
                31     9  MEMDIAGG            57265
                32    10  HEXDUMP              2385

           3.  Insert the badblocks cartridge for the disc that was
               just formatted into the cartridge tape drive and set
               the drive locking handle in its upright position.

           4.  Now invoke the dir command again.  This time note the
               name(s) of the files on the cartridge.


                34  SUS> dTape Directory
                36    no  file=name=====     size(byte)
                38     1  BB.29586             1950
                39     2  BB.32279              900

           5.  Put the SUS distribution cartridge into the drive and
               set the drive locking handle in its upright position.

           6.  Using the discutil command of SUS load the discutil
               program.  The discutil program takes about three


         004-5030              RX/V Release 1.1              Page  11








         ----------------   Installation Procedures  ----------------



               minutes to load from the SUS distribution cartridge.


                41  SUS> discutil[]
                43  Disc UtiVersions4.1 22-Jul-87or ROS
                44

           7.  While the SUS what command displays controller
               addresses in hexadecimal, discutil defaults to decimal
               input.  The hex command changes the input base of
               discutil to hexadecimal.  The dec command changes it
               back to decimal.

               By default the discutil program uses unit number 0 on
               the lowest numbered controller.  To format other discs
               use the hex and dec commands in conjunction with the
               dev and unit commands to select the proper disc.


                46  DU> dev[14[]
                48  DU> dec[]2[]


           8.  Format the disc using the format command of discutil.
               The actual formatting of the disc will take about two
               minutes for every 150 megabytes of capacity.

               If the disc does not contain valid disc skewing
               information discutil will ask for the values while
               suggesting default values.  It is advisable to use the
               standard skew values.  These values differ from one
               disc model to another.

               If the disc does contain valid skewing information
               discutil will ask you to review the values {51-53}.

                49  DU> format[]
                51  HeadattonHeadscSkew = 0
                53  Doayoutwantato usewthese standard values ? (y)
                54  Track 0
                56  Track 50.
                58          .
                60  Track 800
                61

           9.  Insert the badblocks cartridge for the disc that was
               just formatted into the cartridge tape drive and set
               the drive locking handle in its upright position.

          10.  Read the badblocks information using the rbb command
               of discutil.  If the cartridge has more than one file


         Page  12              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



               on it, or the badblocks file is not named BADBLOCKS,
               you must give that file name as an argument to the rbb
               command.


                62  DU> rbb bb.29586[]

          11.  Next format the Volume Table of Contents (VTOC) using
               the mvtoc command.  SUS asks for the serial number of
               the disc drive, which can be found on the badblocks
               cartridge label or on the manufacturers label on the
               disc drive.  This establishes volume header
               information such as track-to-track skew, serial
               number, and defective space mapping.


                64  DEntertdisc drive serial number = 29586[]
                66   Confirm ? (y) y[]


         If you have more discs to format return to the beginning of
         this section.  Otherwise, continue with the next section.

         Root File System Installation

           1.  Insert the RX/V Release 1.1 distribution cartridge
               into the drive and set the drive locking handle in its
               upright position.  The cartridge rewinds when put into
               the drive.

           2.  Reboot RBUG and use the c command to read the tape
               boot program.  RBUG may respond with an error number.
               This usually means that the cartridge tape drive is
               not yet reset.  Simply wait 10 to 15 seconds and try
               the command again.

                 1  CIO self test passed.
                 3  :c[] (08-May-87) PC=00042000
                 4

           3.  The tape boot program asks for disc controller number
               and unit number.  Simply depress the return key for
               both of these.  This will use the default: the first
               drive on the first controller.

               The root file system should always be on the first
               partition on the first drive on the first controller
               (e.g., c0d0s0).  If the root file system is not
               installed on c0d0s0, it will be necessary to boot the
               system using the h command of RBUG in order to specify
               the nonstandard location.


         004-5030              RX/V Release 1.1              Page  13








         ----------------   Installation Procedures  ----------------




                 6  disc controller number (0) : []0
                 7  unit number (0) : []0

           4.  The tape boot then asks if you want to copy boot.
               Respond with y for yes.  This will copy the disc boot
               program to the disc.


                 9  Boot copied (n) : y[]
                10

           5.  When the tape boot asks if you want to copy the root
               file system respond with y for yes.


                11  Copy file system (n) : y[]

           6.  When asked whether to copy the root or miniroot file
               from the cartridge respond with r for root.  There are
               two raw root file system images on the distribution
               cartridge.  The root image is a complete root file
               system.  The miniroot image is a small subset of the
               root file system used when performing updates to the
               system.


                12  Copy ROOT or MINIROOT [(r) or m] : r[]

           7.  The root file system is usually installed as partition
               number 0 on the lowest numbered controller.  If this
               is the case on your system simply depress the return
               key when asked for a partition.  If this is not the
               case on your system, enter the appropriate partition
               number and depress the return key.


                13  partition number (0) : []0

           8.  After reviewing that these values have been entered
               correctly respond with a y.  The notation used below
               is that of the special device file names for the disc
               partitions.  The digit following the c is the
               controller number in the range 0-3.  The digit
               following the d is the drive, or unit, number in the
               range 0-3.  The number following the s is the section,
               or partition, number in the range 0-15.


                15  OKp? (n)t:fy[] system to c0d0s0



         Page  14              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



           9.  At this point you get a display including a decimal
               number on the left and a line of dots and colons that
               represent tape blocks being read.  At the end of the
               line numbered 63 the root partition has been loaded
               and the system boots in single user mode.  This takes
               approximately four minutes.


                16  :::::::::::::::::::::::::::::::::::::::::::::::::
                18  Skipping Miniroot file system
                20  File system copied : 4096 blocks
                22  End of Tape Copy
                24  board address=0 type=65  CIO number=0
                26  board address=20 type=3  SMD number=1
                28  board address=254 type=32  MT number=0
                30  Cache: number of buffers 256
                31  ridge:45 RX/V release: 1.1 version: standard on
                33  14:48:45 real mem  = 8388608 avail mem = 5820416
                35  14:48:45 CIO 0 CODE Rev: D
                37  14:48:45 ethernetAinitialized
                39  INIT: SINGLE USER MODE
                40  #

               Note that the board addresses {24-27} and memory
               numbers {33} in the example above are a function of
               the hardware and software configuration of the system.
               The number of lines of output and the values you see
               will most likely be different than those shown in this
               example.

         Remaining Installations

         The reminder of the installation can either use the supplied
         installation scripts or be done by hand.  Unless there is
         some reason your system configuration must differ from the
         standard RX/V configuration it is suggested that you
         continue with this section and use the installation scripts.

         If you do not wish to use the standard configuration, skip
         forward to the section titled ``Detailed Installation
         Instructions.''

           1.  Make sure the the RX/V distribution cartridge is in
               the drive and that the drive locking handle is in its
               upright position.

           2.  Verify that the date is set correctly using the
               checkdate command.  Make sure you first set the
               environment variable TZ if you are not in the Pacific
               Time Zone.



         004-5030              RX/V Release 1.1              Page  15








         ----------------   Installation Procedures  ----------------



               Note that when entering the date or time leading zeros
               must be entered, e.g., January 1, 1988 is 01/01/88.


                 2  # export5TZ[]]
                 4  Is/the/datekFrieNov  6 13:32:39 EST 1987
                 5  Pleasetsetythe date[mm/dd/yy hh:mm (ex: 11/06/87
                 6  13:33)                   or  hh:mm (ex: 13:33)
                 7  Tue1Nov/10 09:23:00 EST 1987
                 8  correct?a(y oren)oy[]0 09:23:00 EST 1987


           3.  Begin the installation of RX/V by entering the
               install.rx command.  This script will lead you through
               the installation of the entire system.  If at any
               point install.rx fails or is terminated by the
               operator, the safest thing to do is to return to the
               beginning of the section titled ``Root File System
               Installation.''

                 9  # /etc/install.rx[]
                10

               The first part of the installation defines the Volume
               Table Of Contents, or VTOC, and then displays it.  The
               values for the VTOC {15-31} will vary with disc type.


                11  contents.lishing the default volume table of
                13  mkvtoc: warning system on /dev/dsk/c0d0s0
                14  place.:  New volume table of contents now in
                15  mappingid:      2       F2322   System disk
                17  * Dimensions:
                19  *    2049 sectors/track
                21  *     823 cylindersinder
                23  *     812 accessible cylinders
                24  Cylinderion 512Tbytes block size    First
                25  331200          2       00                 1
                26  331201          3       01                93
                27  745202          4       00               185
                28  142920          4       00               392
                29  292320          5       01                 0
                30  360  7          1       01                 0
                31  828015          4       00               789
                33


               The next step is to make the file system for /usr.
               Again the values for file system size {37, 38, 40, 45}
               will vary depending on disc type.



         Page  16              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




                35  Making the /usr file system.
                37  total logicaliblockso=k9315096
                39  total inodes = 9280
                41  10 secondssfor0DEL2if wrong !hysical blocks
                43  Labeling the /usr file system.
                45  Current fsname: , Current volname: , Blocks:
                46  FS5Units:o4Kb, Date last mounted: Tue Nov 10
                47  NEW2fsname9=7usr, NEW volname = 0 -- DEL if
                48  wrong!!


               The new file system is mounted on /usr and the
               lost+found directory is created and initialized.

                49  Mounting the /usr file system.
                51  mounting: <usr> as </usr>
                53  Making the lost+found directory for the /usr
                54  file system.
                56  removing dummy.files...
                58  drwxr-xr-x   2 root     sys         1056 Nov 10
                59  09:24 /usr/lost+found


               The distribution cartridge is now repositioned for the
               installation of the usr file system bundle.  This
               should take about five minutes.

                60  Rewinding the cartridge tape.
                62  Now positioning the tape to the first
                63  Thisawillitakeuadfew moments.


           4.  Now the first cpio archive of the root file system
               bundle is read and you are given the option of
               installing this bundle.  Since the root partition was
               copied onto the disc earlier, simply type RETURN when
               asked if you want to install the root file system.

               This will cause the root file system cpio archive to
               be skipped.  This should take about two minutes.

                64  10 blocks
                65  systemxcpiolarchive. tape is the root file
                66  mini rootifilehsystem.ly be installed from the
                68  Youwshould nottinstallnthisharchivedifeyourare
                69  your system.izing
                71  Do you want to install the root file system cpio
                    archive? (n)[]




         004-5030              RX/V Release 1.1              Page  17








         ----------------   Installation Procedures  ----------------



           5.  Now the first cpio archive of the usr file system
               bundle is read and you are given the option of
               installing this bundle.  Simply type RETURN when asked
               if you want to install the /usr files.


                73  Do youcwant to install the /usr files? (y)[]
                75  usr/adm/acct/niteal
                77          .
                79  usr/ucb.lib
                81  26600 blocks


           6.  Now the first cpio archive of the manual page bundle
               is read and you are given the option of installing
               this bundle.  Answer appropriately when asked if you
               want to install the online manual pages.

                82  10 blocks
                83  (y)[]u want to install the online manual pages?
                85  usr/catman/a_man/man1/accept.1m.z
                87          .
                89  usr/catman
                91  usr
                92  5290 blocks

         At this point all of the ``standard'' bundles have been
         installed or skipped.  There may be more installation dialog
         if you have purchased optional software.  Each bundle should
         ask if you want to install it or not.  If you choose not to
         install a particular bundle, it will be skipped by the
         installation scripts.


          94  Allboptions on this tape have been processed.
          95  #

         Defining Other Discs

         At this point the primary disc has several partitions set up
         for use.  The number of partitions depends on the particular
         disc drive type in your system.  You can use the
         /etc/prtvtoc(1m) command to see the numbers and types of
         these partitions.









         Page  18              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




           2  # /etc/prtvtoc /dev/rdsk/c0d0s7[]
           4                  VTOC    /dev/dsk/c0d0s7
           5  32279Drive :            F2322           serial number
           7  cylinders                823            sectors/track
           8  accessible cylinders     812            heads/cylinder
           9  maximum bad blocks       312            bytes/sector
          10  bad8blocks                18
          12  partition                p_flag           p_start
          13  p_blockn                                  cylinder
          14  512 bytes
          15  33120ot                  0             1
          16  33120ap                  1            93
          17  74520r                   0           185
          18  142920                   0           392
          19  04                       1             0
          20  05                       1             0
          21  292320ldisk              1             0
          22  360boot                  1             0
          23  08                       1             0
          24  09                       1             0
          25  00                       1             0
          26  01                       1             0
          27  02                       1             0
          28  03                       1             0
          29  04                       1             0
          30  8280sr                   0           789


         In the next section the remaining partitions on the primary
         disc will be set up.  This section adds other disc units to
         the configuration and initializes them.  Skip to the next
         section if you have only one disc.

         Before the following initialization can take place make sure
         you have formatted the disc and VTOC using SUS.  If you did
         not format the disc earlier, go back to the section titled
         ``Disc Formatting'' and follow the instructions there, boot
         the system single user (see the section titled ``Booting the
         System for Single User Operation'') and then return to this
         discussion.

         Discs are identified by a controller number and a device
         number.  RX/V does not use the device address as SUS does.
         The controllers are ordered by their device addresses and
         the first controller is 0, the second is 1, etc.  The drive
         number is selected on the drive with switches.

         For each additional disc type
              /etc/adddisc c d



         004-5030              RX/V Release 1.1              Page  19








         ----------------   Installation Procedures  ----------------



         where c is the controller number and d is the drive number.
         This will make the appropriate special files in /dev/dsk and
         /dev/rdsk as well as perform basic initialization of the
         VTOC.

         For example to initialize unit two on the second controller:


          32  mkvtoc:adNewsvolume]table of contents now in place.
          34  **Driveid:      3       F2333   System disk mapping
          36  * Dim2048obytes/sector
          38  *      10 heads/cylinder
          40  *     808 accessible cylinders
          42  * Partition    Tag     Flag         First Cylinder
          43  512 b0tes block 2ize    00                 1
          44  331201          3       01                47
          45  331202          4       00                93
          46  828003          4       00               208
          47  423366          5       01                 0
          48  581767          1       01                 0
          49  720 15          4       00               796
          50  8640


         Making Other File Systems

         A simple set of scripts to ease the initialization of the
         remaining disc partitions is provided with RX/V.  The script
         /etc/mkfsinit creates another script called fsinit which you
         can then edit and run.  /etc/mkfsinit takes, as arguments,
         pairs of numbers which specify the controller and device
         number respectively.

         Fsinit is a sequence of invocations of the script
         /etc/addfs.  This script performs all of the necessary
         functions for one partition.  It is called with the
         controller number, device number, partition number,
         partition size, file system name, and a directory pathname
         used for /etc/mount.

         The file system names generated are simply a catenation of
         the controller, unit and section/partition numbers prefixed
         with the character u (e.g., c1d2s3 is named u123).  The
         directory pathnames generated are these same strings with an
         additional / prefix (e.g., c1d2s3 is mounted at /u123).

         Editing of this script is only necessary if you do not want
         the default pathnames and file system names that mkfsinit
         provides.  If you want to change these names edit the
         appropriate arguments to the /etc/addfs commands in fsinit.
         (addfs takes a controller number, unit number, partition
         number, partition size, partition name, and directory name

         Page  20              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



         for mount.)

         The example below demonstrates how to use the defaults for
         all except the file system on c0d0s3.  For a single drive
         system the last two arguments to /etc/mkfsinit should be
         omitted.

           1.  Run /etc/mkfsinit to generate the fsinit script.


                 2  # /etc/mkfsinit 0 0 1 2[]
                 4  /etc/addfsi0i0[3 142920 u003 /u003
                 6  /etc/addfs 1 2 2582800 u1225/u12215
                 8  /etc/addfs 1 2 15486400u1215 /u1215


           2.  Rename u003 to u and have it mount at /u.

                 9  # ed ./fsinit[]
                11  1s/003//gp[]
                13  w[]c/addfs 0 0 3 142920 u /u
                15  q[]


           3.  Now run fsinit to establish the remaining file
               systems.

                16  # ./fsinit[]
                18  total logicaliblockso=k1786596
                20  total inodes = 17856
                22  10 secondssfor0DEL3if wrong0!physical blocks
                23  142920, Inodes: 17856rent volname: , Blocks:
                24  10:58:34:1987, Date last mounted: Tue Nov 10
                25  wrong!!ame = u, NEW volname = 0 -- DEL if
                27  mounting:n<u> ask</u>rectory /u
                29  removing dummy.files...
                31  drwxr-xr-x   2 root     sys         1056 Nov 10
                32  10:59 /u.lost+found
                34          .
                35  #

           4.  Unmount all of these file system.











         004-5030              RX/V Release 1.1              Page  21








         ----------------   Installation Procedures  ----------------




                37  /usrtc/mount[] on /dev/dsk/c0d0s2 read/write on
                38  /ud Jan  6 06:2on3/dev/dsk/c0d0s3 read/write on
                39  /u0015n  6 07:4on2/dev/dsk/c0d0s15 read/write on
                40  Wed Jan .6 07:42:52 1988
                42          .
                44  # /etc/umount /dev/c0d0s15[]
                46          .
                48  # /etc/mount[]
                49  WedrJan  6 06:28:35d1988sk/c0d0s2 read/write on


         Now all of the system software is installed and all of the
         disc partitioning is completed.  Skip forward to the section
         titled ``Administrative Files'' to complete the system
         setup.

         Detailed Installation Instructions

         If you have installed RX/V using the previous sections skip
         forward to the section titled ``Administrative Files.''  To
         proceed with the following instructions for installing your
         own configuration, you must have completed the steps above
         describing formatting the disc and installing the root file
         system.  You should have an INIT: SINGLE USER MODE message
         and a prompt on your console.

           1
           3  #NIT: SINGLE USER MODE


         This section does not contain the level of explanation that
         other sections may have simply because readers of this
         section are assumed to be familiar with the basic actions
         taking place here.

         In the example shown below the system tehama is configured
         such that the disc partitioning is rather simple:  the disc
         has root, swap, and usr partitions.  The standard disc
         configuration would have two user partitions: usr and u003.
         Here we will combine these into one larger usr file system.

           1.  Execute the following commands to enable traps and
               record the installation date in the installation
               logfile.

                 4  #trap 1 2 3[]
                 5  >>c/etc/.install.log[]%d@%T`\t`/bin/uname -rv`





         Page  22              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



           2.  Just to get all the standard numbers first make the
               VTOC with the standard values.


                 7  mkvtoc:mwarningdsystemkon0/dev/dsk/c0d0s0
                 8  place.:  New volume table of contents now in
                 9  mappingid:      3       F2333   System disk
                11  * Dimensions:
                13  *    2018 sectors/track
                15  *     823 cylindersinder
                17  *     808 accessible cylinders
                18  Cylinderion 512Tbytes block size    First
                19  331200          2       00                 1
                20  331201          3       01                47
                21  828002          4       00                93
                22  423360          4       00               208
                23  581760          5       01                 0
                24  720  7          1       01                 0
                25  864015          4       00               796
                26

           3.  Now adding the sizes of partitions 2 and 3 remake the
               VTOC with a partition 2 that includes all of the
               blocks that were in both partitions 2 and 3.

               Partitions must be an integral number of 4096 byte
               pages.  Make sure you choose a multiple of eight 512
               bytes blocks for the size of the partition.

























         004-5030              RX/V Release 1.1              Page  23








         ----------------   Installation Procedures  ----------------




                28  ?vtocvtoc[]
                30  0[2 00 1 33120[]
                32  2 4 00 93 506160[]
                34  7 1 01 0 720[]0[]
                36  .[]4 00 796 8640[]
                38  94]
                40  #[/etc/mkvtoc -s vtoc /dev/rdsk/c0d0s7[]
                42  mkvtoc: wNewivolumettable ofecontentsdnow in
                43  **Driveid:      3       F2333   System disk
                44  *apping
                46  * Dim2048obytes/sector
                48  *      10 heads/cylinder
                50  *     808 accessible cylinders
                52  * Partition    Tag     Flag         First
                53  Cylin0er    512 2ytes bl00k size           1
                54  331201          3       01                47
                55  331202          4       00                93
                56  506166          5       01                 0
                57  581767          1       01                 0
                58  720 15          4       00               796
                59  8640


           4.  Using the new size of partition 2, make the file
               system using mkfs.

                60  # /etc/mkfs /dev/rdsk/c0d0s2 506160[]
                62  total logicaliblockso=k6327096
                64  total inodes = 63232
                66  10 secondssfor0DEL2if wrong0!physical blocks


           5.  Label the file system using labelit.

                67  # /etc/labelit /dev/rdsk/c0d0s2 usr 0[]
                68  506160, Inodes: 63232rent volname: , Blocks:
                69  18:20:35:1988, Date last mounted: Mon Jan  4
                70  wrong!!ame = usr, NEW volname = 0 -- DEL if


           6.  Mount the new file system.

                71  #/etc/mount /dev/dsk/c0d0s2 /usr[]
                72  mounting: <> as </usr>

           7.  Change working directories to /usr and make the
               lost+found directory for the usr file system.





         Page  24              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




                74  #/etc/mklost+found[]
                76  removing dummy.files...
                78  drwxr-xr-x   2 root     sys         1056 Jan  4
                    18:25 /usr/lost+found

           8.  Reposition the distribution cartridge to the first
               bundle.


                80  #/bin/cmt rew[]
                81  #/bin/cmt fsf 5[]

           9.  And install the remaining bundles.


                83  10/blocksstall.option[]
                85  usr/adm/acct/fiscalall the /usr files? (y)[]
                87  usr/adm/.cct/nite
                89          .
                91  usr/ucb.lib
                93  106blockscks
                94  systemxcpiolarchive. tape is the root file
                95  mini rootifilehsystem.ly be installed from the
                97  Youwshould nottinstallnthisharchivedifeyourare
                98  your system.izing
                100 Do you want to install the root file system cpio
                101 10cblocks(n)[]
                102 (y)[]u want to install the online manual pages?
                104 usr/catman/a_man/man1/accept.1m.z
                106         .
                108 usr/catman
                110 usr
                112 109blocksks
                113 All options on this tape have been processed.

          10.  Make and initialize the remaining file systems.
















         004-5030              RX/V Release 1.1              Page  25








         ----------------   Installation Procedures  ----------------




                115 bytescperflogicalrblock0=040968640[]
                117 total inodesl=b1024s = 1080
                119 On /dev/rdsk/c0d0s15 : 8640 physical blocks
                121 #0/etc/labelit /dev/rdsk/c0d0s15 minrot 0[]
                122 8640,nInodes:e1024Current volname: , Blocks:
                123 19:31:50:1988, Date last mounted: Mon Jan  4
                124 wrong!!ame = minrot, NEW volname = 0 -- DEL if
                126 mounting:u<minrot>das/</mnt>5 /mnt[]
                128 # /etc/mklost+found[]
                130 removing dummy.files...
                132 drwxr-xr-x   2 root     sys         1056 Jan  4
                133 #9cd4/[]nt/lost+found
                135 # /etc/mount[]/dev/dsk/c0d0s15[]
                136 MonrJan  4 18:24:54d1988sk/c0d0s2 read/write on


         Now all of the system software is installed and all of the
         disc partitioning is completed.

         Administrative Files

         This section lists some of the administrative files that are
         likely to need modification.  In addition to these files
         there is a directory named /etc/templates.  The files in
         this directory are provided as templates for the major
         system administrative data files and are shipped this way to
         avoid overwriting to the actual files.

         In RX/V Release 1.0 the template files were in /etc directly
         but were named with a .1.0 suffix.

         /etc/TIMEZONE contains the commands to set the time zone
                     information for your system.  If this file were
                     not present the time zone for your system would
                     be determined by the values in the kernel which,
                     by default, are set for Pacific Time.

                     To change the time zone for your system edit
                     this file to contain the proper value (e.g.,
                     EST5EDT for the east coast).

         /etc/checklist contains a list of the device special files
                     containing file systems other than the root file
                     system which should optionally be checked by
                     fsck when the system is booted multi-user.

                     The default installation scripts modify this
                     file for you.  If you have followed the detailed
                     installation instructions you will need to add
                     the appropriate partition names to this file.


         Page  26              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



         /etc/fscknight contains the fsck commands to check all file
                     systems, including those which are currently
                     mounted.  The default crontab for root executes
                     this on week nights.

                     The default installation scripts modify this
                     file for you.  If you have followed the detailed
                     installation instructions you will need to add
                     the appropriate partition names to this file.

         /etc/group  defines the groups on your system.

                     Modify this file to define the groups you want.

         /etc/hosts  defines the hosts on your network.

                     If you are not connected to the network, you can
                     leave this file alone.  Otherwise, modify this
                     file to list other hosts.  See the examples
                     below for more information.

         /etc/hosts.equiv lists all of the systems that are assumed
                     to have identical user id to user name mappings
                     on your network.

                     If no such systems exist you can remove this
                     file.  Otherwise, modify this file to list those
                     other systems.  Again, see the examples below
                     for more information.

         /etc/inittabspecifies actions to be taken by init(1m) when
                     changes in run level occur.

                     You should modify this file to activate
                     getty(1m) on any tty ports that you plan to use
                     as login devices.

         /etc/mountlist is a script that is run to mount file systems
                     when the system enters run levels 0, 1 or 2.

                     Modify this file to mount the file systems,
                     other than root, that you want mounted when the
                     system is booted multi-user.

         /etc/networks lists the networks that are accessible from
                     this system for internetworking.

                     This file should not require any editing.

         /etc/passwd lists all of the user id to user name mappings
                     for the system as well as password, default


         004-5030              RX/V Release 1.1              Page  27








         ----------------   Installation Procedures  ----------------



                     group and default shell for each user.

                     You should modify this file (or copy one from
                     another system) to define all of the users that
                     will use this system.

         /etc/rc     is run whenever the system changes run levels.

                     You should modify this file to set the node name
                     for your system in the uname -N command line.
                     See the examples below for more information.

         /etc/rc.local is executed whenever the system is booted
                     multi-user.

                     This is intended as the place for site specific
                     customization.

         /usr/lib/aliases defines the mail aliases for your system.

                     See aliases(4) for the format and function of
                     this file.

         /usr/lib/sendmail.cf is a configuration file for sendmail.
                     If it does not exist, the sendmail daemon
                     (started in rc.inet) will not be started.

                     It must be customized for your site.  There are
                     several template files provided.  They are
                     located in /usr/lib and contain the .cf suffix.

         What follows is a sample console session showing examples of
         the customization of these administrative files.

           1.  Edit the TIMEZONE file to define the proper time zone
               for your system.


                 2  # ed TIMEZONE[]
                 4  1,$p[]
                 6  #ident  Set8timezone environmentEtoNdefault1for
                 7  TZ=PST8PDTe
                 9  3s/P/E/g[]
                11  TZ=EST5EDT
                13  112
                14  q[]

           2.  Remove any device special file names that are not to
               be used for file systems or are not to be checked when
               the system comes up for multiuser operation from the
               checklist file.  In this example neither of the


         Page  28              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



               miniroot file systems is to be checked.


                16  99ed checklist[]
                18  /dev/rdsk/c0d0s2
                20  /dev/dsk/c0d0s15
                22  /dev/dsk/c1d2s3
                24  $d[]/dsk/c1d2s15
                26  1,$p[]
                28  /dev/dsk/c0d0s32
                30  /dev/dsk/c1d2s3
                32  65]
                33  q[]

           3.  Likewise remove the fsck commands for those file
               systems from the fscknight script.


                35  232d fscknight[]
                37  #,``[@(#)fscknight       6.1     87/11/23 ''
                39  /etc/fsck -n /dev/dsk/c0d0s2
                41  /etc/fsck -n /dev/dsk/c0d0s15
                43  /etc/fsck -n /dev/dsk/c1d2s3
                45  /s15[]sck -n /dev/dsk/c1d2s15
                47  d[]c/fsck -n /dev/dsk/c0d0s15
                49  /etc/fsck -n /dev/dsk/c1d2s15
                51  /[]
                53  w[]
                55  q[]


           4.  As with checklist and fscknight we will remove the
               miniroot file systems from the mountlist script.

                56  # ed mountlist[]
                58  1,$p[]
                59  refusedumountev/dsk/c0d0s2 /usr || echo usr
                60  mountmount /dev/dsk/c0d0s3 /u || echo u refused
                61  refusedumountev/dsk/c0d0s15 /u0015 || echo u0015
                62  refusedumountev/dsk/c1d2s2 /u122 || echo u122
                63  refusedumountev/dsk/c1d2s3 /u123 || echo u123
                64  refusedumountev/dsk/c1d2s15 /u1215 || echo u1215
                66  /etc/mount /dev/dsk/c0d0s15 /u0015 || echo u0015
                67  d[]used mount
                69  /etc/mount /dev/dsk/c1d2s15 /u1215 || echo u1215
                70  d[]used mount
                72  ?[]
                74  240
                75  q[]




         004-5030              RX/V Release 1.1              Page  29








         ----------------   Installation Procedures  ----------------



           5.  Define the group name to GID mappings to be used by
               editing the /etc/group file.  In this example we
               replace the group public with two new groups:  sw and
               hw as groups 100 and 101 respectively.


                77  229d group[]
                79  root::0:root
                81  bin::2:root,bin,daemon
                83  adm::4:root,adm,daemon,mhm
                85  mail::6:root,daemon
                87  news::10:news,daemon
                89  manager::20:managermon
                91  c[]lic::100:guest
                93  hw::101[]
                95  $-2,$p[]
                97  sw::100::20:manager
                99  w[]:101
                101 q[]


           6.  The passwd file should be edited to add any initial
               users desired.  In this example we add fred, barney,
               and wilma.  Fred is in the group sw.  Barney and wilma
               are in the group hw.  In addition, barney's login
               shell is set to be csh.

                102 # ed passwd[]
                104 1,$p[]
                106 daemon:**NO0LOGIN**:1:12:0000-Admin(0000):/:
                108 sys:**NO LOGIN**:3:3:0000-Admin(0000):/usr:
                110 uucp::5:5:0000-Admin(0000):/usr/lib/uucp:r/adm:
                111 Admin(0000):/usr/spool/uucppublic:/usr/lib/uucp/uucico
                113 date::18:1::/:/bin/date0000):/usr/lib/news:
                115 shut::21:1:0000-Admin(0000):/:/etc/shutdown
                117 shqer::69:8:0000-rje(0000):/usr/rje:
                119 lp:**NOOLOGIN**:71:2:0000--ftp(0000):/tmp:
                120 a[]0000):/usr/spool/lp:
                122 barney::101:101:BarneynA.hire:/u/fred:[]
                123 wilma::102:101:WilmanA.sFlintshire:/u/wilma:[]
                125 w[]
                127 q[]


           7.  Next the hosts file is edited to at least define this
               and one other host on the network.  Once this is done
               and the system is brought up for multiuser operation
               and a hosts file can be copied from the other system.

               If your system is not connected to a network you can
               ignore this step.


         Page  30              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




                129 615d hosts[]
                131 #,@(#)hosts     6.1  11/24/87
                133 # DO NOT REMOVE NEXT LINE or everything will
                134 #rIPkHOST Addresses
                136 # local hosts database
                138 # ADDR  SYS NAME        SYS No   SYS ADM.
                140 127.1-  local---        localhost-#-name-of the
                141 system administrator.
                142 machine.lowing line is a sample entry for this
                144 #126.1  ridge           ridge1  #your-name-here
                145 scripts.rmat is required by the DTC installation
                146 DistributediTerminaliController.entry for a
                147 SERVER  NAME            ENET ADDR       BOOT
                148 ---------------         ------------
                149 ridge75 dtc1            08000200AAAA    boot:
                151 #126.1[]ridge           ridge1  #your-name-here
                153 126.7   ridge[]
                155 .[].45  tehama[]
                157 #126.1[]ridge           ridge1  #your-name-here
                159 #126.1] ridge           ridge1  #your-name-here
                161 126.45  tehama
                163 #This format is required by the DTC installation
                164 #Thepfollowing line is a sample entry for a
                165 w[]tributed Terminal Controller.
                167 q[]


           8.  Likewise the hosts.equiv file is updated to list this
               system and the one from which a real hosts.equiv file
               will be copied.

               If your system is not connected to a network you can
               ignore this step.

               You may not want a hosts.equiv file on your system.
               See hosts.equiv(4) for more details.
















         004-5030              RX/V Release 1.1              Page  31








         ----------------   Installation Procedures  ----------------




                169 226d hosts.equiv[]
                171 #,@(#)hosts.equiv       6.1  11/24/87
                173 # hosts.equiv  is a list of hosts considered
                174 #`loginanames'andeusergID's are the same for
                175 #isted machines.
                177 # host name
                179 myfriendlyhost
                181 $-1,$c[]ndlyhost
                183 tehama[]
                185 $-3,$p[]
                187 # ---------
                189 tehama
                191 207
                192 q[]

           9.  Edit the inittab as necessary to define login sessions
               on direct connect lines (tty01-tty63).

               The inittab entry for the console should always
               specify the baud rate as follows:

                                                                         o For
                                                                           Ridge
                                                                           32
                                                                           systems
                                                                           the
                                                                           baud
                                                                           rate
                                                                           should
                                                                           always
                                                                           be
                                                                           9600.

                                                                         o For
                                                                           Ridge
                                                                           3200
                                                                           systems
                                                                           the
                                                                           baud
                                                                           rate
                                                                           should
                                                                           be
                                                                           set
                                                                           to
                                                                           agree
                                                                           with
                                                                           the
                                                                           rate
                                                                           set
                                                                           on


         Page  32              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



                                                                           the
                                                                           switches
                                                                           on
                                                                           the
                                                                           clock
                                                                           board.
                                                                           See
                                                                           your
                                                                           Ridge
                                                                           Service
                                                                           Representative
                                                                           for
                                                                           more
                                                                           details.

               In this example the inittab is edited to enable login
               on tty01 and tty04.


                194 868d inittab[]
                196 id:2:initdefault:
                197 cf::bootwait:/etc/machconf/1>/dev/systty 2>&1
                198 bl::bootwait:/etc/bcheckrc </dev/systty
                199 bc::bootwait:/etc/brc 1>/dev/systtyc2>&1
                200 rc::wait:/etc/rcd1>/dev/systty 2>&1
                201 ri::wait:/etc/rc.inet 1>/dev/systty 2>&1
                202 rl::wait:/etc/rc.locale1>/dev/systty 2>&1
                203 lp::off:/etc/initlp 1>/dev/systty 2>&1
                204 sl::wait:/etc/initcons 1>/dev/syscon 2>&1
                205 pf::powerfail:/etc/powerfail 1>/dev/syscon 2>&1
                206 co::respawn:/etc/getty -Tunknown console 9600
                207 t1::off:/etc/getty -Tvt100 /dev/tty01 9600
                208 t2::off:/etc/getty1-Tvt100 /dev/tty02 9600
                209 t3::off:/etc/getty2-Tunknown /dev/tty03
                210 a[]em2400       # modem
                211 #4Fred'saoffice[]getty -Ttvi950 /dev/tty04 9600
                213 /t1[]
                214 #1locationtofgtty01-Tvt100 /dev/tty01 9600
                216 t1::respawn:/etc/getty -Tvt100 /dev/tty01 9600
                217 w[]ocation of tty01
                219 q[]


          10.  The rc file should be edited to define the node name
               of this system.  Simply replace the string undef in
               the uname -N command line as shown below.







         004-5030              RX/V Release 1.1              Page  33








         ----------------   Installation Procedures  ----------------




                221 977d rc[]
                223 /undef[]        uname -N undef
                225 s//tehama/p[]   uname -N tehama
                227 978
                228 q[]

          11.  The rc.local file is intended to contain local site
               specific commands to be executed when run levels are
               changed.  Edit this file as needed.  In the example
               below we make no modifications.


                230 # ``t@(#)rc.local        6.1     87/11/23 ''


          12.  There are several template sendmail configuration
               files.  Choose the one best suited to your system and
               customize it writing the resulting file in
               /usr/lib/sendmail.cf.

                231 # cd /usr/lib[]
                233 9012 leafnode.cf[]
                235 Cwquartz
                237 Cwtehama/tehama/p[]
                239 DRridge
                241 DRridge/ridge/p[]
                243 CStrinity
                245 -1[]S/d[]
                246 --konly $RTneedhbencomplete (this domain only)
                248 CSridge[]
                250 .[]ehama[]
                252 8833ndmail.cf[]
                254 #[]


         Multiuser Operation

         Once the above steps have been completed you should sync the
         disc(s), reboot the system and allow multiuser operation.

           1.  First sync the disc(s).

                 1  # sync;sync[]


           2.  Reboot RBUG and use the h command to boot the image
               now on disc.





         Page  34              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




                 3  RBUGs(02-Apr-87)sPC=00042000
                 5  :h[]
                 7  board address=0 type=65  CIO number=0
                 9  board address=18 type=3  SMD number=0
                11  Cache: number of buffers 256
                12  ridge:51 RX/V release: 1.1 version: standard on
                14  08:04:51 real mem  = 8388608 avail mem = 5820416
                16  08:04:51 CIO 0 CODE Rev: D
                18  08:04:51 ethernetAinitialized
                20  INIT: SINGLE USER MODE


           3.  Using telinit request run level 2.

                21  # telinit 2[]
                23  INIT: New run level: 2
                24  Swap space established on /dev/dsk/c0d0s1.

           4.  Check that the date and time printed are correct and
               respond accordingly.  If your system is a 3200 this
               question will not appear.


                25  correct?a(y ordn)ay[]6 08:05:02 PST 1988


           5.  When asked if you want to check /dev/syst respond
               positively.

                26  Do you want to check system file /dev/syst ?(y
                27  or n) y[]
                29    File/System: root Volume: 0
                31    ** Phase 1 - Check Blocks and Sizes
                33    ** Phase 3 - Check Connectivity
                35    ** Phase 5 - Check FreerList Counts
                36    490 files 15552 blocks 16688 free

           6.  When asked if you want to check other file systems it
               is recommended that you respond positively.













         004-5030              RX/V Release 1.1              Page  35








         ----------------   Installation Procedures  ----------------




                37  checklistn? (y oren) y[]e systems from the
                39    /dev/rdsk/c0d0s2
                41    File System: usr Volume: 0
                43    ** Phase 2 - Check Pathnamesd Sizes
                45    ** Phase 4 - Check ReferenceiCounts
                47    1999hfiles 38208cblocks 460032 free
                49          .
                51          .
                52  Corporation. developed in cooperation with Bull
                54  mounting: <usr> as </usr>
                56  cronistarteding ram...
                58  localidaemons:rftpdnrshd rlogind telnetd rwhod.
                60  starting bridge servers: name file boot.
                62  Welcome to native UNIX(tm) on the Ridge
                63  login:

           7.  If your system is a Ridge 32, you should carefully
               flip the load enable switch back to the left at this
               point.

































         Page  36              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



         Installing an RX/V Update

         Before installing any RX/V update your system should be
         completely backed up.  While, the instructions provided have
         been tested on several configurations, not all possible
         configurations have been tested.

         The instructions that follow use something called a
         miniroot.  This is simply a very small subset of the
         software in the root file system which can be installed in
         partition 15 on discs that use a standard configuration or
         in a swap partition of at least 4 megabytes.  You should
         determine the identity of the partition you will use before
         proceeding.

         Updating an RX/V Release 1.0 system to RX/V Release 1.1 may
         require changes to the partition sizes on your system.  The
         table below lists the increases in disc space utilization
         for the standard RX/V configuration.

                      __________________________________
                      |nameition | disc blocks | inodes |
                      |root______|____2032_____|___35___|
                      |usr_______|____2608_____|__212___|
         TABLE 2.  Decreases_in_Disc_Utilization_from_RX/V Release
                   1.0 to RX/V Release 1.1

         If you do not have enough free space to accommodate these
         increases you should completely back your system up and
         install RX/V Release 1.1 from scratch.

         If you have enough space continue with the remainder of this
         section.

         Due to many changes in the device drivers the minor device
         numbers have changed extensively.  This update procedure
         will completely replace many of the files in /dev.  You
         should check the ownership of all tty special device files
         so that you can restore proper ownership after installing
         this update.

           1.  Make sure the the RX/V distribution cartridge is in
               the drive and that the drive locking handle is in its
               upright position.

           2.  Boot RBUG and use the c command to load the tape boot
               program.






         004-5030              RX/V Release 1.1              Page  37








         ----------------   Installation Procedures  ----------------




                 2  RBUGs(08-May-87)sPC=00042000
                 4  :c[]


           3.  The tape boot program asks for disc controller number
               and unit number.  Simply depress the return key for
               both of these.  This will use the default: the first
               drive on the first controller.

                 5  Tape Copy :
                 7  unit numberl(0) :u[]0r (0) : []0


           4.  The tape boot then asks if you want to copy boot.
               Respond positively.  This will copy the disc boot
               program to the disc.

                 8  Copy Boot ? (n) : y[]
                10  Boot copied


           5.  When the tape boot asks if you want to copy the root
               file system respond positively

                11  Copy file system (n) : y[]


           6.  When asked whether to copy the root or miniroot file
               from the cartridge respond with m for miniroot.

               There are two root file system images on the
               distribution cartridge.  The root image is a complete
               root file system.  The miniroot image is a small
               subset of the root file system used when performing
               updates to the system.

               The root image will be skipped.  This takes
               approximately four minutes.

                12  Copy ROOT or MINIROOT [(r) or m] : m[]
                14  Skipping root file system


           7.  Enter the appropriate partition number (15 if you have
               a miniroot partition, otherwise some other partition
               large enough to hold the miniroot) and press return.

                15  partition number (15) : 15[]




         Page  38              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



           8.  After reviewing that these values have been entered
               correctly respond positively.  The notation used below
               is that of the special device file names for the disc
               partitions.  The digit following the c is the
               controller number in the range 0-3.  The digit
               following the d is the drive, or unit, number in the
               range 0-3.  The number following the s is the section,
               or partition, number in the range 0-15.


                17  OKp? (n)i:oy[]file system to c0d0s15


           9.  At this point you get a display including a decimal
               number on the left and a line of dots and colons that
               represent tape blocks being read.  After the miniroot
               image has been loaded into the specified partition,
               the system will come up in single user mode.  This all
               takes approximately one minute.

                18  15
                    :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
                20  File system copied : 1024 blocks
                22  End of Tape Copy
                24  board address=0 type=65  CIO number=0
                26  board address=18 type=3  SMD number=0
                28  Cache: number of buffers 256
                29  standard on/ridgeease: 1.1 standard version:
                31  13:20:41 real mem  = 8388608 avail mem = 5820416
                33  13:20:41 CIO 0 CODE Rev: D
                35  13:20:41 ethernetAinitialized
                37  INIT: SINGLE USER MODE


               Note that the board addresses {24-25} and memory
               numbers {31} in the example above are a function of
               the hardware and software configuration of the system.
               The number of lines of output and the values you see
               will most likely be different than those shown in this
               example.

          10.  Verify that the date is set correctly using the date
               command.  If it is not correct, set it with the date
               command.  The syntax for setting the date is not
               obvious.  The argument is the month, day, hour,
               minute, and finally year.

                38  # date 0114221588[]
                39  Thu Jan 14 22:15:01 EST 1988




         004-5030              RX/V Release 1.1              Page  39








         ----------------   Installation Procedures  ----------------



          11.  Mount your root file system as /mnt.


                41  mounting:d<root>/asd</mnt>nt[]


          12.  Using the install.rx script install the root file
               system bundle provided on the distribution cartridge.
               Don't forget the -o flag to install.rx.  The
               distribution cartridge is first repositioned by the
               script.  This takes approximately four minutes.

                42  # /etc/install.rx -o[]
                44  Rewinding the cartridge tape.
                46  Now positioning the tape to the first
                47  Thisawillitakeuadfew moments.


               The first cpio archive of the root file system bundle
               is read and you are given the option of installing
               this bundle.  Type y when asked if you want to install
               the root file system cpio archive.

                48  10 blocks
                49  systemxcpiolarchive. tape is the root file
                50  mini rootifilehsystem.ly be installed from the
                52  Youwshould nottinstallnthisharchivedifeyourare
                53  your system.izing
                55  Do you want to install the root file system cpio
                56  bin/as9? (n)y[]
                58  bin/as  .
                60          .
                62  .nix
                64  14900 blocks


               There will be some lines printed in the above output
               {56-58} that are of the form:  Cannot mknod
               <dev/dsk/c0d0s0> (errno:17) or current <etc/rc> newer.
               These are normal.  The first form is due to the fact
               that your system already has special files defined and
               the distribution contains these files.  The second
               form is simply telling you that the /etc/rc file from
               the distribution is not being loaded because you have
               changed the file /etc/rc since the last installation.

          13.  The update of the root partition is now completed.
               Since the installation script syncs the disc you do
               not need to do so.




         Page  40              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------




                65  rebootoyourlcomputer has been updated.  Please
                66  SoftwareiReleasehNotes.pdate procedure in the
                67  #

          14.  Now reboot RBUG and use the h command to load the new
               kernel that was installed as part of the preceding
               steps.


                69  RBUGs(08-May-87)sPC=00042000
                71  :h[]
                73  board address=0 type=65  CIO number=0
                75  board address=18 type=3  SMD number=0
                77  Cache: number of buffers 256
                78  standard on/ridgeease: 1.1 standard version:
                80  09:30:32 real mem  = 6291456 avail mem = 3735552
                82  09:30:32 CIO 0 CODE Rev: D
                84  09:30:32 ethernetAinitialized
                86  INIT: SINGLE USER MODE


          15.  Mount the usr file system and any others in which you
               may have system software or files installed.

                87  # mount /dev/dsk/c0d0s2 /usr[]
                88  mounting: <usr> as </usr>

          16.  Using the install.rx script install the remaining
               bundles provided on the distribution cartridge.  Don't
               forget the -o flag to install.rx.  The distribution
               cartridge is first repositioned by the script.  This
               takes approximately four minutes.


                90  # install.rx -o[]
                92  Rewinding the cartridge tape.
                93  installationibundle.tape to the first
                94  This will take a few moments.

          17.  Do not install the root partition again.  Answer the
               question below with an n or simply press return.


                96  Thebnextsfile on the tape is the root file
                97  Thisearchiveashould.only be installed from the
                98  Itnwillobefinstalledminto the /mnt directory.
                99  justsinitializingstall this archive if you are
                101 your system.
                102 archive?a(n)[] install the root file system cpio



         004-5030              RX/V Release 1.1              Page  41








         ----------------   Installation Procedures  ----------------



          18.  The first cpio archive of the usr file system bundle
               is read and you are given the option of installing
               this bundle.  Type y when asked if you want to install
               the /usr files.


                104 Do youcwant to install the /usr files? (y)[]
                106 usr/adm/acct/niteal
                108         .
                110 usr/ucb.lib
                112 26600 blocks


          19.  The first cpio archive of the online manual page
               bundle is read and you are given the option of
               installing this bundle.  Answer the question
               appropriately.

                113 10 blocks
                114 (y)[]u want to install the online manual pages?
                116 usr/catman/a_man/man1/accept.1m.z
                118         .
                120 usr/catman
                122 .sr
                123 5290 blocks

               At this point all of the ``standard'' bundles have
               been installed or skipped.  There may be more
               installation dialog if you have purchased optional
               software.  Each bundle should ask if you want to
               install it or not.  If you choose not to install a
               particular bundle, it will be skipped by the
               installation scripts.


                125 Allboptions on this tape have been processed.


          20.  Dismount the file systems mounted in step 14.

                126 # umount /dev/dsk/c0d0s2[]


         At this point your system has been updated.  Proceed to the
         next section and customize the administrative files for your
         system.







         Page  42              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



         Administrative Files

         This section lists some of the administrative files that are
         likely to need modification.  In the update a directory of
         template files was updated.  These files are in
         /etc/templates.  The files in this directory are provided as
         templates for the major system administrative data files and
         are shipped this way to avoid overwriting the actual files.

         /etc/TIMEZONE contains the commands to set the time zone
                     information for your system.  If this file were
                     not present the time zone for your system would
                     be determined by the values in the kernel which,
                     by default, are set for Pacific Time.

                     To change the time zone for your system edit
                     this file to contain the proper value (e.g.,
                     EST5EDT for the east coast).

         /etc/checklist contains a list of the partitions, other than
                     the root partition, which should optionally be
                     checked by fsck when the system is booted
                     multi-user.

                     The default installation scripts modify this
                     file for you.  If you have followed the Detailed
                     Installation Instructions you will need to add
                     the appropriate partition names to this file.

         /etc/fscknight contains the fsck commands to check all
                     partitions, including those which are currently
                     mounted.  The default crontab for root executes
                     this on week nights.

                     The default installation scripts modify this
                     file for you.  If you have followed the Detailed
                     Installation Instructions you will need to add
                     the appropriate partition names to this file.

         /etc/group  defines the groups on your system.

                     Modify this file to define the groups you want
                     defined.

         /etc/hosts  defines the hosts on your network.

                     If you are not connected to the network, you can
                     leave this file alone.  Otherwise, modify this
                     file to list other hosts.  See the examples
                     below for more information.



         004-5030              RX/V Release 1.1              Page  43








         ----------------   Installation Procedures  ----------------



         /etc/hosts.equiv lists all of the systems that are assumed
                     to have identical user id to user name mappings
                     on your network.

                     If no such systems exist you can remove this
                     file.  Otherwise, modify this file to list those
                     other systems.  Again, see the examples below
                     for more information.

         /etc/inittabspecifies actions to be taken by init(1m) when
                     changes in run level occur.

                     You should modify this file to activate
                     getty(1m) on any tty ports that you plan to use
                     as login devices.

         /etc/mountlist is a script that is run to mount file systems
                     when the system enters run levels 0, 1 or 2.

                     Modify this file to mount the file systems,
                     other than root, that you want mounted when the
                     system is booted multi-user.

         /etc/networks lists all of the networks that are accessible
                     from this system for internetworking.

                     This file should not require any editing.

         /etc/passwd lists all of the user id to user name mappings
                     for the system as well as password, default
                     group and default shell for each user.

                     You should modify this file (or copy one from
                     another system) to define all of the users that
                     will use this system.

         /etc/rc     is run whenever the system changes run levels.

                     You should modify this file to set the node name
                     for your system in the uname -N command line.
                     See the examples below for more information.

         /etc/rc.local is executed whenever the system is booted
                     multi-user.

                     This is intended as the place for site specific
                     customization.

         /usr/lib/sendmail.cf is a configuration file for sendmail.

                     It must be customized for your site.  There are


         Page  44              RX/V Release 1.1              004-5030








         ----------------   Installation Procedures  ----------------



                     several template files located in /usr/lib/*.cf.

         New administrative files are distributed in the
         /etc/templates directory.  You can look at these files and
         see what has changed that you are interested in using.  In
         the following examples the /etc/rc and /etc/rc.local are
         checked.


           2  2c2iff rc templates/rc[]
           4  --- `` @(#)rc    3.6     87/05/18 ''
           6  18c18` @(#)rc    6.1     87/11/23 ''
           8  ---             uname -N tehama
          10  30a31           uname -N undef
          12  33,34c34,35     /etc/tools/readlr -z
          14  < #             /bin/rm -f /usr/spool/uucp/STST**
          16  >--             /bin/rm -f /usr/spool/locks/LCK*
          18  # ed templates/rc[]n/rm -f /usr/spool/uucp/.Status/*
          20  /undef[]
          22  s/undef/tehama/p[]ame -N undef
          24  w rc[]          uname -N tehama
          26  q[]
          28  1c1iff rc.local templates/rc.local[]
          30  --- `` @(#)rc.local      4.1     87/03/13 ''
          32  # # `` @(#)rc.local      6.1     87/11/23 ''


         Installing P&A Cartridges

         Options such as F77 that are purchased after the initial
         purchase of your system are shipped as P&A tapes.  To
         install all of the options on such a tape:

           1.  Boot the system for single user operation.  See the
               section titled ``Booting the System for Single User
               Operation'' for more information.

           2.  Make sure the the distribution cartridge is in the
               drive and that the drive locking handle is in its
               upright position.

           3.  Invoke the install.option script.

                 1  # install.option[]
                 2  10 blocks

           4.  When asked if you want to install an option respond
               appropriately and the bundle for that option will
               either be installed or skipped.




         004-5030              RX/V Release 1.1              Page  45








         ----------------   Installation Procedures  ----------------



               When all bundles on the tape have been processed the
               install.option script terminates.


                 3  versionw3.1?t(y)[]tall the RX/V F-77 compiler,
                 5  bin/f77
                 7          .
                 9  usr/lib .
                11  2480lblocksp
                13  #0 blocks


           5.  Reboot the system for multi user operation.  See the
               section titled ``Booting the System for Multi User
               Operation'' for more information.






































         Page  46              RX/V Release 1.1              004-5030








         --    Distributed Terminal Controller (DTC) Installation  --



         Distributed Terminal Controller (DTC) Installation

         The DTC is a terminal concentrator that provides 10
         asynchronous ports connected to the Ridge system.  The DTC
         is very flexible in that it connects to the same LAN as your
         Ridge, thus allowing terminals to be placed in any location
         serviced by your LAN.

         The DTC needs to be downloaded from some Ridge system on the
         LAN.  This section describes the process by which a
         particular system becomes the boot server for a particular
         DTC.  Following these instructions results in a DTC that
         provides up to 10 new login or serial printer connections to
         this system.

           1.  Make sure the system is running multi user and log
               into the system as root.


                 2  Welcome to native UNIX(tm) on the Ridge
                 4  RX/Vn: rNative UNIX(tm) on Ridge 32/3200


           2.  Edit /etc/hosts to add the internet address and name
               that you have chosen for the DTC.  Here at Ridge we
               also add the ethernet address and boot server name.
               The ethernet address is a 12 digit hexadecimal number
               that can be found on the manufacturers serial number
               label on the back of the unit.  It should be labeled
               E/A.

                 5  # ed /etc/hosts[]
                 7  $-5,$p[]
                 9  #This format is required by the DTC installation
                10  #Thepfollowing line is a sample entry for a
                11  #iADDRbuNAMETerminal ConENETlADDR       BOOT
                12  #-----  -------         ------------
                13  #126.75-dtc1            08000200AAAA    boot:
                14  a[]ge
                15  tehama[]dtc0            08000200E5ED    boot:
                17  w[]
                19  q[]


           3.  Change directories to /etc/bridge and run the
               stdbridge script.

               The stdbridge script takes the ethernet address of the
               DTC as its first argument.  The second argument to
               stdbridge is the name assigned to the DTC in the
               previous step.


         004-5030              RX/V Release 1.1              Page  47








         --    Distributed Terminal Controller (DTC) Installation  --




                21  # ./stdbridged08000200E5ED dtc0[]
                22  thateit the Bridge box to the network.  Verify
                23  exitsebootrstateits self test, boot state, and
                25  Hit return when this is complete


           4.  When the Self Test and Boot State lights goes out on
               the DTC it has booted.  At this point you should
               depress the return key.  The stdbridge script will
               then provide default configuration parameters for all
               ports on the DTC.

                26  []
                27  Bridge^J'' welcomestring=``^MWelcome to the dtc0
                29  setdefau.t prompt=``dtc0> ''
                31          .
                32  savedeaseconfiguration!`9'efault parameters
                33  primaryrandtsecondarygname2server.1 is both


         At this point the DTC is configured to provide 10 ports to
         the system.  You should be able to attach a terminal to any
         of the DTC ports and log in.





























         Page  48              RX/V Release 1.1              004-5030








         -------   DTC Connected Serial Printer Installation  -------



         DTC Connected Serial Printer Installation

         RX/V Release 1.1 provides facilities to connect serial
         printers to the DTC.  This section describes the steps
         necessary to set up the system files to support such a
         printer.

         This facility relies on a new utility /etc/bridge/catnet.
         Catnet performs the inter-socket communications necessary
         for the remote printing.

         The example shown below connects a printer named dtc0pr4 to
         port 4 of the DTC named dtc0.

           1.  Using the /etc/bridge/remote command, set an internet
               address for the port that the printer is to be
               connected to (in this example 4), and disable the
               command interpreter for that port.  Remember that to
               exit the remote command you must enter an end of file
               character (usually ^D).

               The internet address should be chosen carefully.  The
               network number must match the current network.  It is
               also necessary that the least significant byte of the
               host number should match that of the DTC to which the
               printer is connected and the remainder of the host
               number can then be supplied as port numbers.  For
               example, given a DTC internet address of 126.0.0.88 as
               used in the previous section, the printer connected to
               port 4 would have an internet address of 126.0.4.88.


                 2  Bridge/remote>rsetde(!4)0ip=126.0.4.88[]
                 4  Portid !4mdefaulttparametersisavedsas]
                 5  Bridgeuremote>`sh ip[]
                 7                             Server Internet
                 8  Addres126.000.000.088     (Ethernet Address
                 9  %08000200E5ED)           (subnet
                10  mask000.000.000.255)
                11  Addresses              Physical Port Internet
                12  !2    Active only         !1    Active only
                13  !5    Active only         !4    126.000.004.088
                14  !8    Active only         !7    Active only
                16  !9    Active only
                17  Addresses               Rotary Port Internet
                18  !130  Rotary unused       !129  Rotary unused
                19  !133  Rotary unused       !132  Rotary unused
                21  BridgeRremote>n^D#d       !135  Rotary unused





         004-5030              RX/V Release 1.1              Page  49








         -------   DTC Connected Serial Printer Installation  -------



           2.  Make an entry in the /etc/hosts file for the printer
               using the internet address set above.


                23  681d /etc/hosts[]
                25  126.88  dtc008000200E5EDboot: tehama
                27  126.0.4.88dtc0pr4[]
                29  w[]
                31  q[]


           3.  Set the printer characteristics on the chosen port of
               the DTC.  To display the settable parameters issue the
               show command (as in {33} below).

               It should be noted, that XON/XOFF cannot be used
               exclusively to provide flow control, since the current
               printer state cannot be interrogated when a socket
               connection is first opened.  It is thus suggested that
               hardware flow control is used wherever available.

                32  # /etc/bridge/remote dtc0[]
                34  DefaultParameters (for PortId !4
                36  AUToDisconnect = 60 AUtoLogoff = OFF
                37  DeVices=z( Host, Glass )
                38  PermanentVC = ``''
                39  None = 9600 FFPad = Noned = None        CRPad =
                40  =F8ad = NonDUplex = Fullad = None       DataBits
                41  NonePRotocoStopBitsc=r1nous             PARIty =
                42  =sIgnoret = ( AlwaysAssert, NoToggle )  UseDTRin
                44  BReakAction = IGnore
                45  DataForwardc=iNone NECHOData = OFF
                46  EOMO=aDisabledlphaNum, CR, Term, Punct )
                47  FlowControlToo= ( Xon_Xofff) )
                48  XOFFT=m^S = 1       LongBReakAction = IGnore
                50  Bridge^remote> setd (!4) db=7 pari=e[]
                51  configurationa`4' parameters saved as
                52  Bridge remote> ^D#

           4.  Verify the connection to the printer by invoking the
               catnet command interactively.


                53  # /etc/bridge/catnet dtc0pr4 < /etc/passwd[]

           5.  The catnet program as shipped is not accessible to the
               lp spooler.  The easiest way to make it accessible is
               to change the owner of the command to lp.





         Page  50              RX/V Release 1.1              004-5030








         -------   DTC Connected Serial Printer Installation  -------




                54  # chown lp /etc/bridge/catnet[]

           6.  Now the printer port on the DTC is configured.  The
               remaining steps will introduce the printer to the lp
               spooler.

               First make sure the scheduler is not running.


                56  schedulerbstopped[]


           7.  Use the lpadmin command to define the printer.  In
               this example we have chosen the name dtc0pr4 for the
               printer.  Note that no device is specified since the
               catnet program will direct the output to the required
               location.

                57  # /usr/lib/lpadmin -pdtc0pr4 -mdumbnet
                    -v/dev/null[]

           8.  When the new printer is defined it will initially be
               disabled and rejecting requests.  Allow requests and
               enable the printer for printing.


                59  destinationa``dtc0pr4''rnow accepting requests
                61  printere``dtc0pr4'' now enabled
                63  # lpstati-t[]sched[]
                65  nohsystem defaultidestination
                67  dtc0pr4faccepting4requestsusince Jan  7 22:42
                68  22:43er dtc0pr4 is idle.  enabled since Jan  7




















         004-5030              RX/V Release 1.1              Page  51








         -----------------   STC 2925 Installation  -----------------



         STC 2925 Installation

         As shipped, RX/V Release 1.1 contains a driver for 1/2" tape
         that supports the Cipher tape drive sold by Ridge.  To use
         the STC 2925 tape drive (1600/6250 bpi) you must change two
         constants and build a new kernel.  The sample console
         session below shows these modifications.


           2  # ed config.h[]
           4  /MT_0[]
           6  s/1/0/p[]T_0            1
           8  /STC[]e MT_0            0
          10  s/0$/1/p[]CT_0          0
          12  w[]fine STCT_0          1
          14  q[]1


         After these changes have been made refer to the next section
         titled ``Building a New RX/V Kernel'' to build and install
         the new kernel.
































         Page  52              RX/V Release 1.1              004-5030








         --------------    Building a New RX/V Kernel  --------------



         Building a New RX/V Kernel

         There are a number of configuration parameters in the RX/V
         kernel that the knowledgeable system administrator may
         choose to modify.  These can be found in the directory
         /sys/cf.

           1.  After making the desired modifications, make a new
               kernel for your RX/V system using the makefile
               provided.

               In this example the time zone constants are changed to
               eastern time.


                 2  # ed config.h[]
                 4  $-3,$p[]
                 6                  /* Timezone informations */
                 8  #define DSTFLAGE        DST_USAT
                10  #define TIMEZONE        ZONE_PST
                12  #define[TIMEZONE        ZONE_EST
                14  ?PST[]
                16  3871
                18  #[cd ..[]
                20  # make acd[cf/; make
                21  -DREL=``1.1_beta''YS-DVER=``standard''``-ndef''
                22  CM-CCopyright'(c)c1987fRidge Computers v3.0
                24  conf.c: cc -O  -DSYS=``RX/V''  -DNODE=``undef''
                    DMACH=``ridge''a-c linesw.c`standard''  -
                26  linesw.c:ight (c) 1987 Ridge Computers v3.0
                28          rmk-fuunix start.o
                30          /bin/ld/-NB-oaunixrunix.ld -e _start
                    os/LIB1.af/io/LIB2.a/lkdb/LIBKDB.aLInet/LIBN.a
                    io/LIB2.aIBkdb/LIBKDB.aWBnet/LIBN.a.a  os/LIB1.a
                31  netinet/chmod.544wunixBWB.a
                32          rm -f start.o

           2.  Move this new kernel to / and shut the system down.
               Make sure you do not overwrite the existing kernel
               (/unix).













         004-5030              RX/V Release 1.1              Page  53








         --------------    Building a New RX/V Kernel  --------------




                34  # cd /[]x /unix.new[]
                36  # /etc/shutdown 0[]
                38  SHUTDOWN PROGRAM
                40  Tue Nov 10 11:42:58 EST 1987
                42  Broadcast Message from root (console) Tue Nov 10
                43  SYSTEM5BEING BROUGHT DOWN NOW ! ! !
                45
                47  phoneolinesufordthis system.ropriate
                49  Do you want to continue? (y or n):   y[]
                51  /usr/lib/lpshut:nscheduler.not running
                53  LP spooler system shut down.
                54  killed.rently running processes will now be
                56
                58  Wait forY`INIT:HSINGLETUSEReMODE'sbefore***
                59  #alting.
                61  INIT: New run level: S
                63  #Nsync;sync[]USER MODE
                64  #

           3.  Next reboot RBUG and use the h command to boot the new
               kernel.  See the ``RBUG'' appendix for more details on
               RBUG.


                66  RBUGs(08-May-87)sPC=00042000
                68  :h /unix.new[]
                70  board address=0 type=65  CIO number=0
                72  board address=20 type=3  SMD number=1
                74  Cache: number of buffers 256
                76  11:43:08 RX/V release: 1.1 version: standard on
                77  ridge
                79  11:43:08 CIOl0mPROM=Rev:1D56 avail mem = 3735552
                81  11:43:08 CIO 0 PCAEConf: 0
                83  ethernet initialized
                85  #NIT: SINGLE USER MODE


                86  # date[]
                87  Tue Nov 10 11:43:22 EST 1987

           4.  Once you are comfortable with the new kernel rename it
               to /unix and change to the multi user run level.

               It is very important that the kernel be named /unix
               when running multi user.  There are a number of pieces
               of the system (e.g., ps) that demand that the kernel
               be in the file /unix.





         Page  54              RX/V Release 1.1              004-5030








         --------------    Building a New RX/V Kernel  --------------




                89  # mv /unix.newi/unix[]
                91  # telinitn2[]


                92
                94  Swap:spacerestablished on /dev/dsk/c0d0s1.
                95  correct?a(y oren)oy[]0 08:43:51 PST 1987
                96  or n)uy[]nt to check system file /dev/syst ?(y
                98    /dev/syst
                100   File System: root Volume: 0
                102   ** Phase 2 - Check Pathnamesd Sizes
                104   ** Phase 4 - Check ReferenceiCounts
                106   529Pfiles516368eblockse15872 free
                107 checklistn? (y oren) y[]e systems from the
                109   /dev/rdsk/c0d0s2
                111   File System: usr Volume: 0
                113   ** Phase 2 - Check Pathnamesd Sizes
                115   ** Phase 4 - Check ReferenceiCounts
                117   1997hfiles 38224cblocks 35120 free
                119         .
                121         RX/V developed in cooperation with Bull
                122 Corporation.
                124 mounting: <u>rasa</u>usr>
                126 mounting: <u122>>ass</u122>5>
                128 mounting: <u1215>aas<</u1215>
                130 cronistarteding ram...
                132 localidaemons:rftpdnrshd rlogind telnetd rwhod.
                134 starting bridge servers: name file boot.
                136 Welcome to native UNIX(tm) on the Ridge
                137 login:






















         004-5030              RX/V Release 1.1              Page  55








         ------------    Booting and Shutting Down RX/V  ------------



         Booting and Shutting Down RX/V

         The Ridge 3200 has two switches that are of interest in
         booting the system.  The first is the keyswitch which should
         be in the PANEL position.  The rocker switch directly above
         the key switch can be depressed either on the edge marked
         MAN or the edge marked AUTO.

         If the AUTO edge is depressed and released the system
         attempts to boot with as little operator intervention as
         possible.  It will not stop in RBUG; it will assume the h
         command was intended.  In addition, if there is an
         initdefault entry in the inittab, that will be honored.

         If the MAN edge of the rocker switch is depressed and
         released the system will stop in RBUG where the operator can
         choose any set of RBUG commands.  The two most common
         choices are c or h.  In addition, the initdefault, if it
         exists in the inittab, will be ignored and the system will
         stop in single user mode.

         On the Ridge 32, the situation is more complicated.  The
         Ridge 32 has a LOAD rocker switch on the front panel.  This
         operates in conjunction with a switch called the load enable
         switch.  The load enable switch is the lowest toggle switch
         on the clock board (the clock board is the half height board
         at the far right of the card cage).

         With the load enable switch to the right, booting the system
         is like depressing the MAN edge of the 3200 rocker switch.
         With the load enable switch to the left, booting the system
         is like depressing the AUTO edge of the 3200 rocker switch.

         It is possible to change the load enable switch during the
         bootload.  This is not recommended.

         Booting the System for Single User Operation

         There are two ways to boot the system single user.  If there
         is no initdefault entry in your inittab, you can boot AUTO
         and supply s or S as the run level.  If the system is booted
         MAN it will stop in RBUG where an h command will cause the
         system to boot single user.










         Page  56              RX/V Release 1.1              004-5030








         ------------    Booting and Shutting Down RX/V  ------------




           2  RBUGs(08-May-87)sPC=00042000
           4  :h[]
           6  board address=0 type=65  CIO number=0
           8  board address=20 type=3  SMD number=1
          10  Cache: number of buffers 256
          12  08:28:05 RX/V release: 1.1 version: standard on ridge
          14  08:28:05 real mem  = 6291456 avail mem = 3735552
          16  08:28:05 CIO 0 CODE Rev: D
          18  08:28:05 ethernetAinitialized
          20  INIT: SINGLE USER MODE
          21  #

         Shutting Down Single User Operation

         When the system is running single user there are only a
         couple of things that you need to do to shut the system
         down.  First, you should make sure all mounted file systems
         are unmounted.  And finally, make sure you execute sync.
         This will ensure that the root file system is consistent on
         the disc.


           2  # sync[]ount[]
           3  #

         After this is done, you can reboot or power off the system.

         Booting the System for Multi User Operation

         There are two common ways of booting the system for multi
         user operation.  If you are already in single user mode you
         can simply execute telinit with the desired run level.  You
         should first make sure there are no file systems mounted
         that are in the mountlist file.

         To boot multi user from a non running system, depress the
         AUTO edge of the rocker switch and specify the desired run
         level if asked.

         One final word of caution:  There are some system facilities
         that assume the kernel is named /unix.  If you boot with a
         kernel with another name (e.g., h /unix.new), and enter run
         level 2 for multi user operation these facilities will not
         operate correctly.








         004-5030              RX/V Release 1.1              Page  57








         ------------    Booting and Shutting Down RX/V  ------------




           2  # telinit 2[]
           4  board address=0etype=65  CIO number=0
           6  board address=20 type=3  SMD number=1
           8  Cache: number of buffers 256
          10  08:28:05 RX/V release: 1.1 version: standard on ridge
          12  08:28:05 real mem  = 6291456 avail mem = 3735552
          14  08:28:05 CIO 0 CODE Rev: D
          16  08:28:05 ethernetAinitialized
          18  IsathepdateeTuebNovh10 08:28:37dPSTc19871correct? (y
              or n) y[]

         It is a good idea to check all file systems when the system
         is booted for multi user operation.


          19  y[]you want to check system file /dev/syst ?(y or n)
          21    /dev/syst
          23    File System: root Volume: 0
          25    ** Phase 2 - Check Pathnamesd Sizes
          27    ** Phase 4 - Check ReferenceiCounts
          29    526Pfiles515568eblockse16672 free
          30  (y orun)ay[]to check file systems from the checklist ?
          32    /dev/rdsk/c0d0s2
          34    File System: usr Volume: 0
          36    ** Phase 2 - Check Pathnamesd Sizes
          38    ** Phase 4 - Check ReferenceiCounts
          40    1997hfiles 38224cblocks 35120 free
          42          .
          44          RX/V developed in cooperation with Bull
          45  Corporation.
          47  mounting: <u>rasa</u>usr>
          49  mounting: <u122>>ass</u122>5>
          51  mounting: <u1215>aas<</u1215>
          53  cronistarteding ram...
          55  localidaemons:rftpdnrshd rlogind telnetd rwhod.
          57  starting bridge servers: name file boot.
          59  Welcome to native UNIX(tm) on the Ridge
          60  login:

         Shutting Down Multi User Operation

         When the system is in multi user mode (i.e., run level not s
         or S) the system can be shut down to single user mode using
         /etc/shutdown.  Just follow its instructions.








         Page  58              RX/V Release 1.1              004-5030








         ------------    Booting and Shutting Down RX/V  ------------




           2  # /etc/shutdown 0[]
           4  SHUTDOWN PROGRAM
           6  Tue Nov 10 11:27:57 EST 1987
           8  Broadcast Message from root (console) Tue Nov 10
           9  SYSTEM5BEING BROUGHT DOWN NOW ! ! !
          11
          13  phoneolinesufordthis system.ropriate
          15  Do you want to continue? (y or n):   y[]
          17  /usr/lib/lpshut:nscheduler.not running
          19  LP spooler system shut down.
          21  All currently running processes will now be killed.
          23  ****   SYSCON CHANGED TO /dev/console  ****
          25  #ait for `INIT: SINGLE USER MODE' before halting.
          27  INIT: New run level: S
          28  INIT: SINGLE USER MODE

         Once in single user mode, sync the root file system and you
         can reboot or power the system off.


          30  # sync[]































         004-5030              RX/V Release 1.1              Page  59








         ------------    Changes Since RX/V Release 1.0  ------------



         Changes Since RX/V Release 1.0

         Problems Fixed Since RX/V Release 1.0

         multi-reel cartridge tape
                   The 1/4" cartridge tape driver now supports
                   multi-volume operation.  For example, you can now
                   create and read cpio archives of more than one
                   cartridge.

         cmt eod
                   The eod (end of data) function of the cmt(1)
                   command has been fixed.

         executables > 4mb
                   In RX/V Release 1.0 an executable file with more
                   than 4 megabytes of data would cause the system to
                   crash.  This has been fixed, however, it is still
                   possible to run out of swap space.

         setvbuf
                   In RX/V Release 1.0 setvbuf(3CS) would always fail
                   and return -1.  This has been fixed and
                   setvbuf(3CS) now works.

         file systems > 256 mb
                   In RX/V Release 1.0 df(1M) and dlist(1M)
                   incorrectly reported errors for file systems with
                   a large number of inodes.  This has been fixed.

         printer driver
                   The printer driver now recognizes a printer that
                   is connected after the system is booted.  The
                   initialization that tests for printer type is now
                   done during open(2).

                   The printer driver has also been enhanced to
                   provide support for Versatec printers and
                   plotters.

                   In addition, canceling a print job no longer
                   causes DMA errors.

         adventure
                   adventure(6) has been added to the standard
                   distribution.

         ct
                   The  ct(1C) command has been added to allow call
                   back to a remote terminal.



         Page  60              RX/V Release 1.1              004-5030








         ------------    Changes Since RX/V Release 1.0  ------------



         sadp
                   The sadp(1m) utility now accepts device names of
                   the form c0d0.

         man
                   The man(1) command now orders output from multiple
                   sections in numerical order.  It also stops
                   between sections.

                   There were problems in RX/V Release 1.0 with the
                   output from man(1).  These were manifest as odd
                   white space in the text and video modes that were
                   not reset where appropriate.  These have been
                   fixed.

         lp model files
                   Several new model files have been added to
                   /usr/spool/lp/model.  See those files for more
                   information.

         signal handler interface
                   Handlers called as a result of kills now get
                   context information passed to them.  See the
                   online manual page for more details.

         as
                   The assembler now returns nonzero status if the
                   assembly failed.

         more
                   Invoking more(1) with input defaulted to the
                   terminal is now considered an error and a usage
                   message is printed.

         encryption
                   The editor ed(1) now supports the -x option for
                   data encryption on domestic versions of RX/V.

                   Data encryption has been fixed in vi(1) and ex(1).

         csh
                   File name expansion using * and ? in csh(1) when
                   the directory contains 14 character file names now
                   works.

                   The builtin command ``kill -l'' has been fixed and
                   no longer causes csh(1) to terminate prematurely.

         terminfo
                   The terminfo data base was damaged as shipped in
                   RX/V Release 1.0.  This was most often noticed as


         004-5030              RX/V Release 1.1              Page  61








         ------------    Changes Since RX/V Release 1.0  ------------



                   the absence of the vt100 definition.  This has
                   been corrected.

                   Also, the vt100-w description was fixed to use the
                   full 24 line screen.

                   The tvi925 definition was fixed to properly scroll
                   folded lines in vi.  In RX/V Release 1.0 such a
                   folded line would overprint the two parts on one
                   line.

         telnet
                   Flow control characters now work on telnet
                   connections.

                   In RX/V Release 1.0 there were many spurious NUL
                   characters passed through on telnet connections.
                   These have been eliminated.

         ctime
                   In RX/V Release 1.0 ctime(3C) had problems with
                   daylight savings time.  These problems have been
                   fixed.

         mailx
                   The mailx(1) command, when asked to log outgoing
                   messages, does so in the correct directory.

         ethernet timouts
                   In RX/V Release 1.0 the timeout values were being
                   miscalculated and were always about 30 seconds.
                   They are now correctly calculated.  The correct
                   values prevent the appearance that there are long
                   delays on the network.

         /etc/machconf
                   The /etc/machconf script was setting the swap size
                   incorrectly.  This has been fixed.

         kermit
                   The kermit utility has been modified to use the
                   same lock file conventions as the uucp utilities.

         sendmail
                   In RX/V Release 1.0 there was a problem that
                   occasionally caused mail to get stuck in the mail
                   queue.  This was a problem in sendmail(1M) which
                   has been fixed.

                   The invocation of sendmail(1M) in the /etc/rc.inet
                   script has been changed to be done only if there


         Page  62              RX/V Release 1.1              004-5030








         ------------    Changes Since RX/V Release 1.0  ------------



                   is a sendmail configuration file and the
                   specification of the queueing interval was fixed.

         /etc/rc
                   The removal of uucp files that is done in /etc/rc
                   has been corrected.

         ftp
                   The networking utility ftp(1) has been enhanced to
                   handle the multiple line replies generated by some
                   systems.

                   In RX/V Release 1.0 the ftpd(1M) daemon was
                   started in /etc/rc.inet script with debug enabled.
                   This caused a file (/tmp/ftplog) to be written
                   which logged all incoming ftp connections.  This
                   debug flag has been removed.

         installation scripts
                   The installation procedures were leaving temporary
                   directories in /tmp.  This is no longer true.

         longjmp
                   In RX/V Release 1.0 longjmp(2) could return any
                   value, including 0.  It is no longer possible for
                   longjmp(2) to return 0.

         vtocdft
                   The VTOC definition in vtocdft has been corrected.

         MAXFLOAT and MAXDOUBLE
                   These constants in <values.h> have been corrected.
                   You will need to recompile source to take
                   advantage of these corrections.

         host names
                   The network daemon rwhod(1M) has been fixed to
                   allow punctuation characters such as _ to appear
                   in host names.

         netstat
                   The networking utility netstat(1M) has been
                   changed to provide a more useful display of
                   statistics when invoked with a reporting interval.

         dirname
                   The dirname(1) utility has been fixed to work
                   properly.  The command ``dirname x'' was returning
                   ``x''.  It now returns ``.''.




         004-5030              RX/V Release 1.1              Page  63








         ------------    Changes Since RX/V Release 1.0  ------------



         uucp
                   The crontab for uucp has been corrected.  See the
                   crontab in /usr/spool/cron/crontabs/uucp for the
                   new content.

         Compatibility Changes Since RX/V Release 1.0

         /etc/profile
                   The script /etc/profile no longer defines a set of
                   ls related shell procedures.  This change was made
                   to bring the system more in line with other System
                   V systems.

         <ioctl.h>
                   This empty header file has been added for
                   compatibility reasons.

         /etc/setdate
                   The program /etc/setdate has been removed.  Use
                   /etc/checkdate or date(1) to set the date.

         /etc/tset
                   The program /etc/tset has been removed from the
                   system.

         default tty modes
                   The default modes for tty devices have changed
                   with this release.  They have been changed to make
                   them more compatible with other System V systems.
                   You can get the same erase and kill characters by
                   adding

                           stty erase ^H kill ^X

                   to your /etc/profile, .profile or .login file.


















         Page  64              RX/V Release 1.1              004-5030








         ----------   Changes Planned for Future Releases  ----------



         Changes Planned for Future Releases

         swap space
                   In RX/V Release 1.1 a process can start that
                   requires more swap space than is provided by the
                   system.  In the next release this has been changed
                   such that the process will fail in exec(2).

         lf, lc, et. al.
                   These links to ls will be removed in the next
                   release.  If you want to retain the effect of
                   these links you can define shell procedures or
                   aliases at this time.

         sysridge
                   The system call sysridge is being replaced by
                   sysmachdep(2).  In this release both are
                   supported.  In the next release only sysmachdep
                   will be supported.

         xsys
                   The utility xsys(1M) is being replaced by prtconf
                   in the next release.






























         004-5030              RX/V Release 1.1              Page  65








         --------    RX/V Release 1.1 Known Problem Summary  --------



         RX/V Release 1.1 Known Problem Summary

         odd parity on the console
                   The terminal connected as the console should not
                   be configured to generate odd parity.  If it is
                   you will not be able to boot your system.  Simply
                   configure the terminal with no or even parity.

         dd to cartridge tape with bs > 60k
                   Writing blocks of more than 60k bytes to the
                   cartridge tape with dd will not work.  Writing
                   blocks of 64k bytes or more hangs the system,
                   rendering it unusable.

         libdbm
                   This 4.2bsd library creates files that may have
                   gaps in them (i.e., data pages not used in the
                   middle of the file).  This can cause fsck(1m) to
                   become upset.  There is nothing wrong, but fsck's
                   output can be confusing.

         lp
                   The lp(1) command will not accept the
                   specification of a file on the command line if the
                   access to the directory has been restricted.  In
                   this case, simply specify the file as redirected
                   input to lp.

         DTC
                   The DTC will not flush output when the interrupt
                   key is depressed.

                   There is a problem with the modem control lines on
                   ports 0 & 1 which may require special cabling.
                   The symptom is that one or both ports will appear
                   non-functional.  Port 1 does not raise DCD (pin
                   8), and port 0 does not raise DCD (pin 8), CTS
                   (pin 5), or DSR (pin 6).  This can be worked
                   around by using a 3 (or 4) wire cable on these
                   ports with pins 2, 3, and 7 (and 1).  Another
                   workaround is to tie DCD (pin 8), CTS (pin 5), and
                   DSR (pin 6) to DTR (pin 20) which should be driven
                   by the terminal.

         pseudo ttys
                   The shl command does not work on pseudo ttys.

         ethernet cable disruption
                   When faulty equipment is attached to the ethernet
                   or the cable is not properly terminated the system
                   will experience a large number of ethernet errors.


         Page  66              RX/V Release 1.1              004-5030








         --------    RX/V Release 1.1 Known Problem Summary  --------



                   The system may begin to accumulate defunct
                   processes and the rwho daemon, rhowd(1M), will not
                   recover until the system is rebooted.

                   When this occurs the RX/V system cannot be
                   successfully booted.  If this is the case, isolate
                   the system from the network by disconnecting the
                   transceiver cable at the back of the system and
                   reboot.

         csh
                   If you run the csh and try to execute a Bourne
                   shell script (especially one containing a # in the
                   first character position) the csh tries to
                   interpret the script.  The best way to prevent
                   this is to start every Bourne shell script with a
                   : character.

         as
                   The assembler, as(1), can process header files.
                   However, to enable this feature you must provide
                   the -I flag.  See the online manual page for as(1)
                   for more information.






























         004-5030              RX/V Release 1.1              Page  67








         -----------------    Compatibility Issues  -----------------



         Compatibility Issues

         This section is a brief list of compatibility issues that
         have been accumulated over the lifetime of RX/V Release 1.0.
         They are organized into two subsections:  those of general
         interest and those of interest to users moving from the
         Ridge proprietary operating system ROS.

         General Compatibility

         type char in C
                   The default for the type char in C is unsigned.
                   Use the -k flag to the cc compiler if you want
                   signed characters, but be warned that you do not
                   get the best performance from your application.
                   For specific instances you can also use the signed
                   keyword in C.

         setjmp
                   Due to the code generation techniques of the RISC
                   Optimized compilers the user is cautioned to use
                   the setjmp(2) and longjmp(2) system calls
                   carefully.  You cannot assume that local variables
                   retain state across a setjmp/longjmp pair.

         fdopen
                   In some systems (mostly BSD based) it is possible
                   to have two standard I/O streams open with the
                   same file descriptor.  This does not work in
                   System V.  If you have code of the form:

                        Out==ffdopen(d,""w");

                   change it to look like:

                        Out==ffdopen(dup(d), "w");

         HZ
                   The manifest constant HZ is defined to be 50 for
                   RX/V.  If you have applications that do not use
                   the constants from the header files you may
                   experience incorrect times being reported by your
                   applications.

         stty/gtty
                   These obsolete interfaces will lose some modes if
                   used to save and restore tty modes.  Instead use
                   the TCGETA ioctl call to save the modes.  Use
                   either the TCSETA, TCSETAF or TCSETAW ioctl calls
                   to restore the modes.



         Page  68              RX/V Release 1.1              004-5030








         -----------------    Compatibility Issues  -----------------



         Compatibility With ROS

         rsh
                   In ROS the restricted shell was named rshell and
                   the remote shell command was rsh.  This is just
                   the opposite of RX/V, rsh(1) is the restricted
                   shell and rshell(1) is the 4.2bsd remote shell.

         open
                   Unlike ROS the open(2) system call does not open
                   the current directory if the first argument is a
                   null string.

         as
                   The RX/V assembler does not process floating point
                   constants.  The ROS assembler does process
                   floating point constants, but sometimes precision
                   can be lost with the assembler's conversions.
                   With RX/V you should perform the conversion
                   manually and use hexadecimal constants.

         tty modes
                   On ROS the modes on tty lines were ``persistent''
                   in that they did not revert to default values when
                   a tty line was closed.  This was not normal System
                   V behavior.  For instance if you had a command
                   sequence like:

                        stty 1200 < $DEV; cat file > $DEV

                   change it to:
                        (stty 1200; cat file) < $DEV > $DEV

         sum
                   The output of sum(1) consists of two numbers.  The
                   first is a checksum which should be the same on
                   both RX/V and ROS.  The second number is a block
                   count which will differ due to the fact that the
                   RX/V block size is 512 and the ROS block size is
                   1024.













         004-5030              RX/V Release 1.1              Page  69








         -----------------   Documentation Summary  -----------------



         Documentation Summary

         The following table lists the publications available for
         RX/V Release 1.1:

         __________________________________________________________________
         |model  | part     |                                              |
         |number | number   | title                                        |
         |_______|__________|______________________________________________|
         |9201   | 004-2416 | RX/V Manual Set                              |
         |_______|__________|______________________________________________|
         |9112   | 004-1739 | RX/V System User's Reference Manual          |
         |_______|__________|______________________________________________|
         |9111   | 004-1723 | RX/V System Programmer's Reference Manual    |
         |_______|__________|______________________________________________|
         |9110   | 004-1717 | RX/V System Administrator's Reference Manual |
         |_______|__________|______________________________________________|
         |9150   | 004-2422 | RX/V Programming Guide                       |
         |_______|__________|______________________________________________|
         |9156   | 004-2472 | RX/V FORTRAN Section (for 9150)              |
         |_______|__________|______________________________________________|
         |9157   | 004-2488 | RX/V PASCAL Section (for 9150)               |
         |_______|__________|______________________________________________|
         |9179   | 004-2494 | RX/V Software Release Notes Binder           |
         |_______|__________|______________________________________________|

         As this is not a major release there are no printed manual
         updates being produced.  However, several corrections have
         been made to the online manual pages.  Where you have
         questions it is recommended that you consult the online
         manual pages.






















         Page  70              RX/V Release 1.1              004-5030








         -------------------   Problem Reporting  -------------------



         Problem Reporting

         Reporting Problems in Person

         If you have questions about or experience problems with RX/V
         Release 1.1 and you have purchased a service contract or
         your system is under warranty, you should contact your
         service representative at RIDGE Computers.  If you have not
         purchased a service contract and your system is not under
         warranty, consulting services are available.

         Main Memory Dump to Cartridge Tape

         In some failure scenarios it may be desirable to dump main
         memory to cartridge tape.  To do so first boot RBUG as
         described earlier in this document.  Then use the md command
         of RBUG to do the memory dump.


           2  RBUGs(08-May-87)sPC=00042000
           4  Memory Dump
           6  DumpComplete:00001536*Pages
           7  :

         This dump of main memory can then be read back into the
         system to be analyized with crash(1m).  Keep in mind that to
         read this cartridge into a file you will need 2048 disc
         blocks (as reported by df(1m)) for each megabyte of memory
         your system contains.

         For example, if your system contains four megabytes of
         memory, you will need 2048*4 (or 8192) blocks of disc space
         to put the memory dump online for analysis.

         To read the cartridge in and process it with crash, type:



           9  1536+0/blocks/inv/rct/0 of=dump bs=4096[]
          11  #5/etc/crashsdump
          12  >












         004-5030              RX/V Release 1.1              Page  71








         -------------------------    RBUG  -------------------------



         RBUG

         RBUG is a basic debugger provided in PROMs in your system.
         This appendix provides instructions for booting RBUG and a
         summary of the command syntax of RBUG.

         Booting RBUG

         Several times in the installation of RX/V the instructions
         will ask the operator to boot RBUG.  When asked to do so
         follow the steps listed in the appropriate section below.

         By default RBUG uses the first port on the CIO board whose
         address is 0 as the console.  RBUG will always communicate
         at 9600 baud on this port.

         For Ridge 3200 Systems

           1.  Set the key switch to the PANEL position.  This
               enables the MAN/AUTO rocker switch.

           2.  Depress the MAN/AUTO rocker switch in the MAN
               direction to slow boot the system.  After the various
               self tests have run the RBUG prompt should be
               displayed on the system console.


                 2  RBUGs(08-May-87)sPC=00042000
                 3  :

           3.  Set the key switch to the 1 position.  This disables
               the MAN/AUTO rocker switch.

         For Ridge 32 Systems

         To boot RBUG on a Ridge 32 system it is necessary to remove
         the front cover from the system to access switches on the
         clock board.  This board is the half-height board to the far
         right in the card cage.  After the front cover is removed
         and the clock board has been located:

           1.  Depress switch 0.  This is the lowest white button on
               the clock board.

           2.  Flip the load enable toggle switch to the right.  This
               is the lowest toggle switch on the clock board.

           3.  Boot the system by pressing and releasing the LOAD
               switch on the front panel.  After the various self
               tests have run the RBUG prompt should be displayed on
               the system console.


         Page  72              RX/V Release 1.1              004-5030








         -------------------------    RBUG  -------------------------




                 2  RBUGs(08-May-87)sPC=00042000
                 3  :

         RBUG Command Syntax

         This section describes the syntax of the RBUG command set.
         In the descriptions below the construct [...] signifies
         something that is optional.  The construct <...> signifies a
         parameter for which you must substitute a value in the form
         of an expression.

         Expressions consist of hexadecimal constants and the
         operators +, -, * and /.  Evaluation is left to right with
         all operators having equal precedence.  The table below
         gives some examples:

                             ____________________
                             |expression | value |
                             |___________|_______|
                             |a1         | a1    |
                             |___________|_______|
                             |a1+1       | a2    |
                             |___________|_______|
                             |3/2        | 1     |
                             |___________|_______|
                             |20+2/2     | 11    |
                             |___________|_______|
                             |14%2       | 14    |
                             |___________|_______|
                             |qqq        | =     |
                             |___________|_______|

         =  Invalid expressions result in commands failing and
         replacement operations stopping.

         Commands for Booting

         Software can be loaded into a Ridge system from either the
         system disc or the cartridge tape.  The h command loads from
         the system disc while the c command loads from the cartridge
         tape.

              c [<filenum>]er>] [d<drive>] [s<section>] [/<filename>]

         where:

         controller specifies which disc controller is to be used.
               Valid values are in the range 0-3.  The default value
               is 0.
         drive specifies which disc drive on the specified or implied


         004-5030              RX/V Release 1.1              Page  73








         -------------------------    RBUG  -------------------------



               controller is to be used.  Valid values are in the
               range 0-3.  The default value is 0.
         section specifies which section, or partition, on the
               specified or implied disc drive is to be used.  Valid
               values are in the range 0-F.  The default value is 0.
         filename specifies the name of the file in the root
               directory of the specified/implied partition that is
               to be loaded.  Any valid file name can be specified.
               The default value is unix.
         filenum specifies the number of files to be skipped on the
               cartridge before loading.  Any value is valid.  The
               default value is 1.

         The Command to Dump Physical Memory

         The md command writes all of the physical memory to the
         cartridge tape.

              md

         Other Commands Not Commonly Used

         Commands for Breakpoints

         Breakpoints can be set using the b command.  Up to 16
         temporary breakpoints can be in place at any one time.  The
         e command continues execution after encountering a
         breakpoint.
              b <addr>
              e

         where:

         addr  specifies the physical address at which the breakpoint
               is to be set.  This must be the start of an
               instruction.

         Commands to Display and Modify Registers

         There are 16 general registers and 16 special registers.
         The dr command displays the 16 general purpose registers.
         The dsr command displays the 16 special registers.

         The mr command is used to modify a general register.  The
         user is queried for a new value.  Only the last eight
         hexadecimal digits are retained (e.g., a replacement value
         of 100000000 is the same as 0).
              dr
              dsr<register>

         where:


         Page  74              RX/V Release 1.1              004-5030








         -------------------------    RBUG  -------------------------



         register specifies the number of the register to be
               modified.

         Commands to Display and Modify Physical Memory

         The d command displays physical memory.  The m command is
         used to modify physical memory on a byte by byte basis.  The
         user is queried for a new value for each byte starting at
         the specified physical address.  Modification is terminated
         by specifying any invalid value (usually / or .).

              m <addr> [<count>]

         addr  specifies the physical address at which display or
               modification is to begin.
         count specifies the number of the bytes to be displayed.
               The default is 16.




































         004-5030              RX/V Release 1.1              Page  75








         -------------   Standard Special Device Files  -------------



         Standard Special Device Files

         Major device numbers are a function of bdevsw and cdevsw in
         /sys/cf/conf.c.  Minor device numbers are a function of the
         driver used.  The ``standard'' values for major numbers are
         summarized in this section.

                 ___________________________________________
                 |block/char | major number | name in /dev  |
                 |___________|______________|_______________|
                 |    b      |            0 | dsk/c?d?s*    |
                 |___________|______________|_______________|
                 |    b      |            1 | mt/*          |
                 |___________|______________|_______________|
                 |    b      |            2 | ct/*          |
                 |___________|______________|_______________|
                 |    c      |            1 | console       |
                 |___________|______________|_______________|
                 |    c      |            1 | tty[0-9][0-9] |
                 |___________|______________|_______________|
                 |    c      |            2 | tty           |
                 |___________|______________|_______________|
                 |    c      |            3 | mem or kmem   |
                 |___________|______________|_______________|
                 |    c      |            3 | null          |
                 |___________|______________|_______________|
                 |    c      |            4 | rdsk/c?d?s*   |
                 |___________|______________|_______________|
                 |    c      |            7 | rct/*         |
                 |___________|______________|_______________|
                 |    c      |            8 | lp            |
                 |___________|______________|_______________|
                 |    c      |            9 | rmt/*         |
                 |___________|______________|_______________|
                 |    c      |           10 | sxt/???       |
                 |___________|______________|_______________|
                 |    c      |           12 | tty[p-s][0-f] |
                 |___________|______________|_______________|
                 |    c      |           13 | pty[p-s][0-f] |
                 |___________|______________|_______________|
                 |    c      |           15 | tcpip         |
                 |___________|______________|_______________|
                 |    c      |           25 | rnet          |
                 |___________|______________|_______________|

         The following sections provide details on how the minor
         device numbers for various drivers are composed.






         Page  76              RX/V Release 1.1              004-5030








         -------------   Standard Special Device Files  -------------



         Hard Disc

         The minor device number for the hard disc special device
         files encode the controller number, unit number, and
         partition number.

         The controller number is in the range 0 to 3.  The
         controller with the lowest device address is controller
         number 0.  The controller with the next higher device
         address is controller number 1, etc.

         The unit number is in the range 0 to 3.  This can be read
         directly from the switches on the device.  See the
         appropriate disc drive manuals for this information.

         The partition number is in the range 0 to 15 and is simply
         an index into the VTOC written on the disc at initialization
         time.

         These values are combined as shown in the figure below.

         _______________________________________________________________________________
         |   controller#    |       unit#       |          section/partition#           |
         |________|_________|_________|_________|_________|_________|_________|_________|
               Figure 2.  Hard Disc Minor Device Number Layout

         The files found in the dsk directory are the block special
         files and the files found in the rdsk directory are the
         character special files.  These files are named cmdnsp where
         m is the controller number, n is the unit number and p is
         the partition number.

         Asynchronous Lines

         The minor device number for the asynchronous line special
         device files encode the controller number and port number.

         The controller number is in the range 0 to 7.  The
         controller with the lowest device address is controller
         number 0.  The controller with the next higher device
         address is controller number 1, etc.

         The port number identifies which port on the controller is
         used.

         These values are combined as shown in the figure below.
             7      6      5      4      3      2      1      0
           |____________|____________________|____________________|
           | not used   |        cio#        |       port#        |
           |__Figure_3._|Asynchronous_Line_Device_Number_Layout___|



         004-5030              RX/V Release 1.1              Page  77








         -------------   Standard Special Device Files  -------------



         The file for controller 0, port 0 is named console.  All
         others are named ttydd where dd is the minor device number.
         Do not confuse these special files with those for the pseudo
         ttys.

         Line Printer

         The minor device number for the line printer special device
         files encode the controller number.

         The controller number is in the range 0 to 7.  The
         controller with the lowest device address is controller
         number 0.  The controller with the next higher device
         address is controller number 1, etc.

             ___________________________________________________
             |          not used             |      cio#        |
             |_____|_____|______|_____|______|_____|______|_____|
              Figure 4.  Line Printer Minor Device Number Layout

         Normally there is only one line printer per system.  This
         file is simply named lp.  There is no system convention for
         other line printer device file names.

         1/4 Inch Cartridge Tape

         The minor device number for the 1/4" cartridge tape special
         device files encode the controller number, tape format and a
         rewind on close flag.

         The controller number is in the range 0 to 7.  The
         controller with the lowest device address is controller
         number 0.  The controller with the next higher device
         address is controller number 1, etc.

         The rewind on close flag is 0 for rewind and 1 for no
         rewind.

         The tape format can be QIC-24/9-track, QIC-11/9-track or
         QIC-11/4-track.  These choices are encoded as listed in the
         table below.
                           ________________________
                           |_______________| Value |
                           |____|__________|_______|
                           |____|__________|_______|
                           |11  |__________|_______|
                           |____|__________|_______|

         These values are combined as shown in the figure below.




         Page  78              RX/V Release 1.1              004-5030








         -------------   Standard Special Device Files  -------------



           _______________________________________________________
           | not used   |        cio#        |   format    | rew  |
           |_____|______|______|______|______|______|______|______|
         Figure 5.  Layoutch Cartridge Tape Minor Device Number

         The files found in the ct directory are the block special
         files and the files found in the rct directory are the
         character special files.  The QIC-24 files are named c and
         cn, where c is the CIO number.  The n suffix signifies no
         rewind on close.  The QIC-11 files are named cq114, cq114n,
         cq119 and cq119n.

         1/2 Inch Magnetic Tape

         The minor device number for the 1/2" tape special device
         files encode the controller number, unit number, density and
         a rewind on close flag.

         The controller number is in the range 0 to 7.  The
         controller with the lowest device address is controller
         number 0.  The controller with the next higher device
         address is controller number 1, etc.

         The unit number is in the range 0 to 7.  This can be read
         directly from the switches on the device.  See the
         appropriate tape drive manuals for this information.

         The tape density can be 800, 1600, 3200 or 6250 bpi.  These
         choices are encoded as listed in the table below.

                              _Density___Value_
                              |__800___|___0___|
                              |_1600___|___1___|
                              |_3200___|___2___|
                              |_6250___|___3___|
                              |________|_______|

         The rewind on close flag is 0 for rewind and 1 for no
         rewind.

         These values are combined as shown in the figure below.
               7     6      5     4      3     2      1     0
             |___________|____________|_no___|__________________|
             |  ctrlr#   |  density   | rew  |      unit#       |
             Figure|6.__1/2-inch|Tape_Minor_Device_Number_Layout|

         The files found in the mt directory are the block special
         files and the files found in the rmt directory are the
         character special files.  These files are named [cxd]yz
         where x is the controller number, y is the unit number and z
         is chosen from the following table.


         004-5030              RX/V Release 1.1              Page  79








         -------------   Standard Special Device Files  -------------



                                _Density___z_
                                |__800___|_l_|
                                |_1600___|_m_|
                                |_3200___|_i_|
                                |_6250___|_h_|
                                |________|___|

         The cxd prefix is only used if there is more than one
         controller.  Any of these file names can have an n as a
         suffix indicating no rewind on close.











































         Page  80              RX/V Release 1.1              004-5030














         Preface.................................................   1

         RX/V Release 1.1 Introduction...........................   2

         Release Media Organization..............................   4
           Standard Files........................................   4
           Remaining Files.......................................   5

         Installation Procedures.................................   7
           Installing RX/V from Scratch..........................   7
             Disc Formatting.....................................   8
             Formatting the Primary Disc.........................   8
             Formatting Other Discs..............................  10
             Root File System Installation.......................  13
             Remaining Installations.............................  15
             Defining Other Discs................................  18
             Making Other File Systems...........................  20
             Detailed Installation Instructions..................  22
             Administrative Files................................  26
             Multiuser Operation.................................  34
           Installing an RX/V Update.............................  37
             Administrative Files................................  43
           Installing P&A Cartridges.............................  45

         Distributed Terminal Controller (DTC) Installation......  47

         DTC Connected Serial Printer Installation...............  49

         STC 2925 Installation...................................  52

         Building a New RX/V Kernel..............................  53

         Booting and Shutting Down RX/V..........................  56
           Booting the System for Single User Operation..........  56
           Shutting Down Single User Operation...................  57
           Booting the System for Multi User Operation...........  57
           Shutting Down Multi User Operation....................  58

         Changes Since RX/V Release 1.0..........................  60
           Problems Fixed Since RX/V Release 1.0.................  60
           Compatibility Changes Since RX/V Release 1.0..........  64

         Changes Planned for Future Releases.....................  65

         RX/V Release 1.1 Known Problem Summary..................  66

         Compatibility Issues....................................  68
           General Compatibility.................................  68
           Compatibility With ROS................................  69



                                    - i -











         Documentation Summary...................................  70

         Problem Reporting.......................................  71
           Reporting Problems in Person..........................  71
           Main Memory Dump to Cartridge Tape....................  71

         RBUG....................................................  72
           Booting RBUG..........................................  72
             For Ridge 3200 Systems..............................  72
             For Ridge 32 Systems................................  72
           RBUG Command Syntax...................................  73
             Commands for Booting................................  73
             The Command to Dump Physical Memory.................  74
             Other Commands Not Commonly Used....................  74
             Commands for Breakpoints............................  74
             Commands to Display and Modify Registers............  74
             Commands to Display and Modify Physical Memory......  75

         Standard Special Device Files...........................  76
           Hard Disc.............................................  77
           Asynchronous Lines....................................  77
           Line Printer..........................................  78
           1/4 Inch Cartridge Tape...............................  78
           1/2 Inch Magnetic Tape................................  79






























                                    - ii -














                               LIST OF FIGURES


         Figure 1.  RX/V Release 1.1 Cartridge Format............   6

         Figure 2.  Hard Disc Minor Device Number Layout.........  77

         Figure 3.  Asynchronous Line Device Number Layout.......  77

         Figure 4.  Line Printer Minor Device Number Layout......  78

         Figure 5.  1/4-inch Cartridge Tape Minor Device Number
                    Layout.......................................  79

         Figure 6.  1/2-inch Tape Minor Device Number Layout.....  79




































                                   - iii -














                                LIST OF TABLES


         TABLE 1.  Configuration for tehama......................   1

         TABLE 2.  Decreases in Disc Utilization from RX/V
                   Release 1.0 to RX/V Release 1.1...............  37












































                                    - iv -




                                                                                                                                                                                                                                                                                                                                                                                   
