Irix 3.3 Major_Enhancements_and_Compatibility
Trevor Paquette
-------------------------
Irix 3.3 Release Notes
3. Major_Enhancements_and_Compatibility
Taken from the command 'pcat /usr/relnotes/standard/ch3.z' and edited to
remove underlining etc..
-------------------------
3. Major_Enhancements_and_Compatibility
This chapter describes the major software and hardware
enhancements included in the 4D1-3.3 release, summarizes
compatibility issues for the program development tools, and
provides a description of the subsystems provided with this
release.
This chapter is divided into the following sections:
o Major Enhancements
o Compatibility of Program Development Tools
o Description of 4D1-3.3 Subsystems
3.1 Major_Enhancements
This section is divided into two subsections that describe
the major software and hardware enhancements (respectively)
in release 4D1-3.3. The major software enhancements in the
4D1-3.3 release include:
o IRIX enhancements
o New compiler features
o 4Sight enhancements
3.1.1 Enhancements_to_IRIX Enhancements to IRIX fall into
these categories:
o POSIX
o Virtual memory/file systems
o Real-time programming
o Parallel programming
o Logical volumes
In release 4D1-3.3, IRIX provides the ability to graft
several physical disk partitions together into one
logical partition, referred to as a logical volume. A
logical volume can span multiple physical disks,
providing both larger data files and greater file
system throughput. Improved throughput is the result
of increased parallelism in the I/O process by striping
accesses across several drives and controllers. Using
logical volumes, it is possible to create file systems
as large as 8 gigabytes and individual data files as
large as 2 gigabytes.
Refer to the manual entries for mklv(1M), lvinit(1M)
and lvtab(4) for more detailed information about
logical volumes. A step-by-step procedure for creating
a logical volume is given in the IRIS-4D System
Administrator's Guide.
o Extensible file systems
The IRIX Extent File System (EFS) now allows partitions
containing EFS file systems to be extended without
bringing the system down or rebuilding the existing
file system contained in the partition. For example, a
logical volume containing an EFS file system can be
extended by adding one or more disk partitions to the
end of the existing logical volume.
Note: File systems can only be extended if a logical
volume is being created or if there is room
remaining in the disk partition (this is usually
not the case).
After this has been done, the growfs(1M) utility
program can be used to extend the existing EFS file
system to fill the newly enlarged logical volume. This
extension operation automatically preserves all the
data in the original file system. It is not necessary
to mkfs(1M) and then reload the data.
o POSIX compliance
As a beta site for the NIST POSIX Verification Suite,
Silicon Graphics is committed to providing a POSIX-
compliant operating system.
The 4D1-3.3 release provides a major step towards POSIX
(IEEE 1003.1) compliance. All functions and interfaces
specified by the 1003.1 Full Use Standard are provided
with the following exceptions:
o The behavior of file system operations specified
by 1003.1 is guaranteed only for local EFS file
systems, not for NFS file systems.
o The ANSI setlocale function as specified and
extended by Chapter 8 of the 1003.1 spec is not
implemented.
o The POSIX tar and cpio program extensions
specified in Chapter 10 are not provided.
Note: At the time release 3.3 was completed, the NIST
suite had not yet been released in final form,
so Silicon Graphics cannot warrant that release
3.3 will pass the final released version of the
NIST POSIX Verification Suite.
o Merged page and buffer caches
A number of significant changes have been made to the
kernel algorithms that manage system memory. All
system memory is now treated as a large cache that
holds pages of the virtual space of processes and pages
from disk files.
These changes have a number of beneficial effects,
including significant performance improvements in the
file system and correct semantics when a given file is
accessed both as a mapped file and through the
traditional read/write interface.
The cache is subordinate to memory attached to user
processes, so caching activity will not affect
currently running processes. Any page of free memory,
however, is now available to cache disk data, as long
as the file's corresponding inode is resident in the
in-core inode cache.
o Resident set size limitation
The kernel page replacement algorithm has been changed
to provide the ability to limit the number of physical
memory pages that a particular process can use at any
given time. This is called the Resident Set Size (RSS)
of a process.
By using this feature, it is possible to minimize the
effect that background jobs doing heavy paging have on
the interactive response of the system. Refer to the
setrlimit(2) manual entry for further information.
o No more preallocation of swap space
In previous versions of IRIX, it was impossible to
create any virtual space without having a place to
store it (i.e., main memory or swap space). In Release
4D1-3.3, the system has been changed so that storage
space is required only when the virtual space actually
needs to be stored.
For example, when a large program calls fork(2) and
then immediately calls exec(2) to execute a smaller
program, it is no longer required that the system have
enough swap and memory to hold twice the size of the
parent process. Since fork(2) marks the pages of the
parent copy-on-write and most of the parent's pages are
never touched by the child before it calls exec(2),
separate storage space is not required for most of the
child's logical pages in the interim between the fork
and the exec.
o Autogrowable mapped files
In this release it is possible to extend a mapped file
by storing to a virtual address corresponding to a
location beyond the current end of file. At the time
the file is originally mapped using the mmap(2) system
call, the caller specifies the file offset and length
of the segment to be mapped. If the specified segment
reaches beyond the end of file and autogrow mode has
been requested for the segment, then stores to virtual
addresses that correspond to locations beyond the end
of file cause the file to be extended automatically to
the required length. The extension is done in
multiples of pages (4096 bytes each) up to the limit
specified by the offset and length given at mmap(2)
time. All pages added to the file will be zero filled.
Refer to the mmap(2) manual entry for more information.
o Large virtual spaces handled more efficiently
The performance of programs that have large virtual
address spaces (more than 10 megabytes of code or data)
or many virtual address spaces (using many shared
libraries or mapped files) is much better in Release
4D1-3.3, as a result of changes in the way the kernel
virtual memory code manages the Translation Lookaside
Buffer (TLB). The TLB is a 64-entry cache on the
microprocessor that caches virtual to physical address
translations.
Large programs that exhibit poor reference locality
generate significantly fewer TLB faults in Release
4D1-3.3, resulting in much better performance.
3.1.1.1 Real-time_Programming The IRIX operating system
supports a powerful set of real-time programming features.
In combination, a programmer can use these features to time
events accurately, use signal handlers as true interrupt
routines, control allocation of real memory to the process
and provide for priority scheduling.
Real-time programming provides for a range of response time
and latency from very fast handling at device interrupt time
to high-priority dispatch of user processes to handle the
event.
The following enhancements have been made to the real-time
features of IRIX in Release 4D1-3.3:
o High-resolution interval timers and time-of-day clock,
accurate to 833 microseconds.
The maximum resolution of the system time-of-day (as
returned by the gettimeofday(2) call) and interval
timers (see setitimer(2)) has been increased from 10
milliseconds to 833 microseconds. By default, the
resolution is set to 10 milliseconds. If you want the
greater resolution, you can enable it as the superuser
with the new ftimer(1) command.
o Lower interrupt latency
The 4D1-3.3 release guarantees a maximum interrupt
latency of 650 microseconds on properly configured
systems. Maximum interrupt latency has been decreased
by reducing the worst-case time that interrupts are
masked by the operating system. On properly configured
systems, worst-case interrupt latency is 650
microseconds (assuming a 25 MHz processor).
o Kernel preemption points have been added to allow non-
degrading priority processes to preempt lower priority
processes even when the preempted process is executing
in the kernel. This provides a significant improvement
in worst-case process dispatch latency.
3.1.1.2 Parallel_Programming
o Gang scheduling
Cooperating processes can now be scheduled as a unit.
This ``gang scheduling'' of processes on multiple-
processor systems greatly increases the efficiency with
which cooperating processes communicate with one
another. With gang scheduling it is possible to run
parallel jobs efficiently in a time sharing
environment. This results in better overall system
performance, particularly on systems supporting many
simultaneous users or tasks. See schedctl(2) for more
information.
o Shared graphics within a parallel job
In Release 4D1-3.3, it is possible for graphics to be a
shared attribute within a shared process group. In
previous releases, only one process within the share
group could be a graphics process. A process that is
already a graphics process (that is, has called
winopen(3G)) and calls sproc(2) with a share mask that
specifies the sharing of address space automatically
creates a shared process group in which graphics is
shared. This means that any process within the share
group can make Graphics Library calls and that all such
calls affect the same window or graphics context.
It is important to note that Graphics Library code does
not prevent separate processes within a parallel job
from simultaneously accessing Graphics Library data
structures or the graphics pipe. Because the
programming model presented by the Graphics Library is
fundamentally stateful, the responsibility for the
definition and protection of critical regions must be
owned by the application program.
For example, suppose that two processes within the
share group want to perform a bgnpolygon, v3f, v3f, ...
endpolygon sequence, each for a different polygon. As
soon as one of the processes has done its bgnpolygon,
the other process must not touch the pipe until the
first process has done the corresponding endpolygon.
Thus the application code must make the above sequence
a critical region in each process in order to ensure
that the two processes do not interleave their
sequences of calls.
o Improvements to signal handling in parallel jobs
In Release 4D1-3.3 it is possible to generate a signal
to all members of a shared process group when any
member of that group dies. The prctl(PR_SETEXITSIG)
system call is used to activate this behavior and to
specify the signal that is delivered. Refer to the
prctl(2) and sproc(2) manual entries for details.
o Blocking and unblocking entire shared process groups
Two new routines are provided that are analogous to
blockproc(2) and unblockproc(2) but that act on entire
shared process groups. These are blockprocall(2) and
unblockprocall(2). Refer to the blockprocall(2) manual
entry for details.
o New debugging support in libmpc
Two new routines have been added to aid in debugging
parallel programs that use the locking primitives in
libmpc: usdumplock(3) and usdumpsema(3). These
primitives provide the ability to dump the history
associated with a single lock or semaphore,
respectively.
3.1.2 New_Compiler_Features
o The 4D1-3.3 release integrates MIPS 2.0 compiler
technology.
o The new compilers contain numerous improvements and
fixes over the previous release, most notably in the
code optimizer.
o Nearly complete ANSI C support:
o Include files provided with this release have been
changed to use
ANSI C-type prototypes.
o ANSI rules and type checking can be turned on with
a compiler switch.
o New ANSI types (for example, void, void*, const)
and ANSI constructs are recognized.
For developers who do not need to conform to the ANSI
standard immediately, the new compiler permits non-ANSI
constructs recognized by the current compiler. If you are
porting C applications from Release 4D1-3.2 to 4D1-3.3, be
aware that the ANSI C compiler outputs numerous new warning
messages where the previous compiler remained silent. If
ANSI compatibility is not required for applications you are
developing under Release 4D1-3.3, you can ignore these error
messages.
For more information on the specific ANSI support introduced
in Release 4D1-3.3, read ``Changes to Program Development
Tools'' in Chapter 5, ``Changes''.
3.1.2.1 4Sight_Enhancements Release 4D1-3.3 includes a new
version of 4Sight (1.5) in which retained canvases are
implemented when 4Sight is running in 24-bit RGB mode.
Previously retained canvases only worked when the server was
running in 8-bit color-index mode. A backgammon program has
been included in /usr/NeWS/demos as a demonstration of
retained canvases.
Psview(1) no longer caches the current page in 4Sight. This
means that the PostScript programs that use the currentfile
can now be previewed. It also means that 4Sight no longer
grows during extensive previewing. A complete and accurate
manual page is now provided.
Many bugs have been fixed as described later in these
release notes.
3.1.3 Graphics
3.1.3.1 Sphere_Library Release 4D1-3.3 includes a new
subroutine library called the Sphere Library, that draws
spheres by issuing GL calls. It can be called from C or
FORTRAN programs.
The Sphere Library files are /usr/lib/libsphere.a and
/usr/include/gl/sphere.h. There is an example program
located in /usr/people/4Dgifts/src/sphere.
Appendix B of these Release Notes contains manual pages for
the Sphere Library routines. These manual pages are also
available on-line.
3.1.4 Hardware_Enhancements The 4D1-3.3 release supports
the following new Silicon Graphics hardware:
o PowerVision Graphics
o 4D/300 POWER Series systems
o POWER Channel IO controller for POWER Series systems
o IPI2 disk subsystem for POWER Series systems
o System memory expansion to 256 MB on POWER Series
systems
o RV2 Raster Subsystem
o 14" Monitor Support (for 4D/20 and 4D/25 systems)
o Entry Plus Graphics Upgrade (for 4D/20 and 4D/25
systems)
o Multihead Personal IRIS
3.1.4.1 PowerVision_Graphics The PowerVision system is a
graphics supercomputer that renders 1 million polygons per
second and includes hardware support for real-time texture
mapping, polygon antialiasing, fog/haze effects, sub-
millisecond full-screen clear, arbitrary clipping planes,
and image processing operations. It also includes hardware
support for near-real-time rendering of higher-quality
images, with full-scene antialiasing, depth of field, and
motion blur.
Programs compiled with gl_s will run on the VGX workstations
without recompilation.
PowerVision is available as a complete system and as an
upgrade to existing members of the IRIS Power Series product
line.
3.1.4.2 4D/300_POWER_Series_Systems These multiprocessor
systems feature CPU boards which have 33 MHz
microprocessors, floating point units and associated caches.
Each 33 MHz processor board contains two complete CPU and
FPU pairs. This board is also available as an upgrade to
existing 4D/200 series systems in both server and graphics
configurations.
3.1.4.3 POWER_Channel_IO_Controller The POWER Channel IO
Controller provides a significant increase in IO bandwidth
for POWER Series systems. The POWER Channel has the
following features:
o Up to 32 megabytes per second VME throughput
o Two complete SCSI controllers, both supporting
synchronous SCSI
o Ethernet controller with DMA capability
3.1.4.4 IPI2_Disk_Subsystem IPI2 is a new high performance
VME disk interface. Each IPI2 controller can support up to
8 drives on each of its two independent channels. Each
drive has an unformatted capacity of 1.1 gigabytes and a raw
transfer rate of 6 megabytes per second. The largest
configuration supported at first release will be two
controllers, supporting 16 drives each, for a total of 32
gigabytes of high performance disk capacity.
3.1.4.5 256_MB_Memory Through the use of 4 megabit dynamic
RAMs, POWER Series machines now support a maximum memory
configuration of 256 megabytes.
3.1.4.6 RV2_Raster_Subsystem The 4D1-3.3 release includes
support for the RV2 raster subsystem. The RV2 is a single
board replacement for the RV1/RM1 three-board set.
The GT/GTX systems shipped after 7/1/90 may include RV2
boards and thus require the 4D1-3.3 release.
Note: The RV2 raster subsystem does not contain alpha
bitplanes.
3.1.4.7 14-Inch_Monitor_Support The 14-inch monitor
differs from our standard 19-inch monitor in that its
resolution is only 1024x768 instead of 1280x1024. This
difference is automatically recognized by the system
software, and the default transforms for graphics are set
accordingly.
However, there are times when applications need to know the
size of the monitor, for example, when placing and sizing
windows. There are getgdesc inquires to return this
information (see getgdesc(3G)).
_____________________________________________
getgdesc Inquiry Return Value
______________
19" Monitor 14" Monitor
____________________________________________
GD_XPMAX 1280 1024
GD_YPMAX 1024 768
GD_XMMAX 340 240
GD_YMMAX 272 180
_____________________________________________
3.1.4.8 Entry_Plus_Graphics_Upgrade The Entry Plus
graphics upgrade allows Z buffered RGB images to be
displayed on an eight bit Personal IRIS. This upgrade
includes a Z buffer and overlay planes. RGB images are
displayed in 8 bits by using dithering to approximate the
true color. When RGB mode is enabled in this configuration,
double buffering is turned off (because 4 bit RGB mode is
not supported).
The getgdesc call can be used to get information about the
configuration of the current system. In the case of an
Entry Plus graphics configuration, getgdesc will return the
following values:
_____________________________________
getgdesc Inquiry Return Value
____________________________________
GD_BITS_NORM_SNG_RED 3
GD_BITS_NORM_SNG_GREEN 3
GD_BITS_NORM_SNG_BLUE 2
GD_BITS_NORM_DBL_RED 0
GD_BITS_NORM_DBL_GREEN 0
GD_BITS_NORM_DBL_BLUE 0
_____________________________________
GD_BITS_NORM_SNG_CMODE 8
GD_BITS_NORM_DBL_CMODE 4
_____________________________________
This information indicates that there are three bits of red,
three of green, and two of blue in single buffered RGB mode.
It also shows that double buffered RGB mode is not
supported.
3.1.4.9 Multihead_Personal_IRIS For applications that
demand multiple screens, the Multihead Personal IRIS is now
available. This workstation incorporates up to four
multiple Personal IRIS graphics cards, each with their own
monitor. The system is based on the IRISette VME card set
and is packaged in a Professional IRIS chassis.
In this release, only two screens are supported, the second
of which is without window management.
3.2 Compatibility_of_Program_Development_Tools
This section describes the compatibility between these
software releases:
4D1-3.2 and 4D1-3.3
Release 4D1-3.3 is generally compatible with release 4D1-
3.2.
3.2.1 Upwards_Compatibility Binaries linked with the non-
shared versions of libfm.a or libgl.a must be relinked.
Silicon Graphics recommends always linking with the shared
versions of the font manager and the GL.
Most system header files have been changed to conform to the
ANSI C specification; in particular, non-ANSI names have
been renamed and function prototypes added. As a result,
some previously undetected "incorrect" C programs will be
detected.
There are a large number of enhancements and changes to
Fortran. Please read the Fortran release notes for Fortran
specific compatibility information.
In the following table, source means source files, whether
Fortran, C, or another language. Application libraries
means not only archive libraries of object files (.o files),
but also individual object files. Executables means
executable binaries (not shell command files).
_______________________________________________________________________
| | 4D1-3.3 System Software |
| |______________________________________________________|
|4D1-3.2 | Compilation | Tools | Execution |
|Generated | Environment | Environment | Environment |
| | (cc, f77, ar,| (nm, strip, | |
| | ld) | dbx, edge, | |
| | | lint, stdump, | |
| | | size, dis) | |
|______________|_______________|__________________|___________________|
|source | yes | NA | NA |
|______________|_______________|__________________|___________________|
|application | | | |
|libraries | yes | yes | NA |
|______________|_______________|__________________|___________________|
|executables | NA | yes | yes, unless |
| | | | the non-shared |
| | | | versions of |
| | | | the font |
| | | | manager or GL |
| | | | were used |
|______________|_______________|__________________|___________________|
3.2.2 Backwards_Compatibility While object files and
executables created under 4D1-3.3 may work on an older
system, this use is not recommended. Indeed, it is
dangerous to run a new executable on an older system as it
may have unpredictable consequences.
The 3.2 loader, ld, will generate warning messages if it
encounters an object file generated on a 3.3 system. This
warning can be ignored.
Due to changes in the shared library format, executables
linked under 3.3 to shared libraries will not execute
correctly under 3.2 or older systems. And, of course,
executables linked to private libraries under 3.3 should not
be executed on 3.2 or older systems.
3.3 Description_of_4D1-3.3_Subsystems
3.3.0.1 Execution_Only_Environment_Tape_1
eoe1.sw.unix This subsystem contains the core IRIX
commands and files and is required on all
systems.
eoe1.man.relnotes This is an on-line readable copy of the
IRIX release notes.
eoe1.man.unix This is an on-line copy of the IRIX user's
manual. Entries may be viewed with the
``man'' command.
3.3.0.2 Execution_Only_Environment_Tape_2
eoe2.sw.NeWS This is the 4Sight window manager and is
required by all workstations. This
subsystem contains the ``standard'' NeWS
fonts.
Courier Icon
Courier-Bold Iris
Courier-BoldOblique Screen
Courier-Oblique Screen-Bold
Cursor Times-Bold
Helvetica Times-BoldItalic
Helvetica-Bold Times-Italic
Helvetica-BoldOblique Times-Roman
Helvetica-Oblique type
eoe2.sw.X11 This is the run-time X11 windowing
package. It is required to run X11
applications. This subsystem includes the
following fonts that are required to run
X, along with some terminal emulator fonts
expected by xterm users:
6x10 cursor
6x12 Terminal
6x13 Terminal-Bold
8x13 Terminal-BoldNormal
8x13b TerminalNormal
9x15
eoe2.sw.Xapps These are X client applications.
eoe2.sw.Xdemos These are demonstration programs that make
use of the X windowing system. You must
install eoe2.sw.X11 in order for these
programs to work.
eoe2.sw.Xfonts These are a set of fonts which were
shipped with X11 Release 2. They are no
longer a part of X, but some older X
programs require these fonts to be in
place.
apl German sup
arrow Greek supsup
chess Hebrew swd
chp ipa sym
cyr krivo vbee
Cyrillic lat vctl
dancer met vg
fcor micro vgb
fg mit vgbc
fg-Bold oldera vgh
fg-Oblique plunk vgi
fgone rot vgvb
fgone-Bold runlen vgl
fgone-Oblique sansserif vmic
fgs sansserif-Bold vply
fqxb sansserif-Oblique vr
fr serif vrb
fr-Bold serifb vri
fr-Oblique serifi vsg
frone stan vsgn
frone-Oblique stempl vshd
frthree sub vxms
frtwo subsub xif
eoe2.sw.acct This is the System V Process Accounting
package. It is used to monitor system
resource usage on a per-user basis. When
Process Accounting is installed and turned
on, a record is kept of every command that
is executed along with data on the
resources the command used. Report
generating scripts are then run which
produce periodic reports of system
utilization. This package is useful when
it is desired to monitor usage patterns in
systems with large numbers of users.
eoe2.sw.bsdlpr This subsystem contains 4.3BSD line
printer software to allow the IRIS to
access remote printers using the lpd
protocol. Using the lpd daemon to control
local printers is not supported.
eoe2.sw.cdsio This is the driver for the VME Serial
Expansion board. It is required for
systems with that option installed.
eoe2.sw.crypt This subsystem contains the crypt and
makekey programs which, along with the
editors ed and vi, implement a simple text
encryption system.
eoe2.sw.demos This is the standard SGI demonstration
package. It has been enhanced and
expanded with this release and features a
menu driven front end called
``buttonfly''. Some programs may not
image properly on machines with eight
bitplanes or without a Z buffer.
eoe2.sw.dfm This is a subset of IRIX utilities dealing
with directory and file management. It is
generally required in all systems.
eoe2.sw.editors This subsystem contains the standard IRIX
text editors and is generally required on
all systems.
eoe2.sw.envm This is the IRIX WorkSpace package, a
user-friendly alternative to the standard
IRIX command shell.
eoe2.sw.gltools This subsystem contains a collection of
simple tools that perform a variety of
graphics-related functions on a
workstation. Complete source code for
these tools is contained in the
dev.sw.giftssrc subsystem described in the
next section. These tools include:
blanktime imged mag
cedit icut mousewarp
clock imgexp savemap
dialwarp interp scrsave
gamcal ipaste showmap
gamma istat snapshot
ical loadmap textcolors
eoe2.sw.hyper This is the driver for the HyperNet VME
interface and is required only on systems
with that option installed.
eoe2.sw.ikc This is the driver for the VME Parallel
Expansion interface and is required only
by systems with that option installed.
eoe2.sw.ipc This subsystem contains utilities useful
in controlling the System V Inter Process
Communications facility. It consists of
two utilities: ipcrm and ipcs.
eoe2.sw.ipgate This subsystem contains additional network
routing daemons for machines with multiple
network interfaces (gateways). The gated
routing daemon supports RIP, EGP and HELLO
routing protocols. The mrouted allows
forwarding of IP multicast packets between
networks.
eoe2.sw.lp This subsystem contains the Line Printer
Spooling package and is required on any
system that will be used with printers,
either locally or over a network.
eoe2.sw.mast This subsystem contains vital graphics
software and is generally required on
workstations. On some systems, this
subsystem will be empty however.
eoe2.sw.moregltools This is an extension of the
eoe2.sw.gltools subsystem and contains
commands that implement simple image
processing functions. The complete source
to these commands is contained in the
def.sw.giftssrc subsystem described in the
next section.
eoe2.sw.optfonts These are additional fonts that are not
required by the base system but may be
desirable for some applications.
Boston NewCenturySchoolbook-Bold
Charter-Black NewCenturySchoolbook-BoldItalic
Charter-BlackItalic NewCenturySchoolbook-Italic
Charter-Italic NewCenturySchoolbook-Roman
Charter-Roman Symbol
Kanji
eoe2.sw.perf This subsystem contains the System
Activity Reporting (SAR) package. This
facility is useful for monitoring
processor activity and IRIX system
performance.
It may be used in either an interactive
mode or as a background data
collector/report generator. This
subsystem is not required, but may be
useful in diagnosing system performance
problems.
eoe2.sw.spaceball This subsystem provides IRISphere support.
eoe2.sw.spell This subsystem contains a dictionary and
command that checks spelling.
eoe2.sw.sysadm This is a system administration package
that does not require graphics and is
intended for use primarily on server
machines.
eoe2.sw.tcp This subsystem contains programs and files
that implement the TCP/IP family of
networking facilities. It is generally
required on all systems even if they will
be used in a stand-alone environment.
eoe2.sw.terminf This is the Terminfo terminal database.
It contains files describing the
capabilities of hundreds of different
types of terminals and is used by the vi
editor as well as many common terminal-
oriented applications. A few common
terminals may be used without this
subsystem.
eoe2.sw.ts This is the driver for the ISI VME
quarter-inch cartridge tape controller.
It is required on systems with that option
installed.
eoe2.sw.uds This subsystem contains support for 4.3BSD
UNIX domain sockets if you install
eoe2.sw.tcp. This subsystem is required
if you install the eoe2.sw.bsdlpr
subsystem.
eoe2.sw.usrenv This subsystem contains a subset of the
standard IRIX commands and is generally
required on all systems.
eoe2.sw.uucp This is the traditional UUCP
communications package which implements a
point-to-point networking facility. This
is only required for sites where UUCP is
used but it also contains facilities that
may be useful for systems with modems.
eoe2.sw.vadmin This is a graphical interface to the
standard IRIX administration utilities.
It provides user-friendly tools for
managing printers, users, disks, networks
and other common administrative function.
eoe2.sw.xm This is the driver for the Xylogics VME
1/2" tape controller and is required only
on systems with the controller installed.
eoe2.sw.xylsio This provides 16-port serial board
support.
eoe2.man.X11 This is an on-line version of the IRIX
User's Reference entries that describe the
commands in the eoe2.sw.X11 subsystem.
eoe2.man.bsdlpr These are man pages for the BSD lpd/lpr
line printer utilities.
eoe2.man.demos This is an on-line version of the IRIX
User's Reference, section 6, which
describes the demonstration programs.
eoe2.man.spaceball These are man pages that support the
IRISphere product.
3.3.0.3 Development_Option
dev.sw.G0libraries This subsystem contains versions of all
of the standard programming libraries
compiled with the
- - - -G G G G 0 0 0 0 option. These versions of the
libraries are generally not required.
dev.sw.NeWSimg This is an image database for the 4Sight
image demonstration programs.
dev.sw.bsdhdrs This subsystem contains symbolic links for
BSD header files formerly in
/usr/include/bsd. In Release 3.3, BSD
header files are in /usr/include. This
subsystem is needed if you are upgrading
from previous releases or you have source
code that include BSD headers with
explicit mention of the bsd subdirectory,
for example:
#include <bsd/foo.h>
dev.sw.cc This subsystem is contains all of the
standard IRIX commands and files for
compiling and debugging C programs.
dev.sw.cedgetut This contains files that accompany
documentation on how to use Edge, the IRIX
window-based debugger, when programming in
C.
dev.sw.crypt This subsystem contains the file
libcrypt.a for use by programs that
perform data encryption.
dev.sw.debug This contains the IRIX kernel debugger and
is useful only to those developing kernel
device drivers.
dev.sw.giftssrc This subsystem contains a multitude of
sample programs in source code form
including the source for all of the
eoe2.sw.gltools and eoe2.sw.moregltools
subsystems described in the previous
section. While the installation of this
subsystem is not required, many developers
have found the example programs to be
extremely useful in learning about the GL,
networking, and generic SCSI interfacing.
dev.sw.moredemos This is an extension of the eoe2.sw.demos
subsystem and contains more demonstration
programs. These programs are segregated
here due to disk space requirements.
dev.sw.rcs This contains the Revision Control System
(RCS) which is a set of programs that may
be used to control a source code
development project. With RCS, changes to
source files are kept in a database with
comments such that previous versions of a
particular file may be retrieved.
dev.sw.sccs This contains the Source Code Control
System which is identical in purpose
although different in use to RCS
(described above).
dev.man.cc This contains the IRIX Programmer's
Reference manual in an on-line readable
format.
3.4 Subsystem_Sizes
This is a list of all the subsystems and their sizes.
Default Install indicates subsystems that are are installed
by default when you install using automatic mode, or you
select default. To install subsystems that are not installed
by default, you must select them with manual installation
features. All sizes are in kilobytes.
___________________________________________________________________
subsystem Personal IRIS 4D Data Power Default
IRIS & Station Vision Install
Power
Series
__________________________________________________________________
eoe1.sw.unix 16248 15085 12081 11796 yes
eoe1.man.relnotes 185 185 185 185 yes
eoe1.man.unix 2234 2234 2234 2234 yes
__________________________________________________________________
TABLE 1. S4-EOE1-3.3
_____________________________________________________________________
subsystem Personal IRIS 4D Data Power Default
IRIS & Station Vision Install
Power
Series
____________________________________________________________________
eoe2.sw.NeWS 6565 6565 5949 6565 yes
eoe2.sw.X11 2192 2192 2192 2192 no
eoe2.sw.xapps 11602 11602 11602 11602 no
eoe2.sw.Xdemos 1444 1444 1444 1444 no
eoe2.sw.Xfonts 2368 2368 2368 2368 no
eoe2.sw.acct 468 468 468 468 no
eoe2.sw.bsdlpr 550 550 550 550 no
eoe2.sw.cdsio 23 23 0 0 yes
eoe2.sw.crypt 29 29 29 29 yes
eoe2.sw.demos 2385 2274 1385 2277 yes
eoe2.sw.dfm 499 499 499 499 yes
eoe2.sw.editors 385 385 385 385 yes
eoe2.sw.envm 3435 3435 3435 3435 yes
eoe2.sw.gltools 425 425 0 425 yes
eoe2.sw.hyper 99 99 99 99 no
eoe2.sw.ikc 15 15 0 0 yes
eoe2.sw.ipc 121 121 121 121 yes
eoe2.sw.ipgate 334 334 334 334 no
eoe2.sw.lp 759 759 759 759 yes
eoe2.sw.mast 0 490 0 1528 yes
eoe2.sw.moregltools 1307 1307 1307 1307 no
eoe2.sw.optfonts 2273 2273 2273 2273 no
eoe2.sw.perf 802 802 782 782 yes
eoe2.sw.spaceball 399 399 399 399 no
eoe2.sw.spell 433 433 433 433 no
eoe2.sw.sysadm 260 260 260 260 yes
eoe2.sw.tcp 4236 4236 4236 4236 yes
eoe2.sw.terminf 956 956 956 956 no
eoe2.sw.ts 15 15 15 15 no
eoe2.sw.uds 18 18 18 18 yes
eoe2.sw.usrenv 526 526 526 526 yes
eoe2.sw.uucp 1126 1126 1126 1126 no
eoe2.sw.vadmin 4425 4426 4426 4426 yes
eoe2.sw.xm 31 31 31 31 no
eoe2.sw.xylsio 28 28 0 0 no
eoe2.man.X11 563 563 563 563 no
eoe2.man.bsdlpr 23 23 23 23 no
eoe2.man.demos 164 164 164 164 yes
eoe2.man.spaceball 10 10 10 10 no
____________________________________________________________________
TABLE 2. S4-EOE2-3.3
____________________________________________________________________
subsystem Personal IRIS 4D Data Power Default
IRIS & Station Vision Install
Power
Series
___________________________________________________________________
dev.sw.G0libraries 5038 5038 3731 3731 no
dev.sw.NEWSimg 6360 6360 6360 6360 no
dev.sw.bsdhdrs 0 0 0 0 no
dev.sw.cc 10607 10619 9292 8995 yes
dev.sw.cedgetut 8 8 8 8 no
dev.sw.crypt 15 15 15 15 yes
dev.sw.debug 433 329 157 157 no
dev.sw.giftssrc 3548 3548 3548 3548 no
dev.sw.moredemos 3165 5675 2967 9634 no
dev.sw.rcs 839 839 839 839 no
dev.sw.sccs 845 845 845 845 no
dev.man.cc 2062 2062 2062 2062 yes
___________________________________________________________________
TABLE 3. S5-DV01-3.3
___________________________________________/No man is a failure who has friends
Trevor Paquette ICBM:51'03"N/114'05"W|I accept the challange, body and soul,
{ubc-cs,utai,alberta}!calgary!paquette|to seek the knowledge of the ones of old
paqu...@cpsc.ucalgary.ca | - engraved on the Kersa Blade of Esalon
Jesse Rendleman
you can to "pcat file.z | ul -t dumb > file.txt" to get a file
without the underlining stuff.