1. Manuals
  2. Brands
  3. Silicon Graphics Manuals
  4. Desktop
  5. IRIS Workstation
  6. User manual

Silicon Graphics IRIS Workstation User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
IRIS Workstation Guide
Version 1.0
Silicon Graphics, Inc.
Mountain View
California 94043

Advertisement

Table of Contents
loading

Related Manuals for Silicon Graphics IRIS Workstation

Summary of Contents for Silicon Graphics IRIS Workstation

  • Page 1 IRIS Workstation Guide Version 1.0 Silicon Graphics, Inc. Mountain View California 94043...
  • Page 2 Copyright 1984, Silicon Graphics, Inc. © This document contains proprietary information of Silicon Graphics, Inc., and is protected by Federal copyright law. The information may not be disclosed to third parties or copied or duplicated in any form, in whole or in part, without prior written consent of Silicon Graphics, Inc.

  • Page 3: Table Of Contents

    CONTENTS 1. Introduction 2. Unpacking the IRIS Workstation Components 3. IRIS Workstation Specifications Hardware Components Ethernet Equipment Cables Monitor IRIS Control Panel Monitor Control Panel Monitor Back Panel Cabinet Power Switch Cabinet I/O Panel Cabinet Power Panel Power Switch Documentation 4.
  • Page 4 Connecting an ASCII Terminal to the IRIS Workstation Connecting a Modem to the IRIS Workstation 6.10 Connecting a Printer to the IRIS Workstation 6.11 Enabling a Network Connection to the IRIS Workstation 6.12 Tape Drive 6.13 Shutdown 6.14 Crash Recovery...

  • Page 5: Introduction

    1. Introduction This document explains how to install, test and operate an IRIS Workstation. It contains step-by-step procedures for installing the components that make up an IRIS Workstation. This document should be read carefully before installing an IRIS Workstation. The IRIS Workstation components are delivered assembled and ready for connection with cables provided in the delivery cartons.
  • Page 6 IRIS WORKSTATION GUIDE Introduction Version 1.0...

  • Page 7: Unpacking The Iris Workstation Components

    2. Unpacking the IRIS Workstation Components The IRIS Workstation system is shipped in two reinforced cardboard cartons. One contains the Electronics Cabinet and the other contains the Monitor and other components. Each component is delivered assembled and ready for connection with the cables provided in the IRIS Workstation delivery cartons.
  • Page 8 Table 2-1: IRIS Workstation Environmental Specifications Compare the equipment included in the tray with the list in Section 3. If any parts appear to be missing, contact Silicon Graphics Customer Service (see Section 1). 10. Cut the plastic straps on the white carton.

  • Page 9: Iris Workstation Specifications

    IRIS Terminal. 3.2 Ethernet Equipment The IRIS Workstation can be connected to an Ethernet local area network with an Ethernet transceiver and drop cable. • The Ethernet Transceiver connects the IRIS Workstation to the Ethernet.
  • Page 10 IRIS WORKSTATION GUIDE IRIS Workstation Specifications Figure 3-1: IRIS Workstation System Version 1.0...

  • Page 11: Cables

    • 1 15-conductor drop cable connects the Cabinet to an Ethernet transceiver. 3.3 Cables Each IRIS Workstation is supplied with a cable set for connecting the IRIS Workstation components. • 4 bundled, color-coded, coaxial video cables connect the video output of the Cabinet to the Monitor.
  • Page 12 IRIS WORKSTATION GUIDE IRIS Workstation Specifications Figure 3-2: IRIS Control Panel and Monitor Control Panel Version 1.0...

  • Page 13: Monitor Control Panel

    Panel on the Cabinet. Either button may be used. WARNING: Do not press the button Reset while the IRIS Workstation is running UNIX. If the IRIS Workstation is not running UNIX and is under control of the PROM Monitor, then the buttons or the switches...
  • Page 14 IRIS WORKSTATION GUIDE IRIS Workstation Specifications Figure 3-3: Monitor Back Panel Version 1.0...

  • Page 15: Cabinet

    Monitor. 3.5 Cabinet There are two control panels on the back of the IRIS 1400 Cabinet: an I/O Panel and a Power Panel. A switch controls power for the IRIS Workstation Power system. Power Switch switch for the IRIS 1400 Workstation is located beside the tape drive Power slot on the front upper-left corner of the Cabinet.
  • Page 16 IRIS WORKSTATION GUIDE IRIS Workstation Specifications Figure 3-4: IRIS 1400 Cabinet Back Panel Version 1.0...

  • Page 17: Cabinet Power Panel

    Cabinet through the convenience outlet located on the Cabinet Power Panel. 3.6 Documentation The IRIS Workstation is delivered with a complete set of documentation. • The IRIS Workstation Guide (this booklet) explains how to install, test and operate an IRIS Workstation.
  • Page 18 IRIS WORKSTATION GUIDE IRIS Workstation Specifications • The C and FORTRAN editions of the IRIS Graphics Library are quick reference cards with overviews of each command in the IRIS Graphics Library. • The UNIX Programmer’s Manual is a set of reference manuals and tutorials for the UNIX System.

  • Page 19: Hardware Installation

    4. Hardware Installation This section describes how to install and connect the components that make up an IRIS Workstation system (see Figure 4-1). Prior to installation, each component should be unpacked and placed near its final location. Since the IRIS Workstation components are delivered assembled, they only need to be connected with the cables provided in the delivery cartons.
  • Page 20 IRIS WORKSTATION GUIDE Hardware Installation Figure 4-1: IRIS 1400 Monitor to Cabinet Connections Version 1.0...

  • Page 21: Monitor To Cabinet Control Cable Connection

    Cabinet Power Panel. Monitor 4.6 IRIS Workstation to Serial Line Connection The IRIS Workstation can be connected to a modem, a terminal or a printer through a serial line attached to on the Cabinet I/O Port 2...

  • Page 22: Modem Connection

    4.7 IRIS Workstation to Ethernet Connection The IRIS Workstation can communicate with other hosts and terminals through an Ethernet local area network. The IRIS Workstation can be connected to an Ethernet local area network while the network is operating. Select an appropriate tap point on the Ethernet coaxial cable.

  • Page 23: Cabinet Ac Power Connection

    IRIS Workstation. 4.9 Cabinet to Dial and Switch Box Connection The IRIS Workstation can be connected to an optional Dial and Switch Box for sending information to an application program on the IRIS Workstation. Connect the 37-pin flat cable from the port on the Dial Box to the bottom left port on the Switch Box.
  • Page 24 IRIS WORKSTATION GUIDE Hardware Installation Version 1.0...

  • Page 25: Operation

    Normally, the boot and shutdown procedures are handled by the system administrator. They are covered here in outline form only. The IRIS Workstation can be configured by the customer in many ways. These include adding new accounts, new terminals and printers and connecting it to a local area network.

  • Page 26: Demonstration Programs

    5.2 Demonstration Programs After the IRIS Workstation has been booted, it can be tested by running the demonstration programs included in the directory /usr/demos. These include some simple programs like particles and some more sophisticated programs like flight.

  • Page 27: Monitor Adjustment

    “leftovers”, type the command gclear. The IRIS User’s Guide documents the IRIS Graphics Library, the software that a programmer uses to write applications for the IRIS Workstation. In the second section of that manual, the IRIS Graphics Library, there are a few sample programs that illustrate how the graphics software is used.

  • Page 28: Network Software

    Operation 5.4 Network Software The IRIS Workstation has three programs for using an Ethernet local area network: xcp, xx and xlogin. These simple commands allow the user to copy files from one host to another, run commands on a remote host and log into a remote host.

  • Page 29: Shutdown

    Operation 5.5 Shutdown The IRIS Workstation should not be left on indefinitely. However, since the Monitor has a long warmup period, the IRIS Workstation should be left on continuously during work hours. WARNING: Do not press either button or the...
  • Page 30 IRIS WORKSTATION GUIDE Operation Version 1.0...

  • Page 31: System Administration

    Workstation will be booted from and the display of checkout information about the boot state (see Appendix A). The IRIS Workstation can be booted from either a disk drive or a tape drive. These devices can be used automatically or explicitly through the PROM Monitor.

  • Page 32: Automatic Tape Drive Boot

    The PROM Monitor is a simple command interpreter through which each IRIS Workstation boot environment can be accessed. If the Boot Environment configuration switches are set to “01000”, the IRIS Workstation will be under the control of the PROM Monitor when the system power is turned on. Set the...

  • Page 33: Boot Checkout Information

    Since the IRIS Workstation can be booted from different environments (hard disks, tape drives, etc.) it may be useful to find the names of the files on a tape or disk before booting the IRIS Workstation. This information can be found with the PROM Monitor. For example, iris>...
  • Page 34 Is the date Thu Mar 22 09:14:01 PST 1984? (y or n) y A UNIX login prompt will then appear. Log into a UNIX account. The IRIS Workstation is shipped with three user accounts: rootcsh, root and guest. The rootcsh account is a privileged account with a C Shell environment.
  • Page 35 Kernel Number: SYSTEM 5 UNIX #135: [Fri May 4 11:15:09 PST 1984] Release ID: Release: Beta-1.5 (C) Copyright 1983 - UniSoft Corporation (C) Copyright 1983 - Silicon Graphics Inc. Kernel Size: kmem = 290816 Approximate Available Memory: avail = 1282048...

  • Page 36: File Systems And Fsck(1M)

    System Administration File Systems and fsck(1M) The disk drive on an IRIS Workstation has several partitions that are represented by device files in the /dev directory. Three of them are of interest to the user: the root file system (/dev/md0a), the swap space (/dev/swap) and the /usr file system (/dev/md0c).
  • Page 37 There are three fields in /etc/TZ: standard heading for time zone, offset from Greenwich Mean Time, optional daylight savings time zone. For example, the IRIS Workstation is shipped with the time zone set for Pacific Standard Time. PST8PDT For more information, see TZ(4).

  • Page 38: Naming An Iris Workstation

    14 characters long. 6.7 Adding a New Account New accounts can be created on the IRIS Workstation by adding a line to the file /etc/passwd. Additionally, the system administrator can set up the new user ’s environment with startup files, home directories, etc.
  • Page 39 IRIS WORKSTATION GUIDE System Administration root::0:0:Superuser:/:/bin/csh rootcsh::0:0:Superuser:/:/bin/csh rootsh::0:0:Superuser:/:/bin/sh daemon:*:1:1::/: bin:*:2:2:Binary Files:/: uucp:*:3:5:UUCP Login Account:/usr/spool/uucpPublic:/usr/lib/uucp/uucico adm:*:5:3:Administration:/usr/adm: uucpadm:*:8:8:UUCP Administration:/usr/lib/uucp: lp:*:9:9:Line Printer:/: guest::998:998::/usr/people/guest:/bin/csh Figure 6-2: Sample /etc/passwd File group. There are four fields to a line. The asterisk in the second field indicates that there is no group password.

  • Page 40: Connecting An Ascii Terminal To The Iris Workstation

    Port 2 Port 3 Port 4 instructions on how to physically connect the IRIS Workstation to a terminal with an RS-232 serial line. Edit the file /etc/inittab. Each line corresponds to a device file in /dev and contains four fields separated by colons. See Table 6-2 for a list of the correspondences between device files and physical ports on the Cabinet I/O Panel.
  • Page 41 IRIS WORKSTATION GUIDE System Administration File Description console Console terminal. Optional floppy disk drive. floppy Kernel memory (used by ps(1)). See mem(7). kmem Disk zero root (/) file system. md0a Disk zero usr (/usr) file system. md0c Optional disk one first file system.

  • Page 42: Connecting A Modem To The Iris Workstation

    See termcap(4). Login on the ASCII Terminal. 6.9 Connecting a Modem to the IRIS Workstation A modem can be connected to the IRIS Workstation through Port 2 Port 3 on the Cabinet I/O Panel. This modem can then be used by the UNIX Port 4 utilities cu and uucp.

  • Page 43: Connecting A Printer To The Iris Workstation

    The procedure above is intended for a dial-out modem. To connect a modem to the IRIS Workstation for dial-in use, a getty must be started on the appropriate port. To do this, edit /etc/inittab and delete the x in the second field of the line corresponding to the selected port.

  • Page 44: Enabling A Network Connection To The Iris Workstation

    # pr -f -l66 /etc/rc | lpr 6.11 Enabling a Network Connection to the IRIS Workstation The IRIS Workstation can be connected to an Ethernet local area network. See Section 4.7 for instructions on how to physically connect the IRIS Workstation to an Ethernet local area network network.

  • Page 45: Tape Drive

    Login through the network to another host. 6.12 Tape Drive The IRIS Workstation has an optional tape drive for backing up file systems on the disks and for reading new software distributions. See Table 6-4 for a list of tape drive specifications. In addition, the IRIS Workstation can be booted from the tape drive in case the root file system is damaged beyond repair (see Section 6.1).

  • Page 46: Crash Recovery

    6.14 Crash Recovery This section is necessarily incomplete. See Appendix C for a list of error messages and probable causes. If the IRIS Workstation stops running for some reason, first try to reboot it without hitting the button. Use the Reset /etc/reboot -q command.
  • Page 47 IRIS WORKSTATION GUIDE System Administration Tape Drive Procedures Backup $ cpio -oha1 . $ tar -cv . Incremental Backup $ find . -mtime -7 -print | cpio -oha1 $ find . -mtime -7 -print | tar -cv - Read Tape...
  • Page 48 IRIS WORKSTATION GUIDE System Administration Version 1.0...

  • Page 49: Appendix A: Configuration Switches

    Boot environment 00000 Floppy disk boot. 00001 Disk boot. 00100 Network boot. 01000 PROM Monitor. 01100 Serial line boot. 10000 Tape boot. all others Undefined. Table A-1: IRIS Workstation Configuration Switches 1. 0 means and 1 means Closed Open Version 1.0...
  • Page 50 IRIS WORKSTATION GUIDE Appendix A: Version 1.0...
  • Page 51 Appendix B: F -The U File System Check Program B.1 Introduction When a U operating system is brought up, a consistency check of the file systems should always be performed. This precautionary measure helps to insure a reliable environment for file storage on disk. If an inconsistency is discovered, corrective action must be taken.
  • Page 52 IRIS WORKSTATION GUIDE Appendix B: of free inodes, and part of the free-inode list. The super-block of a mounted file system (the root file system is always mounted) is written to the file system whenever the file system is unmounted or a sync command is issued.
  • Page 53 IRIS WORKSTATION GUIDE Appendix B: Free-list blocks are written to the file system whenever they have been modified and released by the operating system. B.3 Corruption of the File System A file system can become corrupted in a variety of ways. The most common of these ways are improper shutdown procedures and hardware failures.
  • Page 54 IRIS WORKSTATION GUIDE Appendix B: Super-Block One of the most common corrupted items is the super-block. The super-block is prone to corruption because every change to the file system’s blocks or inodes modifies the super-block. The super-block and its associated parts are most often corrupted when the computer is halted and the last command involving output to the file system was not a sync command.
  • Page 55 IRIS WORKSTATION GUIDE Appendix B: within the file system. If they don’t agree, then fsck may replace the count in the super-block by the actual free-block count. Free-Inode Count. The super-block contains a count of the total number of free inodes within the file system.
  • Page 56 IRIS WORKSTATION GUIDE Appendix B: If the stored link count is non-zero and the actual link count is zero, fsck may link the disconnected file to the lost+found directory. If the stored and actual link counts are non-zero and unequal, fsck may replace the stored link count by the actual link count.
  • Page 57 IRIS WORKSTATION GUIDE Appendix B: A directory inode within the U file system has the directory bit on in the inode mode word. The directory size must be a multiple of sixteen because a directory entry contains sixteen bytes of information (two bytes for the inode number and fourteen bytes for the file or directory name).
  • Page 58 IRIS WORKSTATION GUIDE Appendix B: If a directory entry inode number is pointing beyond the end of the inode list, fsck may remove that directory entry. This condition occurs if bad data is written into a directory data block. The directory inode number entry for “.” should be the first entry in the directory data block.
  • Page 59 IRIS WORKSTATION GUIDE Appendix B: will be discussed in initialization. Initialization Before a file system check can be performed, certain tables have to be set up and certain files opened. This section concerns itself with the opening of files and the initialization of tables. This section lists error conditions resulting from command line options, memory requests, opening of files, status of files, file system size checks, and creation of the scratch file.
  • Page 60 IRIS WORKSTATION GUIDE Appendix B: The default file system checklist file F (usually /etc/checklist) can not be opened for reading. Fsck terminates on this error condition. Check access modes of F. Can’t stat root Fsck’s request for statistics about the root directory “/” failed. This should never happen.
  • Page 61 IRIS WORKSTATION GUIDE Appendix B: failed. This should never happen. See a guru. Possible responses to the CONTINUE prompt are: attempt to continue to run the file system check. Often, however the problem will persist. This error condition will not allow a complete check of the file system.
  • Page 62 IRIS WORKSTATION GUIDE Appendix B: size, and checking inode format. UNKNOWN FILE TYPE I=I (CLEAR) The mode word of the inode I indicates that the inode is not a special character inode, special character inode, regular inode, or directory inode. See Section 4.2.1.
  • Page 63 IRIS WORKSTATION GUIDE Appendix B: Possible responses to the CONTINUE prompt are: ignore the rest of the blocks in this inode and continue checking with the next inode in the file system. This error condition will not allow a complete check of the file system. A second run of fsck should be made to re-check this file system.
  • Page 64 IRIS WORKSTATION GUIDE Appendix B: inode. This is only a warning. See Section 4.2.5. DIRECTORY MISALIGNED I=I The size of a directory inode is not a multiple of the size of a directory entry (usually 16). This is only a warning. See Section 4.2.5.
  • Page 65 IRIS WORKSTATION GUIDE Appendix B: The root inode (usually inode number 2) is not directory inode type. See Section 4.2.1. Possible responses to the FIX prompt are: replace the root inode’s type to be a directory. If the root inode’s data blocks are not directory blocks, a VERY large number of error conditions will be produced.
  • Page 66 IRIS WORKSTATION GUIDE Appendix B: Phase 1 or Phase 1b have found duplicate blocks or bad blocks associated with directory entry F, directory inode I. The owner O, mode M, size S, modify time T, and directory name F are printed. See Section 4.2.3 and 4.2.4.
  • Page 67 IRIS WORKSTATION GUIDE Appendix B: There is no lost+found directory in the root directory of the file system; fsck ignores the request to link a directory in lost+found. This will always invoke the UNREF error condition in Phase 4. Check access modes of lost+found. See fsck(1M) manual entry for further detail.
  • Page 68 IRIS WORKSTATION GUIDE Appendix B: SORRY. NO lost+found DIRECTORY There is no lost+found directory in the root directory of the file system; fsck ignores the request to link a file in lost+found. This will always invoke the CLEAR error condition in Phase 4. Check access modes of lost+found.
  • Page 69 IRIS WORKSTATION GUIDE Appendix B: ignore this error condition. LINK COUNT OWNER=O MODE=M SIZE=S MTIME=T COUNT=X SHOULD BE Y (ADJUST) The link count for F inode I is X but should be Y. The name F, owner O, mode M, size S, and modify time T are printed. See Section 4.2.2.
  • Page 70 IRIS WORKSTATION GUIDE Appendix B: BAD/DUP DIR I=I OWNER=O MODE=M SIZE=S MTIME= T (CLEAR) Phase 1 or Phase 1b have found duplicate blocks or bad blocks associated with directory inode I. The owner O, mode M, size S, and modify time T of inode I are printed.
  • Page 71 IRIS WORKSTATION GUIDE Appendix B: Possible responses to the CONTINUE prompt are: ignore the rest of the free-block list and continue the execution of fsck. This error condition will always invoke the DUP BLKS IN FREE LIST error condition in Phase 5.
  • Page 72 IRIS WORKSTATION GUIDE Appendix B: BAD FREE LIST (SALVAGE) Phase 5 has found bad blocks in the free-block list, duplicate blocks in the free-block list, or blocks missing from the file system. See Section 4.1.2, 4.2.3, and 4.2.4. Possible responses to the SALVAGE prompt are: replace the actual free-block list with a new free-block list.
  • Page 73 IRIS WORKSTATION GUIDE Appendix B: ***** FILE SYSTEM WAS MODIFIED ***** This is an advisory message indicating that the current file system was modified by fsck. If this file system is mounted or is the current root file system, fsck should be halted and UNIX rebooted. If UNIX is not rebooted immediately, the work done by fsck may be undone by the in-core copies of tables UNIX keeps.
  • Page 74 IRIS WORKSTATION GUIDE Appendix B: Version 1.0...

  • Page 75: Appendix C: Diagnostics

    Appendix C: Diagnostics I. HARDWARE DIAGNOSTICS A. default_intr. An interrupt has occurred for which there is no device driver. I/O err in swap. While swapping a user process, a hard error occurred on the swap disk. C. parity error. A parity error occurred somewhere in the onboard memory.
  • Page 76 IRIS WORKSTATION GUIDE Appendix C: devtab bflush: bad free list no fs no imt dsdattach: geteblk() failed D. swap error: swapping beyond process. Something is wrong with the user memory management code. timeout table overflow. The system attempted to put a time driven event on a queue, and there was no room in the queue.
  • Page 77 IRIS WORKSTATION GUIDE Appendix C: random gr error wnrepaint Version 1.0...
  • Page 78 IRIS WORKSTATION GUIDE Appendix C: Version 1.0...

  • Page 79: Appendix D: The C/Fortran Interface

    Appendix D: The C/FORTRAN Interface The FORTRAN 77 compiler on the IRIS Workstation uses a procedure calling convention that is incompatible with C. To intermix C and FORTRAN routines, special interface modules (called wrappers) are used to transform calling sequences. The first section of this appendix outlines the differences between C and FORTRAN.
  • Page 80 IRIS WORKSTATION GUIDE Appendix D: preceded by an underscore, are entirely in upper case, and are a maximum of six characters. FORTRAN does not allow underscores in identifiers! This is important to note when porting C routines written to interface to VAX FORTRAN 77 programs. The VAX FORTRAN 77 compiler appends an underscore to external function names it generates to distinguish them from C function entry points.
  • Page 81 IRIS WORKSTATION GUIDE Appendix D: Func() Here, the function Func has no parameters. If mkf2c is used to produce a FORTRAN-to-C wrapper, the FORTRAN entry would be FUNC. FUNC would transform the stack for C and call the C routine Func(). If mkc2f is used to produce a C-to-FORTRAN wrapper, the entry would be _Func, that would call the FORTRAN entry FUNC.
  • Page 82 IRIS WORKSTATION GUIDE Appendix D: Arrays of character variables are treated by FORTRAN as simple byte-arrays, with no alignment of elements. If the array sarray() is declared as character*(*) sarray() the length of the individual elements will be determined by the length passed at run time.
  • Page 83 IRIS WORKSTATION GUIDE Appendix D: FORTRAN character variable is treated specially (as discussed in the next section). When calling FORTRAN from C, the address of the string and a length is passed. The length defaults to one. In this case, the FORTRAN declaration for the parameter carray[] will be...
  • Page 84 IRIS WORKSTATION GUIDE Appendix D: int and will also be passed as a 32-bit value. Storing into any of these parameters will not have any effect on the original FORTRAN data. • A copy of the character string whose address is str1 would be passed.
  • Page 85 IRIS WORKSTATION GUIDE Appendix D: Invoking mkf2c and mkc2f mkc2f and mkf2c are invoked by a command line as mkc2f <input file> <output file> The output file contains assembly language routines that must be assembled and linked with the FORTRAN and C routines.
  • Page 86 IRIS WORKSTATION GUIDE Appendix D: To generate the assembly-language wrapper foowrp.s from the above file foo.c, the following set of commands should be used: extcentry foo.c foowrp.fc mkf2c foowrp.fc foowrp.s C-to-FORTRAN wrappers must be generated by coding a dummy C function to describe the interface.
  • Page 87 IRIS WORKSTATION GUIDE Appendix D: call-C wrapper callc.fc is automatically created from callc.c when the C source file changes. This is caused by the dependency of callc.o on callc.fc. (The programmer is responsible for placing the special comments for extcentry(1) in the C source.) .SUFFIXES :...
  • Page 88 C version of the IRIS Graphics Library (libgl.a) and the math library (libm.a) are searched.) FORTRAN binary files (referred to as files in the FORTRAN Reference Manual), are named with .j suffixes on the IRIS Workstation. If you expect to make these files and Version 1.0...
  • Page 89 IRIS WORKSTATION GUIDE Appendix D: keep them around (rather than compiling source directly to an executable each time), you must add rules to your makefile’s to treat them correctly. The makefile example in Section D.2 contains the correct rules. Note also that the .j suffix must be included on the” .SUFFIXES:”...
  • Page 90 IRIS WORKSTATION GUIDE Appendix D: NOTE: It is tempting to use the PARAMETER statement in FORTRAN to define constants for passing to the IRIS Graphics Library. The user is forewarned that any constants defined in a FORTRAN PARAMETER statement type...
  • Page 91 IRIS WORKSTATION GUIDE Appendix D: $CHAREQU INTEGER IA (4) DATA IA/4H(2F1, 4H2.4,, 4H3X, I, 4H8) WRITE(*,IA) iolist is equivalent to WRITE(*,’(2F12.4,3X,I8)’) iolist This corresponds to conventions commonly used in FORTRAN 66 dialects. NOTE: The use of Hollerith strings in new programs is strongly discouraged since it is not part of the FORTRAN 77 standard.
  • Page 92 IRIS WORKSTATION GUIDE Appendix D: Version 1.0...

  • Page 93: Appendix E: Iris Floating Point

    E.2 Floating Point Formats The IRIS Workstation uses the IEEE floating point format. The IRIS implementation offers single- and double-precision floating point in the basic format as outlined in the draft standard. The IEEE standard is considerably more complex and more precise than most...
  • Page 94 IRIS WORKSTATION GUIDE Appendix E: In addition, the standard specifies that the user should have control over how rounding is to occur. The user may opt to round toward nearest, toward zero, toward +∞ or toward -∞. Because of the user-control provided, the IEEE standard is quite difficult to implement and can suffer from unnecessary inefficiency due to the large number of special cases.
  • Page 95 After the operation is performed, the result is truncated to float. The implementation of floating point in C on the IRIS Workstation defines the C types double and float to be the same precision - that of single precision. This decision was made on the following basis: • Many of the operations performed on the IRIS Workstation provide...
  • Page 96 IRIS WORKSTATION GUIDE Appendix E: • When parameters are passed or expressions are calculated, float’s do not require a conversion. It is the user ’s responsibility to guarantee that the caller and callee agree when intermixing float (or double) and long float. Long floats should be used only in instances needing the extra precision.
  • Page 97 IRIS WORKSTATION GUIDE Appendix E: • A set of facilities is outlined below which provide the user with control over floating point exception handling. • An exception is triggered in either precision if an attempt is made to print a not-a-number or infinity. • The default handling of all floating point exceptions is to abort with a core dump. User control over floating point exceptions is provided by the C library routine fpsigset(), and the global exception data structure _fperror.
  • Page 98 IRIS WORKSTATION GUIDE Appendix E: no handler is specified, the data value in _fperror is set to zero except in the special case of the operation MATH and the type PARTIAL_SLOSS. • If error message printing has not been disabled by a call to fpsigset(), an error message concerning the exception will be printed on stderr. In the case of exceptions arising from the math routines, this error message may contain the erroneous operand.
  • Page 99 IRIS WORKSTATION GUIDE Appendix E: CONVERT denotes an interpretation of a floating point number was in progress. This occurs when a number is being printed, when an ascii string is being interpreted as a floating point number (using atof or _latof), or when a floating point number is being assembled or disassembled (ldexp, _lldexp, frexp, _lfrexp).
  • Page 100 _fperror completely identify the function raising the exception. E.4 Compiler Enhancements The IRIS Workstation contains a hardware floating point option. This option currently uses a multibus board from Sky Computer. The C compiler on the IRIS Workstation has been quite heavily optimized for floating point operations in both hardware and software floating point mode.
  • Page 101 Appendix E: Software Floating Point Enhancements The 68000 C compiler and the floating point library on the IRIS Workstation have been modified to expect parameters in volatile registers whenever possible. These are the same registers used for function return values. This reduces the overhead of floating point operations considerably.
  • Page 102 IRIS WORKSTATION GUIDE Appendix E: Version 1.0...

  • Page 103: Appendix F: Manual Pages

    Appendix F: Manual Pages...
  • Page 105 CC(1) Silicon Graphics CC(1) NAME cc, pc, f77 - C. Pascal and FORTRAN compilers for the 68000 SYNOPSIS cc [ options ] files... pc [ options ] files... f77 [ options ] files... DESCRIPTION cc is the UNIX C, Pascal and Fortran compiler for the 68000. It is also avail- able under the names f77 and pc.
  • Page 106 CC(1) Silicon Graphics CC(1) Suppress the loading phase of the compilation, and force an object file to be produced even if only one source file is given. Generate debugging information. Currently, this does not have meaning when C is intermixed with another language. For FOR-...
  • Page 107 CC(1) Silicon Graphics CC(1) Run only the macro preprocessor on the named C, FORTRAN, and Pascal files, and place the results on file.i. Compile the named files, leaving the C assembly language output in files suffixed .s, and the FORTRAN and Pascal binaries in files suffixed .j.
  • Page 108 /usr/bin/pjmptbl.o Pascal graphics jump table and C string converter SEE ALSO IRIS Workstation Guide Appendices D and E. B. W. Kernighan and D. M. Ritchie, The C Programming Language, Prentice-Hall, 1978 B. W. Kernighan, Programming in C—a Tutorial D.
  • Page 109 CC(1) BUGS The additional symbol table information optionally produced by ccom for dbx(1) is not supported as of IRIS Workstation release 1.7. DIAGNOSTICS The diagnostics produced by C, FORTRAN, and Pascal are intended to be self-explanatory. Occasional messages may be produced by the assembler or loader.
  • Page 110 CPIO(1) Silicon Graphics CPIO(1) NAME cpio - copy file archives in and out SYNOPSIS cpio -o [ #aBchv ] [ name-list ] cpio -i [ #BcdhmrtuvfsSb6 ] [ patterns ] cpio -p [ adlmruv ] directory DESCRIPTION Cpio -o (copy out) uses the name-list arguments, or reads the standard input...
  • Page 111 CPIO(1) Silicon Graphics CPIO(1) Swap both bytes and halfwords. Use only with the -i option. Process an old (i.e. UNIX System Sixth Edition format) file. Only useful with -i (copy in). EXAMPLE ls | cpio -o >/dev/mt0 cpio -o0 .
  • Page 112 EXTCENTRY(1) Silicon Graphics EXTCENTRY(1) NAME extcentry - extract FORTRAN-callable entry points from a C file SYNOPSIS extcentry infile outfile DESCRIPTION extcentry is used to extract C functions for which FORTRAN-callable interface routines (wrappers) are to be generated by the program mkf2c. extcentry...
  • Page 113 FSCK(1M) Silicon Graphics FSCK(1M) NAME fsck, dfsck - file system consistency check and interactive repair SYNOPSIS /etc/fsck [-y] [-n] [-sX] [-SX] [-t file] [-q] [-D] [-f] [ file-systems ] /etc/dfsck [ options1 | filsys1 ... - [ options2 | filsys2 ...
  • Page 114 FSCK(1M) Silicon Graphics FSCK(1M) argument is used as the scratch file, if needed. Without the -t flag, fsck will prompt the operator for the name of the scratch file. The file chosen should not be on the file system being checked, and if it is not a special file or did not already exist, it is removed when fsck com- pletes.
  • Page 115 FSCK(1M) Silicon Graphics FSCK(1M) systems. A - is the separator between the file system groups. The dfsck program permits an operator to interact with two fsck(1M) programs at once. To aid in this, dfsck will print the file system name for each message to the operator.
  • Page 116 C for input to the program. (This must be done manually. Refer to Appendix D of the IRIS Workstation Guide.) In all cases, mkf2c and mkc2f generate a .s file that must be assembled with as(1), and loaded with the FORTRAN and C routines that are to be interfaced.
  • Page 117 C-to-FORTRAN interface generator /usr/bin/mkf2c FORTRAN-to-C interface generator SEE ALSO IRIS Workstation Guide, Appendices D and E, Silicon Graphics, Inc. extcentry(1), cc(1) DIAGNOSTICS Mkf2c and mkc2f are very simple-minded about diagnosing syntax errors. They can detect such things as a formal parameter having its type declared when it is not in the formal parameter list.
  • Page 118 Multiple copies of sgboot may be running at a given time. The total number of instances of sgboot equals the number of IRIS Terminals that may be booted in parallel. SEE ALSO Silicon Graphics, lnc., IRIS Terminal Guide, Appendix B sgbounce(1M) Version 1.0 - 1 -...
  • Page 119 Sgbounce can be started by hand, as shown above, but should normally be started in the file /etc/rc.local. NOTE Only one copy of sgbounce may be running at one time. SEE ALSO Silicon Graphics, Inc., IRIS Terminal Guide, Appendix B sgboot(1M) October 1984 - 1 - Version 1.0...
  • Page 120 SMT(1) Silicon Graphics SMT(1) NAME smt - streaming magnetic tape manipulating program SYNOPSIS smt [ -t /dev/tapename ] command [ count ] DESCRIPTION Smt is used to give commands to a Quarter Inch streaming magnetic tape drive. If a tape name is not specified, the default tape drive is used. Smt uses the default tape device /dev/rmtioctl.
  • Page 121 TAR(1) Silicon Graphics TAR(1) NAME tar - tape archiver SYNOPSIS tar key [ name ... ] DESCRIPTION Tar saves and restores multiple files on a single file (usually a magnetic tape, but it can be any file). Tar’s actions are controlled by the key argument. The key is a string of characters containing at most one function letter and possi- bly one or more function modifiers.
  • Page 122 TAR(1) Silicon Graphics TAR(1) files compare files don’t compare The following characters may be used in addition to the letter which selects the function desired. On output, tar normally places information specifying owner and modes of directories in the archive. Former versions of tar, when encountering this information will give error message of the form “<name>/: cannot create”.
  • Page 123 TAR(1) Silicon Graphics TAR(1) tells tar not to restore the modification times. The modification time will be the time of extraction. Force tar to continue reading past tape errors. Force tar to follow symbolic links as if they were normal files or directories.
  • Page 124 XCP(1) Silicon Graphics XCP(1) NAME xcp - remote file copy SYNOPSIS xcp file1 file2 xcp [ -r ] file... directory DESCRIPTION xcp copies files between machines. file1 is copied to file2 or file is copied to directory/file. Each file or directory argument is either a remote file name of the form rhost:path, or a local file name (with a ‘/’...
  • Page 125 XX(1) Silicon Graphics XX(1) NAME xx - remote shell SYNOPSIS xx host command DESCRIPTION xx connects to the specified host and executes the specified command. xx copies its standard input to the remote command, the standard output of the remote command to its standard output, and the standard error of the remote command to its standard error.
  • Page 126 XLOGIN(1) Silicon Graphics XLOGIN(1) NAME xlogin - remote login SYNOPSIS xlogin rhost DESCRIPTION xlogin connects your terminal on the current local host system to the remote host system rhost. All echoing takes place at the remote site, so that (except for delays) xlogin is transparent.
  • Page 127 MT(4) Silicon Graphics MT(4) NAME mt - TM78/TU-78 MASSBUS magtape interface SYNOPSIS master mt0 at mba? drive ? tape mu0 at mt0 slave 0 DESCRIPTION The tm78/tu-78 combination provides a standard tape drive interface as described in smtio(4). Only 1600 and 6250 bpi are supported; the TU-78 runs at 125 ips and autoloads tapes.
  • Page 128 SMTIO(4) Silicon Graphics SMTIO(4) NAME smtio - UNIX streaming magtape interface DESCRIPTION The special file /dev/rmt1 refers to the UNIX streaming magtape drive, which is on the MULTIBUS using the DSD-5217 controller. The following descrip - tion applies to any of the transport/controller pairs. The special files...
  • Page 129 SMTIO(4) Silicon Graphics SMTIO(4) #define MTFSR /* forward space record */ #define MTREW /* rewind */ #define MTNOP /* no operation, sets status only */ /* structure for MTIOCGET - mag tape get status command */ struct mtget { short mt_type;...
  • Page 130 SMTIO(4) Silicon Graphics SMTIO(4) SEE ALSO smt(1), tar(1), cpio(1) BUGS The status should be returned in a device independent format, but the status returned is very device independent. Version 1.0 - 3 - October 1984...
  • Page 131 IRIS WORKSTATION GUIDE Appendix F: Version 1.0...

  • Page 133: Appendix H: Iris Workstation Rs-232 Interface

    A full modem can be connected to the IRIS Workstation by connecting each pin on the modem side to its partner on the IRIS Workstation port. Note that lines 6 (Data Set Ready) and 22 (Ring Indicator) are not required for the IRIS Workstation.
  • Page 134 IRIS WORKSTATION GUIDE Appendix H: A full modem connection with Request to Send (RTS) and Clear to Send (CTS) can be made by connecting pin 2 on the IRIS Workstation port to pin 3 on the modem. Figure H-l: 3-Pin Connection Figure H-2: 5-Pin Connection Version 1.0...
  • Page 135 Appendix H: IRIS WORKSTATION GUIDE Figure H-3: Full Modem Connection Figure H-4: Full Modem Connection with RTS and CTS Version 1.0...
  • Page 136 IRIS WORKSTATION GUIDE Appendix H: Version 1.0...

  • Page 137: Appendix I: Uucp Administration

    IRIS WORKSTATION GUIDE Appendix I: Appendix I: UUCP Administration I.1 Introduction This appendix describes how a uucp network is set up, the format of control files, and administrative procedures. Administrators should be familiar with the manual pages for each of the uucp related commands.
  • Page 138 IRIS WORKSTATION GUIDE Appendix I: granted to outside machines by each of the systems on the private network. Alternatively, access to/from the outside world can be confined to only one processor. This is frequently done to minimize the effort in keeping access information (passwords, phone numbers, login sequences, etc.) updated and to...
  • Page 139 IRIS WORKSTATION GUIDE Appendix I: Password File To allow remote systems to call the local system, password entries must be made for any uucp logins. For example, uucp:zaaAA:3:5:UUCP Login Account:/usr/spool/uucppublic:/usr/lib/uucp/uucico Note that the uucico daemon is used for the shell, and the spool directory is used as the working directory.
  • Page 140 IRIS WORKSTATION GUIDE Appendix I: ttyd2 4800 ttyd3 cua0 1200 The first entry is for a hard-wired line running at 4800-baud between two systems. Note that the acu-device field is zero. The second entry is for a line with a 1200-baud ACU. The last entry is for an Ethernet/XNS connection.
  • Page 141 IRIS WORKSTATION GUIDE Appendix I: (e.g., mh1212,boston5551212). For the hard-wired devices, this field contains the same string as used for the device field. The login information is given as a series of fields and login subfields in the format [expect send] where expect is the string expected to be read and send is the string to be sent when the expect string is received.
  • Page 142 IRIS WORKSTATION GUIDE Appendix I: Dialing Prefixes This file contains the dial-code abbreviations used in the L.sys file (e.g., py, mh, boston). The entry format is abb dial-seq where abb is the abbreviation and dial-seq is the dial sequence to call that location.
  • Page 143 IRIS WORKSTATION GUIDE Appendix I: When a remote computer logs in, the login name that it uses must appear in the USERFILE. There may be several lines with the same login name but one of them must either have the name of the remote system or must contain a null system name.
  • Page 144 IRIS WORKSTATION GUIDE Appendix I: access by local users is allowed (e.g., links to overseas universities). If neither of these files exist, uucp will be perfectly happy to forward for any system. As an example, if the entry for system australia were in the ORIGFILE but not in the FWDFILE on system mhtsa, it would mean that system australia would be capable of forwarding jobs into the network via system mhtsa.
  • Page 145 IRIS WORKSTATION GUIDE Appendix I: Compaction of Log Files The files SYSLOG and LOGFILE that contain logging information are compacted daily (using the pack command from the shell script uudemon.day) and should be kept for 1 week before being overwritten.
  • Page 146 IRIS WORKSTATION GUIDE Appendix I: uucp -r file mhtsd!/tom The -r option forces the job to be queued but does not invoke the daemon to process the job. The uucico command can then be invoked directly: /usr/lib/uucp/uucico -r1 -x4 -smhtsd the -r1 option is necessary to indicate that the daemon is to start up in master mode (i.e., it is the calling system).

  • Page 147: Appendix J: Oem Kernel Generation For The Iris Workstation

    All devices are addressed through the Multibus I/O space. The OEM customer is restricted to the Multibus addresses within the range: 0xF000 to 0xFFFF. Silicon Graphics has reserved the remainder of the Multibus I/O space for its own use. The constant MBIOBASE, defined in ../pmII/cpureg.h, is used as the base address for the Multibus I/O space.
  • Page 148 Appendix J: Interrupt Levels Currently the only interrupt level available for OEM use is level 5 and is further restricted to the IRIS Workstation. Development is in progress to allow shared interrupt levels. Physical I/O Interface The physical I/O interface under the IRIS system is different from the standard System V interface in a few important ways.
  • Page 149 Procedue for Kernel generation Change your directory to the standard kernel configuration area. % cd /usr/sys/conf Choose a template file based on your IRIS Workstation model and its options. Currently, the following kinds of configurations are available: The standard 1400 system.
  • Page 150 IRIS WORKSTATION GUIDE Appendix J: % make binary Normally, a new kernel is tested before it is installed for general use. This test usually takes the form of booting the new kernel while keeping a backup copy of the old kernel. The following steps copy your kernel into the root file system...
  • Page 151 IRIS WORKSTATION GUIDE Appendix J: # Wahoo 727 smd disk controller controller wah0 at mbO csr 0xFEDC priority 5 vector waintr disk at wah0 drive 0 disk at wah0 drive 1 disk at wah0 drive 2 disk at wah0 drive 3 The source for the Wahoo 727 driver lives in /usr/sys/OEM/wahoo.c.
  • Page 152 IRIS WORKSTATION GUIDE Appendix J: Version 1.0...

  • Page 153: Appendix K: The Iris Terminal Programming Environment

    There are some additional routines as well. When the programming environment is first shipped, these GL 1.9 routines may not yet have been ported to the IRIS Workstation, so programs written to run on the IRIS Workstation will use GL 1, and the IRIS Terminal programming environment will be GL 1.9.
  • Page 154 IRIS WORKSTATION GUIDE Appendix K: K.1 How the IRIS Terminal Program Works The IRIS terminal program consists of three parts: a communication section, a terminal emulator, and a dispatch routine. The communication section controls the network connection (where “network” is taken to mean RS-232, Ethernet (XNS or IP/TCP), or IEEE 488—any reliable...
  • Page 155 IRIS WORKSTATION GUIDE Appendix K: Every graphics command from the remote host is preceded by a graphics escape character, indicated here by <GESC>. The command token is sent encoded as two bytes, and is followed by byte-encoded versions of all the other input parameters.
  • Page 156 As an example, suppose you wish to make an IRIS Graphics Library command that clears the screen to a given color, and then returns the number of bitplanes on the system. The following routine on the IRIS Workstation does this: short funnycolor(col) Colorindex col;...
  • Page 157 IRIS WORKSTATION GUIDE Appendix K: The IRIS Terminal programming environment makefile’s are set up so that simplest change — adding a single routine to the remote graphics library — requires changing only files. These $IRIS/lib/lib.prim $IRIS/src/term/local.c. local.c contains the source code for all the additional routines, and lib.prim describes the parameters and return values of each of the...
  • Page 158 IRIS WORKSTATION GUIDE Appendix K: The second part of each entry (also a letter) is somewhat redundant information that tells the physical type of the entry. This could be looked up in a table, but it is included so that the awk scripts will run faster. Lower-case letters are used if the parameter is sent by the remote host;...
  • Page 159 IRIS WORKSTATION GUIDE Appendix K: % cd /usr/progenv/host/c/src/gl Compile the remote graphics library. % make install The new remote graphics library is in the directory /usr/progenv/engr/c/lib. It can be copied (and -ed) to some other directory. ranlib K.7 Generating an IRIS Terminal Program An IRIS terminal program (iris) can be compiled with a single procedure.
  • Page 160 IRIS WORKSTATION GUIDE Appendix K: should be sent and returned as arrays. In general, do not use any of the I/O routines from the standard C library, or you will interfere with the operation of the IRIS terminal program. To do I/O, use IRIS Graphics Library commands ( , etc.).

  • Page 161: Appendix L: Gl 1 And Gl 1.9 Software Differences

    Appendix L: GL 1 and GL 1.9 Software Differences This document describes the differences between release 1 of the graphics library (the standard release) and the version that is used in the IRIS terminal programming environment. The programming environment is a small part of GL 2 -- a project involving major hardware and software enhancements.
  • Page 162 IRIS WORKSTATION GUIDE Appendix L: compacted, depending on how much space can be recovered. The new routine gives users explicit control of the compactification. compactify(object) With the ability to program the terminal, display list editing becomes much less important. With the GL 2 hardware, it will become even less so. In principle, terminal programmers can develop their own display list structure and interpreters.
  • Page 163 IRIS WORKSTATION GUIDE Appendix L: hold all the hit data. For example, suppose that the following sequence of events occurs: pick(100); pushname(10); <hit>; pushname(20); <hit>; <hit>; popname(); pushname(30); pushname(65); <hit>; popname(); popname(); popname() ; endpick(foo); Each <hit> above stands for a graphics library command that would have caused something to be drawn on the screen.
  • Page 164 IRIS WORKSTATION GUIDE Appendix L: L.5 Changes to existing commands , in , can be arbitrary (in GL 1 it had to be 1 or 2). width linewidth(width) The matrix stack depth is no longer limited to 8. There is a hardware stack limit of 8, but on overflow the extra matrices are stored in software.
  • Page 165 IRIS WORKSTATION GUIDE Appendix L: L.8 Input/Output The GL 1 commands , and have been qvaluator() qbutton() qkeyboard() replaced by the single command . Similarly, the commands qdevice() have been replaced unqvaluator() unqbutton() unqkeyboard() . A new device that can be queued or unqueued is KEYBOARD.
  • Page 166 IRIS WORKSTATION GUIDE Appendix L: Error Error number Description ERR_FOV The field of view for the viewing command illegal (probably zero). ERR_BASISID The basis identifier you have tried to use is undefined. ERR_NEGINDEX You have used a negative index in a routine such as...
  • Page 167 IRIS WORKSTATION GUIDE Appendix L: Error Error number Description ERR_INPICK tried something that is illegal in picking mode. ERR_NOTINPICK tried something that is illegal except in picking mode. ERR_ZEROPICK have specified zero-size picking window. ERR_FONTBUG This should never happen. Please report it to your Silicon Graphics representative.
  • Page 168 IRIS WORKSTATION GUIDE Appendix L: Error Error number Description ERR_BADINDEXBUG This should not happen. Please report it to your Silicon Graphics representative. ERR_ZEROVIEWPORT One of your viewport’s dimensions is zero. ERR_DIALBUG This should not happen. Please report it to your...
  • Page 169 IRIS WORKSTATION GUIDE Appendix L: Error Error number Description ERR_ TAGEXISTS The tag you are trying to create already exists. ERR_OFFTOOBIG The offset you specified is too big. Your object does not contain that many entries. ERR_ILLEGALID You have given an illegal...
  • Page 170 IRIS WORKSTATION GUIDE Appendix L: Error Error number Description ERR_POPMATRIX Matrix stack underflow ERR_PUSHVIEWPORT Viewport stack overflow ERR_POPVIEWPORT Viewport stack underflow L.9 Curves routine specifies only a geometry matrix. The precision and basis curve() matrices are set up in separate calls. The routine creates a different...

Table of Contents