Concurrent Computer Corporation
PowerMAX 4.1M Release Notes
PowerMAX 4.1M Products are:
base_4.1m
================================================================================
================================================================================
Power Hawk PowerMAX OS*
Version 4.1m
Release Notes
Harris Computer Systems Corporation
1. Introduction
This document provides an overview of PowerMAX OSTM Release 4.1m.
PowerMAX OS is supported on a variety of hardware platforms including
the following:
o Night Hawk Series 6000 systems (models HN6200 and HN6800)
o PowerMAXION systems
o Power Hawk Model 610 & Model 620 systems
o Power Stack systems
PowerMAX OS Release 4.1m provides support for additional hardware
platforms but is functionally equivalent to Release 4.1. Release 4.1m
is provided only on the following systems:
o Power Hawk Model 610 & Model 620 systems
o Power Stack systems
(Note: Information applicable to Power Hawk is also applicable to
Power Stack unless otherwise noted.)
PowerMAX OS 4.1m is based on UNIXO System V Release 4.2 MP with real-
time enhancements provided by Concurrent Computer Corporation.
The PowerMAX OS release is distributed on multiple tapes. The Base
Installation tape contains standalone utilities, a bootable mini-
kernel, system installation software, file system restore utility, and
the base software package. The Additional Packages tape contains
optional software packages that may be installed once the base package
__________
* These release notes cover the following products: PowerMAX OS
- 1 -
Power Hawk PowerMAX OS 4.1m Release Notes
is installed.
2. Documentation
2.1 PowerMAX OS Software Documentation
The following table lists the available PowerMAX OS documentation.
Note that standalone release notes are available for the Night Hawk,
PowerMAXION and Power Hawk platforms. The corresponding release notes
will be provided with the applicable platform.
__________________________________________________________________
| Manual Name Pub. Number |
|__________________________________________________|______________|
| PowerMAX OS Programming Guide | 0890423-050 |
| Character User Interface Programming | 0890424-000 |
| Device Driver Programming | 0890425-050 |
| STREAMS Modules and Drivers | 0890426-010 |
| User's Guide | 0890428-010 |
| System Administration Volume 1 | 0890429-050 |
| System Administration Volume 2 | 0890430-050 |
| Power Hawk PowerMAX OS Version 4.1m Release Notes| 0891058-4.1m|
| Compilation Systems Volume 1 (Tools) | 0890459-040 |
| Compilation Systems Volume 2 (Concepts) | 0890460-040 |
| PowerMAX OS Real-Time Guide | 0890466-040 |
| PowerMAX OS Documentation Overview | 0890470-050 |
| PowerMAX OS Guide to Real-Time Services | 0890479-040 |
| Power Hawk 610/620 Console Reference Manual | 0830050-010 |
|__________________________________________________|______________|
Copies of the listed documentation can be ordered by contacting the
Concurrent Software Support Center. The toll-free number for calls
within the continental United States is 1-800-245-6453. For calls
outside the continental United States, the number is 1-954-971-6248.
Standalone product release notes are sometimes provided with software
products. The release notes you receive will be at the software
revision level that matches the associated software product level.
3. Software Prerequisites
None.
- 2 -
Release Notes 4.1m Power Hawk PowerMAX OS
4. Hardware Prerequisites
4.1 CPU
Note
The Power Hawk and Power Stack systems are basically similar. The Power Stack system
however does not have a VME backplane. Therefore, all references
to VME, VME devices, software applicable to VME, etc., do not apply
to the Power Stack system.
Single-board computer with minimum of 32MB of memory - Motorola
MVME1604-003, -004, -005 or MVME2604 (PowerPC 604) system.
4.2 SCSI Interface Controller
Minimum requirements are:
1. At least one of the following supported SCSI interface
controllers -
o Internal NCR 53C825 SCSI controller. This is built into the
MVME1604, MVME2604 or Power Stack CPU board.
o VME Interface Adapter (VIA), PN 1580009. Minimum Rev is -1.
2. At least one supported SCSI disk drive for system files and swap
space.
3. At least one supported SCSI tape device for software installation
and updates.
4.3 Disk/Tape Drives
Each system must have a system disk and tape drive. The smallest disk
drive supported for the installation disk (that contains the PowerMAX
OS executables) is 1GB. The installation disk must be on a VIA or an
internal SCSI (ncr) located on the processor board. At least one disk
or tape drive must be attached to the internal SCSI controller during
powerup to provide boot software (console). It is recommended that the
system disk be attached to the internal SCSI controller.
4.4 Ethernet Controllers
4.4.1 Internal_DEC_Ethernet_Controller
Ethernet may be provided with the on-board DEC 21040 or 21140 Ethernet
chip.
- 3 -
Power Hawk PowerMAX OS 4.1m Release Notes
4.4.2 PCI/PMC_DEC_Ethernet_Controller:
Additional networking connections are possible with selected PCI or
PMC based DEC 21040, 21140A, 21142 and 21143 controller chips.
Contact your Concurrent representative to determine if a particular
card is supported.
4.4.3 Interphase_4207_Eagle
VME-based Ethernet may be provided via the Interphase 4207 Eagle
Ethernet Controller. The minimum revision level of the ethernet
controller board (PN 2010221) is Rev E.
4.4.4 Interphase_4221_Condor
VME-based Ethernet may be provided via the Interphase 4221 Condor
Ethernet Controller. The minimum revision level of the ethernet
controller board (PN 2010316) is Rev A.
4.5 FDDI Controllers
4.5.1 Interphase_Peregrine_4211
VME-based FDDI is provided via the Interphase 4211 (Peregrine 1)
controller. The minimum revision level of the FDDI controller board
(PN 2010225) is Rev C.
4.5.2 Interphase_Peregrine_5211
VME-based FDDI is provided via the Interphase 5211 (Peregrine 2)
controller. The minimum revision level of the FDDI controller board
(PN 2010307) is Rev -.
4.6 HPS
VME-based asynchronous serial communications is provided by the High
Performance Serial (HPS) interface controller. The minimum revision
level of the HPS controller board (PN 2010218) is Rev D.
4.7 HSDE
VME-based HSD interface is provided by the High Speed Driver Enhanced
(HSDE) controller. The minimum revision level of the HSDE controller
board (PN 1573300) is Rev P.
- 4 -
Release Notes 4.1m Power Hawk PowerMAX OS
4.8 1553
VME-based MIL-STD-1553 Version 2 (V2) interface is provided by the
1553 controller. The minimum revision level of the 1553 controller
board (PN 2010209) is Rev C.
4.9 DR11-W
VME-based controller with a DEC DR11-W protocol external channel
interface. Up to 8 DR11-W boards are supported. The minimum revision
level of the DR11-W controller board (PN 2010179) is Rev -.
4.10 Parallel Printer Port
The parallel printer port is compatible with IEEE standard P1284, as
well as simple Centronics compatibility. The parallel port connector,
a 25-pin female DB connector, is located on the transition module for
chassis models, or on the rear connector panel on desktop models.
4.11 VDT Terminal
A wy150, vt100, or compatible terminal, is required to the run the
sysadm utility.
5. System Installation
The PowerMAX OS operating system is installed as software packages
using the Software Packaging Tools. Two installation modes, Custom
and Semi-Automatic, are now available. Refer to Section 5.3 for
additional details.
5.1 Software Packages
This section contains brief descriptions of available software
packages. Note that your complement of available software may be less
than that shown in Table 1 and entirely depends on the optional
software packages you purchased.
The availability of a software package for the various supported
platforms is shown in Table 1 by a "y" (yes) or "n" (no) in the
appropriate column.
Package dependencies are specified in the sixth column in Table 1.
Packages with dependencies must be installed after the packages they
depend on.
When installing the optional package(s) from the system installation
menu, you must also remember to select all required dependency
- 5 -
Power Hawk PowerMAX OS 4.1m Release Notes
package(s). The installation scripts will install the packages in the
proper order.
Some optional packages are relocatable, that is, objects may be
installed in an alternative directory other than root. When
installing a relocatable package, the user will be prompted for an
alternate installation path.
Note that all packages are dependent on base.
- 6 -
Release Notes 4.1m Power Hawk PowerMAX OS
Table 1. Software Packages
________________________________________________________________________________________
| | HN6200| Power| Powe| | Package |
| Package Description | HN6800| MAXIO| Hawk| Name | Dependencie|
|___________________________________________|_______|______|_____|_________|____________|
| Standard: | | | | | |
| Base System | y | y | y | base | |
| Printer Support | y | y | y | lp | |
| Network Support Utilities | y | y | y | nsu | |
| Terminfo Utilities | y | y | y | terminf | |
| Advanced Commands | y | y | y | cmds | lp, nsu |
| Program Analyzer | y | y | y | analyze | |
| Cross Compiling Libraries | y | y | y | crosslib| |
| Elan License Manager | y | y | y | elanlm | |
| Fortran Libraries | y | y | y | hf77libs| |
| OA&M | y | y | y | oam | cmds |
| Extended Backup and Restore | y | y | y | bkrs | oam |
| Software Packaging Tools | y | y | y | softint | |
| Kernel Debugger | y | y | y | kdb | |
| Domestic Encryption Utilities | y | y | y | crypt | |
| International Encryption Utilities | y | y | y | crypt-in| |
| Online Manual Pages | y | y | y | man | |
| Closed SARs | y | y | y | sar | |
|___________________________________________|_______|______|_____|_________|____________|
| Drivers: | | | | | |
| Condor Ethernet Driver | y | y | y | cnd | nsu |
| CD-ROM Driver | y | y | y | cdfs | |
| DR11W | y | y | y | dr11w | |
| Eagle Ethernet Driver | y | y | y | egl | nsu |
| High Performance Serial Driver(HPS) | y | y | y | hps | |
| HSDE | y | y | y | hsde | |
| Peregrine FDDI Driver | y | y | y | pg | nsu |
| X.25 Driver | y | y | y | ix25 | |
| 1553 V2 ABI Driver | y | y | y | 1553drv | |
| 1553 V2 ABI Libraries | y | y | y | 1533lib | 1553drv |
| Integral SCSI/Ethernet (ISE) | y | n | n | ise | |
| - ISE SCSI Driver | y | n | n | is | ise |
| - ISE Ethernet Driver | y | n | n | ie | ise,nsu |
| Internal NCR SCSI Driver | n | y | y | ncr | |
| Internal DEC Ethernet Driver | n | y | y | dec | nsu |
| MVME300 IEEE 488 | y | y | n | mvme300 | |
| VIA SCSI Adapter Driver | y | y | y | via | |
| Parallel Port Driver | n | n | y | lpt | lp |
| Multiplexer VMEbus Controller | y | y | n | mvc | |
|___________________________________________|_______|______|_____|_________|____________|
- 7 -
Power Hawk PowerMAX OS 4.1m Release Notes
Table 1. Software Packages (Cont.)
_______________________________________________________________________________________________
| | HN6200| Power| Powe| | Package |
| Package Description | HN6800| MAXIO| Hawk| Name | Dependencies |
|________________________________________|_______|______|_____|_________|______________________|
| TCP/IP Networking: | | | | | |
| Internet Utilities | y | y | y | inet | nsu |
| Commands Networking Extension | y | y | y | netcmds | lp, inet |
| Remote Procedure Calls Utilities | y | y | y | rpc | inet |
|________________________________________|_______|______|_____|_________|______________________|
| Network File System: | | | | | |
| Network File System Utilities | y | y | y | nfs | nsu, inet, rpc, dfs |
| Distributed File System Utilities | y | y | y | dfs | inet |
|________________________________________|_______|______|_____|_________|______________________|
| Security: | | | | | |
| Auditing | y | y | y | audit | |
|________________________________________|_______|______|_____|_________|______________________|
| Loosely-Coupled System: | | | | | |
| Cluster | n | n | y | cluster | netcmds, nfs, dec, x1|
| | | | | | and ncr or via |
|________________________________________|_______|______|_____|_________|______________________|
| Frequency-Based Scheduler: | | | | | |
| Frequency-Based Scheduler and | | | | | |
| Performance Monitor | y | y | y | fbs | |
| Frequency-Based Scheduler Manual Page| y | y | y | fbsman | |
|________________________________________|_______|______|_____|_________|______________________|
| Software Development: | | | | | |
| Concurrent C Compilation System | y | y | y | hc | analyze |
| Fortran 77 Compilation System | y | y | y | hf77 | analyze |
| cfront C++ Language System | y | y | y | cfront | analyze, hc |
| Ada Programming Support | | | | | |
| Environment (HAPSE) | y | y | y | ada | analyze |
| Ada X Interface (AXI) | y | y | y | axi | ada, x11 |
| Ada Runtime Shared-Libraries | y | y | y | ada_rts | |
|________________________________________|_______|______|_____|_________|______________________|
| Window System: | | | | | |
| X Window System with OSF/Motif | y | y | y | x11 | nsu |
|________________________________________|_______|______|_____|_________|______________________|
| NightStar Tools: | | | | | |
| NightProbe | y | y | y | nprobe | elanlm, x11 |
| NightSim | y | y | y | nsim | elanlm, x11 |
| NightTrace | y | y | y | ntrace | elanlm, x11 |
| NightTune | y | y | y | ntune | elanlm, x11 |
| NightView | y | y | y | NightVie| elanlm, x11 |
|________________________________________|_______|______|_____|_________|______________________|
| Miscellaneous: | | | | | |
|________________________________________|_______|______|_____|_________|______________________|
- 8 -
Release Notes 4.1m Power Hawk PowerMAX OS
| Virtual Partition | y | y | y | vp | |
| VERITAS Volume Manager | y | y | y | vxvm | nsu |
|________________________________________|_______|______|_____|_________|______________________|
The following pages contain a brief description of all of the packages
available on PowerMAX OS. Refer to Table 1 above to determine if the
package listed is applicable to your system.
- 9 -
Power Hawk PowerMAX OS 4.1m Release Notes
Description of Standard Packages:
Base System (base)
The Base System package provides the base set of
commands and system utilities.
Printer Support (lp)
Although some printing capabilities are provided in the
base package, more advanced printing capabilities, and
a wider range of printers, are included in the Printer
Support package.
Network Support Utilities (nsu)
The Network Support Utilities package provides the
basis on which networking capabilities are built.
Terminfo Utilities (terminf)
The Terminfo Utilities Package provides support for a
wide variety of terminals beyond those provided in the
base package.
Advanced Commands (cmds)
The Advanced Commands package provides the remaining
user and administrative commands.
Program Analyzer (analyze)
This package provides utilities for performance
analysis and post-linker optimization.
Cross Compiling Libraries (crosslibs)
Libraries for cross-compilation between architecture
types, i.e., between the Night Hawk architecture
(HN6200/HN6800/PowerMAXION) and the Motorola
architecture (Power Hawk/Power Stack). Libraries can
be found in /usr/lib/crosslibs. Each architecture type
contains the other's libraries.
Elan License Manager (elanlm)
This package contains the license manager daemon and
reporting commands required by license-managed
applications, including all NightStar tools.
hf77libs (hf77libs)
This package provides runtime libraries for the Fortran
77 Compilation System.
OA&M (oam)
The Operations Administration and Maintenance package
provides a character-based, menu-oriented interface to
- 10 -
Release Notes 4.1m Power Hawk PowerMAX OS
a wide variety of advanced, server-oriented
administrative tasks.
Extended Backup and Restore (bkrs)
The Extended Backup and Restore Package includes a
flexible set of backup and restore utilities.
Software Packaging Tools (softint)
This package provides tools to support the development
process and includes a variety of archive libraries as
well as tools to create and modify packages.
Kernel Debugger (kdb)
The Kernel Debugger package provides a tool to assist
in the porting and debugging of kernel modules and
drivers by allowing the developer to examine and
control a running kernel.
Domestic Encryption Utilities (crypt)
The domestic Encryption Utilities package supports the
encryption of files and other data. This package is
for distribution in the United States.
International Encryption Utilities (crypt-int)
Same as above but for international distribution.
Online Manual Pages (man)
System manual pages (man pages) provided in an on-line
format for viewing using the man command.
Closed SARs (sar)
Software Action Reports (SARs) closed in this release
can be found in file /usr/src/PRODUCTS/SARS.CLOSED.
Description of Drivers Packages:
Eagle Ethernet Driver (egl)
This package supports the Interphase Ethernet 4207
Eagle VME board. Up to 6 Eagle Ethernet boards are
supported.
Condor Ethernet Driver (cnd)
This package supports the Condor Ethernet 4211 VME
board. Up to 6 Condor Ethernet boards are supported.
CD-ROM Driver (cdfs)
The CD-ROM package provides read-only access to file
systems on SCSI CD-ROM devices. ISO-9660 and High
Sierra formats are supported.
- 11 -
Power Hawk PowerMAX OS 4.1m Release Notes
Parallel Port Driver (lpt)
This driver package supports the parallel port on the
Power Hawk. Only one parallel port is supported per
system. This driver supports local printing to a
directly connected printer.
Peregrine FDDI Driver (pg)
This package supports the Interphase FDDI 4211 and 5211
Peregrine VME boards. Up to 3 Peregrine VME boards are
supported.
High Performance Serial Driver (hps)
This package supports the High Performance Serial
adapter, a VME board providing 16 asynchronous serial
ports running up to 38400 baud, and 1 optional
Centronics parallel printer port. Up to eight HPS
adapters are supported.
VIA SCSI Adapter Driver (via)
This driver package supports the following:
a. SCSI Adapter Interface (hsa), an HVME board
providing mass storage capability to the system. Up
to 7 Concurrent specified SCSI disks or tapes may be
connected to a single HSA board. HSA boards are
available only on HN6200 and HN6800 Night Hawks.
b. VME Interface Adapter for SCSI (via), a VME board
providing mass storage capability to the system. Up
to 30 (if using 16-bit wide SCSI) Concurrent
specified SCSI disks or tapes may be connected to a
single VIA board. The VIA board supports up to two
optional daughter cards. Each daughter card can be
one of the following:
1. SCSI-2 card that supports fast and wide single
ended SCSI-2 transfers.
2. SCSI-2 differential card that supports fast and
wide transfers.
Refer to online manual page dlvia(8) for information on
how to download VIA-board firmware.
Internal NCR 53C8xx SCSI Driver (ncr)
This driver package supports the internal SCSI
controller chip on the PowerMAXION, Power Stack and
Power Hawk processor cards along with NCR53C8xx PCI
SCSI controller chips on separate PMC or PCI cards.
Supported controllers include the 53C810, 53C825,
53C825A and 53C875. This package also provides for
automatic configuration of the controller during system
- 12 -
Release Notes 4.1m Power Hawk PowerMAX OS
initialization (e.g., no Sadapters(4) file changes
required).
Up to seven disks and/or tape drives may be connected
to this internal SCSI bus.
Internal DEC 21x4x Ethernet Driver (dec)
This driver package supports the internal Ethernet
controller chip on the PowerMAXION and Power Hawk
processor cards along with DEC 21x4x controller chips
on separate PMC or PCI cards. Supported chips include
the 21040, 21140A, 21142 and 21143. This package also
provides for automatic configuration of the controller
during system initialization (e.g., no Sadapters(4)
file changes required).
100baseT (except on the 21040), 10baseT, BNC and AUI
connections are supported. The Power Hawk Model 610
processor card uses the 10baseT 21040 while the Power
Hawk Model 620 processor contains a 21140A with 10baseT
or 100baseT connections.
High Speed Data Enhanced Channel Driver (hsde)
This package supports the HSDE Channel Interface. The
HSDE provides high-speed, 32-bit parallel bidirectional
link for transferring control, status and data between
the HN6200/HN6800 (H)VMEbus system and an external
device using the Encore HSD Interface Model 9132
protocol.
1553 V2 ABI Driver (1553drv)
This package provides a user-level device driver for
the Version 2 (V2) Advanced Bus Interface (ABI) MIL-
STD-1553 Adapter.
1553 V2 ABI Libraries (1553lib)
This package provides program interfaces that can be
used within an application program. This interface is
the same as those provided by the manufacturer of the
1553 board, SBS Engineering, Inc.
Motorola MVME300 IEEE488 Interface Driver (mvme300)
This package supports the Motorola's MVME300 IEEE 488
bus interface controller. Up to 8 MVME300 controllers
are supported.
Ikon DR11W Driver (dr11w)
This package supports the Ikon 10089 DR11W emulator
board. Up to 16 DR11W boards are supported (8 in the
- 13 -
Power Hawk PowerMAX OS 4.1m Release Notes
Primary I/O bus, 8 in the Secondary I/O bus).
Integral SCSI/Ethernet Controller (ise)
Provides base support for the Integral SCSI/Ethernet
daughtercards (ISE) available with Night Hawk systems.
This package supports up to four ISE cards (one per
processor board), and provides for automatic
configuration of ISE cards during system initialization
(e.g., no Sadapters(4) file changes required).
ISE - SCSI (is)
Provides driver support for up to seven SCSI
peripherals for each configured ISE daughtercard.
ISE - Ethernet (ie)
Provides Ethernet/IEEE 802.3 local area network
driver support for each configured ISE
daughtercard.
X.25 Driver (ix25)
This package supports the X.25 high speed synchronous
communication module that runs X.25/LAPB/HDLC.
Multiplexer VMEbus Controller (mvc)
This package supports the Multiplexer VMEbus Controller
(MVC) adapter board. The MVC adapter board provides 16
asynchronous serial ports running at up to 38.4 baud,
and one optional Centronic parallel printer port. Up to
two MVC adapter boards are supported.
Description of TCP/IP Networking Packages:
Internet Utilities (inet)
The inet package includes the software needed to run
the TCP/IP network and tools such as ftp, telnet, and
rcp. Administrative software for setting up the
network is also included.
Commands Networking Extension (netcmds)
The Commands Networking Extension Package extends the
functionality of several basic commands by supporting
the means to share printers across a network, and use
additional transport mechanisms for the sending and
receiving of electronic mail.
Remote Procedure Calls Utilities (rpc)
The Remote Procedure Calls Utilities package supports
the remote execution facility.
- 14 -
Release Notes 4.1m Power Hawk PowerMAX OS
Description of Network File System Packages:
Network File System Utilities (nfs)
The Network File System Utilities package supports the
means to transparently share resources across a network
with other computers running the Network File System.
Distributed File System Utilities (dfs)
The dfs utilities package provides a simple user
interface for performing networked operations such as
advertising local resources and accessing remote
resources.
Description of Security Package:
Auditing (audit)
The Auditing package provides auditing facilities
allowing a system administrator or security auditor to
record and report all security-related events that
occur on the system.
Description of Loosely-Coupled System:
Cluster (cluster)
The cluster package provides support to configure and
control multiple Motorola MVME1604 and MVME2604
single-board computers (SBC) in a common VME chassis
using the VMEbus as a point-to-point network interface.
Additionally, this package can support multiple SBC in
one, or more, remote VME chassis connected via
Ethernet. Diskless SBC's can be booted via the VMEbus,
or can boot itself via NET BOOT (boot via TFTP over
Ethernet).
Description of Frequency-Based Scheduler Packages:
Frequency-Based Scheduler and Performance Monitor (fbs)
This package provides kernel support for the
Frequency-Based Scheduler and Performance Monitor and
Real-Time Command Processor.
Frequency Based Scheduler Manual Pages (fbsman)
This package provides the man pages associated with the
Frequency-Based Scheduler and Performance Monitor.
Description of Software Development Package:
- 15 -
Power Hawk PowerMAX OS 4.1m Release Notes
Concurrent C Compilation System (hc)
This package provides the hc C compiler. This compiler
offers ANSI C compliance and support for pre-ANSI C,
together with other extensions.
Fortran 77 Compilation System (hf77)
This package provides the hf77 Fortran compiler and
runtime libraries. This compilation system offers
Fortran 77 and MIL-STD 1753 compliance, together with
many popular extensions and a cross-reference tool with
interface checking.
C++ Language System (cfront)
This package provides Novell's cfront 3.0.1 C++
language system. This language system comes with the
cfront translator and the stream and complex runtime
libraries.
Ada Programming Support Environment (ada)
This package consists of a validated Ada compiler,
library, management tools, symbolic debugger, automated
build utility, Ada bindings, real-time monitoring, the
Ada Real-Time Multiprocessor tasking executive (ARMS)
and runtime support libraries.
Ada to X Interface (AXI) (axi)
This package consists of the Ada to X Window system
interface.
Ada Runtime Shared-Libraries (ada_rts)
This package consists of the compiled and linked form
of HAPSE Runtime Shared-Libraries; including the basic
Ada Real-Time Multiprocessor System (ARMS) standard
libraries, Ada bindings, and others.
Description of X Window System Package:
X Window System Version 11, Release 5 (x11)
Includes OSF/Motif (Version 1.2.5), commands, libraries
and header files.
Description of NightStar Tools Packages:
NightProbe (nprobe)
This package provides a utility for monitoring and
recording data values in one or more target programs.
NightSim (nsim)
This package provides a utility to control and monitor
- 16 -
Release Notes 4.1m Power Hawk PowerMAX OS
the Frequency-Based Scheduler and its Performance
Monitor.
NightTrace (ntrace)
This package provides a utility with a graphical
interface to trace events occurring in the kernel and
optionally within a user's application.
NightTune (ntune)
This package provides a utility with a graphical
interface to monitor and tune a system.
NightView (NightView)
This package provides a general-purpose, source-level
debugger for C, C++, Fortran and Ada with support for
multiple processes.
Description of Miscellaneous Packages:
Virtual Partition (vp)
This package provides a pseudo device driver that
supports RAID level 0, or disk striping.
VERITAS Volume Manager (vxvm)
This package provides the system administrator with a
disk management tool. See section 5.2 below on how
disk must be configured when using the VERITAS Volume
Manager.
- 17 -
Power Hawk PowerMAX OS 4.1m Release Notes
5.2 System Disk Configuration
The following system disk configuration is suggested for installing
the system using an ufs root file system type:
ufs root file system
_________|______|______________
| | minimum size
partition| file| (formatted)
_________|______|______________
0 | root| 75 MB
1 | swap| 96 MB
2 | usr | 350 MB
3 | var | 200 MB
4 | --- | <remainder>
61 | boot| 1024 KB
_________|______|______________
The following system disk configuration is suggested for installing
the system using an xfs root file system type:
xfs root file system
_________|_______|______________
| | minimum size
partition| file | (formatted)
_________|_______|______________
0 | stand| 40 MB
1 | swap | 96 MB
2 | usr | 350 MB
3 | var | 200 MB
4 | --- | <remainder>
52 | root | 50 MB
61 | boot | 1024 KB
_________|_______|______________
1. Partition is applicable to Power Hawk and Power Stack boot
disks only.
2. The xfs root must be on partition 5. (Caution: cannot use
VxVM with xfs root file system.)
During system installation, you will be given the option of running
the format(1M) command. You should choose this option to format the
system disk and to select partition sizes.
The format(1M) command "partition default" automatically selects the
above partition sizes for a ufs root file system.
- 18 -
Release Notes 4.1m Power Hawk PowerMAX OS
Note that the format(1M) "partition default" option should not be used
if an xfs root file system is selected as the default partitions
automatically selected are not appropriate for the xfs file system.
Partition sizes may be increased and new partitions may be added, but
the above assignments of file systems to partitions and minimum
partition sizes must be maintained.
The root and usr file systems should only contain system files and are
not expected to grow much after system installation. The var file
system contains system crashfiles, log(s) and temporary files. It is
strongly recommended that user files be restricted from these file
systems.
The total amount of swap space should be at least 1.5 times the size
of physical memory. An initial swap partition is provided on the
system disk. If this partition is insufficient, it is recommended
that additional swap partitions be added, preferably on other disks.
Note that partition four is left unused. This partition may be:
1. Redistributed to make the other system partitions bigger.
2. Used for additional swap space.
3. Used for user files (for example a home file system).
Use the format(1M) "?" command for help with format commands. Refer
to the format(1M) manual page in Appendix A for details.
Note that non-system disks will need to be initialized once the system
is re-booted for new disk. This includes running format(1M) to format
and partition the disk and newfs(1M) to initialize the file systems.
Additional steps include creating a mount point directory, adding the
appropriate information to /etc/vfstab and adding new entries to the
Device Database (DDB). See the System Administration Manual for
information on disk formatting and partitioning.
Note: All disks, including the system disk, that are to be used by
the VERITAS Volume Manager (VxVM) package have special configuration
requirements. Note however that Power Hawk boot disks cannot be used
by VxVM. These configuration requirements are listed below.
1. Partition 5 must be left unused, and configured with a size of
zero. (Cannot use VxVM with xfs root file system.)
2. Partition 6 must be configured with a size of 512K bytes (1024
sectors).
- 19 -
Power Hawk PowerMAX OS 4.1m Release Notes
Partitions 5 and 6 are used exclusively by VxVM and cannot be used by
users or the system for other uses. If partitions 5 and 6 are not
configured as described, then the disk cannot be used by VxVM.
Use the format(1M) command to format the disks to the specifications
described above if VxVM is to be used.
5.3 Installation Modes
Early in the system installation, the operator will be asked whether
to perform a custom or semi-automatic system installation. A
description of each mode is provided in the following paragraphs.
5.3.1 Custom_Mode_of_Installation
In custom mode, the operator is prompted during the installation in
order to specify the values for configurable items. Custom mode is
recommended if the pre-determined values assigned in the semi-
automatic mode are not appropriate for your site, and/or, you want the
option of installing only certain packages during system installation.
5.3.2 Semi-Automatic_Mode_of_Installation
In semi-automatic mode, the operator still specifies the basic
configuration of the system however, the remainder of the installation
is done with a pre-determined set of responses. Note that in semi-
automatic mode, all the additional products on the tape are
automatically installed. The operator does not have the option of
installing only specific packages.
Refer to Table 2 for a description of the configurable items and the
values that they will be assigned on a semi-automatic installation.
Semi-automatic mode can be used if the configurable values are set
appropriately for the given site and all packages are being installed.
Otherwise, custom mode should be used.
Note: Refer to Table 1 to determine if a given package listed in Table
2 is applicable to your particular system.
- 20 -
Release Notes 4.1m Power Hawk PowerMAX OS
Table 2. Assigned Installation Values Under Semi-Automatic Mode
________________________________________________________________________________________________
Package
Name Configurable Item Automatic Installation Value
________________________________________________________________________________________________
base Host nodename Obtained during initial installation.
Root password "" (null password)
License key - number of users Automatically configured.
License key - number of processors Automatically configured.
________________________________________________________________________________________________
nsu Number of pseudo terminals 64
________________________________________________________________________________________________
elanlm Install man pages ? yes
Start license manager during system boot ? yes
________________________________________________________________________________________________
oam sysadm password "" (null password)
________________________________________________________________________________________________
cnd Number of cnd adapters on primary VME bus 1
Number of cnd adapters on secondary VME bus 0
________________________________________________________________________________________________
dr11w Number of dr11w adapters on primary VME bus 1
Number of dr11w adapters on secondary VME bus 0
________________________________________________________________________________________________
egl Number of egl adapters on primary VME bus 1
Number of egl adapters on secondary VME bus 0
________________________________________________________________________________________________
hps Number of hps adapters on primary VME bus 1
Number of hps adapters on secondary VME bus 0
Configure realtime driver ? no
________________________________________________________________________________________________
hsde Number of hsde adapters on primary VME bus 1
Number of hsde adapters on secondary VME bus 0
________________________________________________________________________________________________
pg Number of pg adapters on primary VME bus 1
Number of pg adapters on secondary VME bus 0
________________________________________________________________________________________________
ix25 Number of ix25 adapters on primary VME bus 1
Number of ix25 adapters on secondary VME bus 0
Install man pages ? yes
________________________________________________________________________________________________
1553drv Number of 1553-ABI adapters 1
________________________________________________________________________________________________
mvme300 Number of mvme300 adapters 1
________________________________________________________________________________________________
inet Configure TCP listener ? yes
Install OAM forms and menus ? yes
- 21 -
Power Hawk PowerMAX OS 4.1m Release Notes
________________________________________________________________________________________________
nfs Install OAM forms and menus ? yes
________________________________________________________________________________________________
ada Install directory for HAPSE standard location relative
to root directory
________________________________________________________________________________________________
x11 Install header files and static libraries ? yes
Install man pages ? yes
Start xdm during system boot ? yes
________________________________________________________________________________________________
(continued)
- 22 -
Release Notes 4.1m Power Hawk PowerMAX OS
Table 2. Assigned Installation Values Under Semi-Automatic Mode
(Cont)
____________________________________________________________________________________
Package Name Configurable Item Automatic Installation Value
____________________________________________________________________________________
nprobe Install directory for NightProbe standard location relative
to root directory
____________________________________________________________________________________
nsim Install directory for NightSim standard location relative
to root directory
____________________________________________________________________________________
ntrace Install directory for NightTrace standard location relative
to root directory
____________________________________________________________________________________
ntune Install directory for NightTune standard location relative
to root directory
____________________________________________________________________________________
NightView Install directory for NightView standard location relative
to root directory
____________________________________________________________________________________
vxvm Install OAM forms and menus ? yes
____________________________________________________________________________________
5.4 Installation Procedure
First the resident console must be loaded off of the distribution
media. This must be done using the Motorola ppcbug product. ppcbug
is the resident debug/self-test program initially loaded when the
Power Hawk hardware is reset. Additional information about ppcbug may
be found in the Motorola document, PPCBUG Firmware Package User's
Manual. Depending on the firmware setup, ppcbug may attempt to auto-
boot or may just go to a debug prompt. If it attempts to auto-boot,
depress the Escape (ESC) key until the PPC1-BUG> prompt is received at
the system console.
The ppcbug "pboot" command is used to load the console off of the
distribution media. This must be done on a tape drive connected to
the internal SCSI controller, as ppcbug is not capable of
communicating with VME controllers. Place the Base Installation Tape
into the tape drive and execute the following:
PPC1-BUG> pboot 0,x0
where x is the SCSI ID of the selected tape drive.
The console is copied to the target disk during the installation
procedure. Once this has been done the console can be loaded from
that disk without having to load it from tape each time. Once the
console is loaded, it will enter the "halt" state and the installation
- 23 -
Power Hawk PowerMAX OS 4.1m Release Notes
may be continued.
To begin system installation on a halted system, insert the Base
Installation Tape and execute the following console commands: (where
d = is the logical tape drive designation of drive containing the
Base Installation Tape. This number is found from the output of the
"fd -l" command.)
#> fd -l
..............
fd disk tape
0 (0,0,x,0) FUJITSU M2624S-512 (0,5,x,0) ARCHIVE VIPER 150 21247
1 (2,0,x,1) FUJITSU M2624F-512
#> p boot 0
#> fd mt(0,1)
#> fb
These commands will boot /stand/unix from tape. The time to complete
the entire installation will vary depending on the packages selected
to be installed and the type of tape drive being used.
As the system is brought up, the initial menu will prompt you to
choose either the system software installation program or the file
system restore program. At this prompt, choose submenu 1 INSTALL. (The
file system restore program is documented in chapter 10 of the System
Administration Volume 2.) Prompts that require user input are
preceded by =>. Most prompts have defaults in parentheses that may be
selected by pressing the "Enter" key. At any prompt, "?" can be
entered for help or "q" to quit installation. If the user selects to
quit installation or if a fatal error occurs, installation will be
suspended by executing a sub-shell. When exiting the shell, the last
operation of the installation procedure will be repeated and
installation will continue. Typing ". restart" from the shell will
restart the installation procedure from the beginning.
The installation is self-guiding, but the following configuration
information is required from the user:
o Installation Mode (choose custom or semi-automatic (see Section
5.3))
o Node name
o Timezone
o Time/Date
o Desired file system types
o System disk location (slot and unit number)
o Tape drive location (if more than one drive in system)
- 24 -
Release Notes 4.1m Power Hawk PowerMAX OS
o System disk configuration (see Section 5.2)
Following are applicable to custom mode installation only:
o Which additional software packages should be installed (see
Section 5.1)
o Configuration information requested by the various packages
o If appropriate, any kernel modules from the optional packages you
want to deconfigure (that is, not link with the kernel)
Note: The installation tapes are accessed at various times and must be
kept in the drive during the installation until you are instructed to
install a different tape.
After all the packages have been installed, you will be given an
opportunity, if in the custom installation mode, to deconfigure kernel
modules from optional packages. When deconfigured, those drivers will
not be linked with the kernel. Note that you must consider package
dependencies when deconfiguring drivers. See Table 1, Software
Packages, for package dependency relationships.
At the end of the installation procedure, a kernel for the newly
installed system will be built.
5.5 Standalone Utilities
The standalone commands are shipped on the Base Installation Tape as
diagnostic aids. These are not required for installation.
The following standalone commands are available:
ls(8), format(8), cat(8), fastcopy(8), dlvia(8)
To run the standalone commands, execute the following commands from
the console terminal. (where d = is the logical tape drive
designation (typically 0), The "1" means that the second partition on
tape contains the bootable kernel, and cmd = command to be loaded)
#> p boot 1
#> fd mt(d,1)
#> fb
Boot
: [cmd]
5.6 Installing Additional Packages
All software packages provided on the Additional Packages tape may be
installed during the installation procedure described in Section 5.4
above. However, you may delay installation of various packages until
after a basic system configuration is installed.
- 25 -
Power Hawk PowerMAX OS 4.1m Release Notes
To install additional packages on an installed system, use the
pkgadd(1M) command. pkgadd(1M) requires that a tape device entry be
added in the Device Database with the putdev(1M) command.
Refer to the pkgadd(1M) man page in Appendix A for more details. In
addition, refer to the chapter entitled "Installing Add-On Software"
in the System Administration Manual Volume 1 (Pubs No. 0890429).
Refer to the putdev(1M) man page in Appendix A for more details. In
addition, refer to the chapter entitled "The Device Database: Adding
and Removing Storage Devices" in the System Administration Manual
Volume 2 (Pubs No. 0890430).
The following example installs the "nsu" package from a tape device
named "tape1":
putdev -a tape1 volume="cartridge tape" cdevice=/dev/rmt/0hf \
desc="tape drive 1" type=ctape
pkgadd -qld tape1 nsu
Multiple packages may be installed at once by specifying more than one
package name, as in:
pkgadd -qld tape1 nsu lp cmds
The package(s) to install may be selected from a menu of all packages
available on the tape by not specifying any package name, as in:
pkgadd -qld tape1
6. Rebooting The System
During the installation, a new kernel is generated. When the system
installation completes, the system first halts and then returns to
console mode.
1. If a kernel was successfully built during the system
installation, execute the following commands from the console:
(where d = is the logical disk drive designation)
#> p boot 0
#> fd dsk(d)
#> fb
2. If the kernel build fails during the installation,
/stand/unix.generic is copied to /stand/unix. You may use this
generic kernel to boot to single-user mode, build a new kernel
- 26 -
Release Notes 4.1m Power Hawk PowerMAX OS
and reboot. Because the generic kernel was not built using your
site's specific configuration, you should not come up in multi-
user mode with the generic kernel. To boot from a generic
kernel, execute the following commands from the console: (where d
= is the logical disk drive designation)
#> p boot 2
#> fd dsk(d)
#> fb
Remain in single-user mode by entering the root password when
prompted. Then execute the following commands:
#> fsck -y /dev/rusr
#> mount /dev/usr
#> /etc/conf/bin/idbuild -B
After you have successfully built a kernel, you can bring the
system down by executing the command init 0. The system
shutdown/reboot sequence takes care of moving the newly built
unix to /stand/unix. Then follow the procedure in step 1 above
on how to boot a newly installed system.
For information on configuring and building a kernel, refer to
the "Configuring and Building a Kernel" chapter in the System
Administration Manual Volume 2, (Pubs No. 0890430).
See the following paragraph pertaining to xfs root file system
and the use of "non-standard" kernel names in /stand.
6.1 Note Pertaining to XFS
If a new kernel is installed in /stand with a non-standard name then a
hard link needs to be created. An explanation for this requirement is
provided in the following paragraph.
The boot program boots kernels from the file system on partition 0,
which it assumes to be of type ufs (or sfs). If this file system is
also the root, then by convention the kernels are held in directory
/stand within the root. However, if the root is xfs (partition 5), the
ufs file system containing the kernels (and standalones) is mounted on
/stand, which in this case is a directory in the xfs root. Using hard
links to the directory /stand/stand ensures that the conventional boot
path can be used.
Note
It is important to point out to the system administrator that if
kernels with names other than "unix" are copied to /stand on a
system with an xfs root, they should be given hard links of the
same name in /stand/stand. This will ensure that they can be
booted using the conventional path "/stand/unix.xxx". If this link
is missing, they can only be booted using "/unix.xxx".
- 27 -
Power Hawk PowerMAX OS 4.1m Release Notes
7. Features Ported From MAXION/OS
Release 4.1m of PowerMAX OS has incorporated features from MAXION/OS
for the added real-time functionality that these features provide and
also, to provide a migration path for users currently hosting their
software on the MAXION architecture. The following features from
MAXION/OS are provided in this release in a source compatible manner.
This means that programs which incorporate these features can be
ported to PowerMAX OS by simply recompiling the program. For more
details on these interfaces refer to Section 8.
o Resilient File System (xfs)
o Exclusive Binding
o STREAMS Enhancements
o Virtual Interrupt System (VIS)
o BSD 4.3 libraries
o setrun(1) command
o mload(1) command
o mview(1) command
o metreg(1) command
o POSIX Thread support
In addition, the newly-released NightTune tool is a port of the
MAXION/OS Performance Tuner product. This tool allows MAXION
programmers a familiar interface for tuning their application. Refer
to the NightTune Quick Reference manual (Pubs No. 0890515) for further
information.
- 28 -
Release Notes 4.1m Power Hawk PowerMAX OS
8. Changes From Previous Release
8.1 Operating System
8.1.1 Architecture_Unification
As the number of hardware platforms on which PowerMAX OS operates
continues to grow, an enhancement to simplify configuration and
installation on selected systems has been implemented. In Release
4.1m this includes Power Hawk 610, Power Hawk 620 and Power Stack
systems. Future releases may support additional architectures.
On these systems, a new configurable module, the Board Support
Package, or 'bsp' has been introduced. In Release 4.1m, Board Support
Packages are provided as bsp1600 for the Power Hawk Model 610, bsp2600
for the Power Hawk Model 620 and bsppstk for the Power Stack. A
bspall package is also available which is used primarily for system
installation.
The system installation scripts will automatically turn on the
appropriate module (bsp1600, bsp2600 or bsppstk) based upon the type
of hardware on which the system is being installed. It is also
possible to manually select one and only one bspxxxx module and relink
a kernel which is appropriate for that particular hardware type. The
bspall module should not normally be used, but if used a kernel which
is larger, slower and can operate on all architectures will be
produced. types.
Similarly, libraries and commands which contain platform-specific code
(for example the intstat(1m) command) will now auto-detect the current
hardware and thus operate on all architecture types.
8.1.2 VIA_Configuration
Configuration of the VIA and HSA SCSI adapters has been simplified.
Previous releases had two different packages depending on system type.
In PowerMAX OS Release 4.1m, the via package must be present on the
system for both HSA and VIA SCSI adapters. There is no longer an hsa
package.
Configuration lines in the /etc/conf/sadapters.d/kernel file may
specify either hsa or via as appropriate for the type of hardware on
- 29 -
Power Hawk PowerMAX OS 4.1m Release Notes
the system.
8.1.3 Resilient_File_System_(xfs)
The Resilient File System (xfs) type is added in this release.
The xfs file system has the following features not available in the
ufs file systems:
o fast file system recovery following a system crash without use of
fsck
o extent sizes (up to 1024 KB) determined by size of first write,
or by mkfs option
o POSIX Real-Time extensions including support for contiguous files
and file advisories
o increase in maximum allowable file system size from 2 GB to 1000
GB
o prioritized I/O selectable at mount time
File system dump and restore utilities (xfsdump(1m) and
xfsrestore(1m)) were added in this release to support xfs file
systems.
Support for xfs file systems was also added to the installation tape's
File System Restore Utility.
For more information on the xfs file system, dump and restore
utilities, etc., refer to the System Administration Volume 2 (Pubs No.
0890430). Also refer to manual pages xfsdump(1m) and xfsrestore(1m)
for additional information on the dump and restore utilities.
8.1.4 Loosely-Coupled_Systems
The Loosely-Coupled Systems (LCS) software provides software support
to configure, boot-load, and control multiple Motorola MVME1604 or
MVME2604 single-board computers (SBCs) using a OSF/Motif configuration
and control utility. The LCS software has the following features:
o A simple OSF/Motif Graphical User Interface (GUI), clusterconfig,
is used to configure, boot load, and control all SBCs in a LCS.
o Only one SBC needs to have a serial console terminal and disk
attached (referred to as the host SBC). The other SBCs do not
require console terminal or disk drive (referred to as the target
SBCs).
- 30 -
Release Notes 4.1m Power Hawk PowerMAX OS
o Each SBC in a loosely-coupled system runs it's own copy of the
PowerMAX OS and are networked together using standard TCP/IP
protocols.
o Each target can NFS mount it's root from the host SBC disk.
o Fast, VMEbus-based point-to-point networking is used to
communicate between SBCs on the same VMEbus.
o Traditional Ethernet is used to communicate between SBCs which
reside in different VME chassis.
o A target can be booted via the VMEbus (initiated by the host). A
target SBC which has Ethernet configured, may initiate booting
using NET BOOT (booting over Ethernet using TFTP).
o A shared memory interface is provided which all SBC's on the same
VMEbus can access.
o SBCs can use the on-board DMA controller to directly read/write
memory of other SBCs on the same VMEbus.
o SBCs can send interrupts to other SBCs on the same VMEbus.
For more information on the Loosely-Coupled Systems, refer to the
Loosely-Coupled System User's Guide (Pubs No. 0891060).
8.1.5 New_spl_manage()_Function
In order to achieve binary compatibility between various hardware
platforms running PowerMAX OS, a new library function, spl_manage(3X),
has been provided in Release 4.1m. spl_manage() provides the same
functionality as the spl_request(3X) function with the exception that
the first argument, the ipl value, must be one of the new PL_xxx
definitions provided in <sys/ipl.h>.
For example, code of the form spl_request(PL4, addr) would now be
written as spl_manage(PL_4,addr).
Whereas the PLxxx definitions required for the old spl_request(3X)
function are unique to the hardware platform, the PL_xxx definitions
used with spl_manage() are identical across all of the supported
architectures. Therefore use of the new spl_manage() provides a
binary compatible method of altering the hardware IPL value.
- 31 -
Power Hawk PowerMAX OS 4.1m Release Notes
8.1.6 Notification_of_VME_I/O_Bus_Errors
The 4.1m release of PowerMAX OS supports the iobus_err(2) system
service. This system service provides applications with the
capability of registering to catch I/O bus errors that may occur
within a user-specified range of VME address space. When a VME I/O
bus error occurs, registered applications are sent a signal to notify
them of the bus error. At that point, additional information about
the bus error may be obtained with an additional iobus_err(2) call.
Registering to catch VME I/O bus errors can often prevent what
otherwise would result in system panics. See the iobus_err(2) man
page for more details.
8.1.7 FBS_Soft_Overruns
The 4.1m release of PowerMAX OS supports soft FBS overruns; in
previous releases, overruns were treated as hard overruns. A hard
overrun can be thought of as a frame overrun that is considered a
catastrophic failure of the scheduled process. A soft overrun can be
thought of as a frame overrun that may or may not be considered a
catastrophic failure depending upon whether or not the scheduled
process has reached its limit on the number of such overruns that can
be tolerated.
The motivation behind soft overruns is twofold. First, a scheduled
process may overrun a frame due to some random, nondeterministic event
which may be highly unlikely to ever occur again. Second, the
magnitude of any such frame overrun may be very small. In spite of
these observations, previous overrun processing would consider this
frame overrun to be catastrophic. Soft overruns give the scheduled
process incurring this delay a chance to recover from it and get back
into synchronization. If the scheduled process cannot recover, this
will be detected whenever the scheduled process exceeds its soft
overrun limit.
For more information, see the following:
PowerMAX OS Guide to Real-Time Services manual (Pubs No. 0890479)
and also, the following man pages:
fbswait(2)
fbswait(3F77rt)
rtcp(1)
sched_pgm_set_soft_overrun_limit(3F77rt)
sched_pgm_set_soft_overrun_limit(3rt)
sched_pgm_soft_overrun_query(3F77rt)
sched_pgm_soft_overrun_query(3rt)
- 32 -
Release Notes 4.1m Power Hawk PowerMAX OS
8.1.8 Network_File_System_(NFS)
The NFS software was changed in PowerMAX OS 4.1m so that it can be
configured in multiple ways to suit the needs of your system. It can
be configured as:
o a client only NFS system
o a server only NFS system
o both a client and server NFS system
There are now four NFS modules:
o nfss - code and structures common to both client and server NFS
(static portion)
o nfscmn - code and structures common to both client and server NFS
(can be a DLM module)
o nfs - code and structures for client NFS (can be a DLM module)
o nfssrv - code and structures for server NFS (can be a DLM module)
The nfss and nfscmn modules must always be enabled to use NFS. At
least one of the nfs or nfssrv modules must be enabled. When the NFS
software is installed on a system, it is configured by default as both
a client and a server NFS system (all four modules enabled).
The kernel lock manager module klm must be enabled for client NFS
configurations, but it is not used by the server NFS module (nfssrv).
Networking must be enabled for all NFS configurations.
8.1.9 Privileges
The kernel maintains a table of file privileges in memory. It is
initialized at system startup by the initprivs(1M) command using the
file privilege entries in the Privilege Data File (PDF),
/etc/security/tcb/privs. Entries in the PDF are added, deleted, or
modified using the filepriv(1M) command. When the filepriv command
adds a file to the PDF, it records checksum, size and last updated
time (ctime) information about the file in addition to the file
privileges. initprivs compares this validity information to the
current values for the file. By default, if these do not match, the
file will not be granted privileges by initprivs and the entry will
not be passed to the kernel to add to the kernel privilege table.
In the 4.1m release of the PowerMAX OS this validity checking can be
disabled by resetting flags contained in the file
- 33 -
Power Hawk PowerMAX OS 4.1m Release Notes
/etc/default/privcmds. If the value of the VAL_SIZE option is No
(default = Yes), then the initprivs command will not validate the file
size value. If the value of the VAL_VALIDITY option is No (default =
No), then the initprivs command will not validate the last updated
time (ctime) information. On systems where the sum module is
configured (the Enhanced Security Utilities are not installed),
disabling the ctime validity checking in initprivs also disables the
validity checking performed by the kernel when a file is executed with
exec(2). See the initprivs(1M) manual page for further information.
The validity checking done in the initprivs(1M) command and the kernel
ensure that users are accessing a secure version of the privileged
command's executable file (that has not been corrupted). However, it
can become a burden for the system administrator to update the file
privilege information each time a new version of a privileged
executable is created on a system with a high volume of development
activity. The new VAL_SIZE and VAL_VALIDITY
o the security of privileged executables or,
o the convenience of building new privileged executables without
having to run the fileprivs(1M) command each time a privileged
executable is built.
The new priv(1) command can be used with any shell to display the
maximum and working sets of privileges associated with the calling
process.
Documentation for privileges and the Trusted Facility Management (TFM)
tools has been updated for the 4.1m release. Privileged users need to
perform sensitive tasks, but because privileges are associated with
processes and executable files, not user IDs (except root), it is not
possible to grant privileges to users directly. However, the TFM
tools maintain a database of users and the commands they may execute
with privilege. If privileges are assigned to a user's shell with the
TFM tools, they will be inherited by all commands executed by that
shell. This effectively provides privileges on a per user basis. The
TFM tools are available with the base package. See the System
Administration Volume 1 (Pubs No. 0890429) and the PowerMAX OS
Programming Guide (Pubs No. 0890423) manuals for further information.
8.1.10 Asynchronous_I/O_Compatibility
The sigevent structure in <sys/siginfo.h> has been modified in the
4.1m release of PowerMAX OS for POSIX compliance reasons. This
modification has caused a change to the size of the sigevent
structure. Since the Asynchronous I/O Control Block (aiocb) structure
contains a sigevent structure within it (see <aio.h> and aiocb(5)),
the offsets of certain fields within the aiocb structure in 4.1m are
- 34 -
Release Notes 4.1m Power Hawk PowerMAX OS
different from previous releases. As a result, the Asynchronous I/O
lio_listio(3) function call in the 4.1m release of PowerMAX OS is not
binary compatible with previous releases, although source
compatibility has been maintained. Therefore, applications using
lio_listio(3) must be recompiled for the 4.1m release.
8.1.11 Exclusive_Binding
As a result of the merger of features from the Maxion/OS, PowerMAX OS
users now have the ability to exclusively bind processes to
processors. This means that those processors are not permitted to run
any process which is not exclusively bound to them. This facility is
dynamic; the processors turns into an exclusive-use processor when it
acquires its first exclusively bound process, and reverts back to
being a general-purpose processor, available to all processes, when
the last process exclusively bound to it exits or disassociates
itself.
Any exclusive binding is inherited by children upon creation, and
across exec(2).
Exclusive bindings are set by the CPU_SETXBIAS command of the
cpu_bias(2) system call, and released by the CPU_SETBIAS command. The
library routines mpadvise(3c), processor_exbind(3c), and
processor_bind(3c) may also be used to affect exclusive bindings, as
well as the commands run(1), rerun(1), pbind(1), and pexbind(1). The
-P option of ps(1) will mark the display of exclusively bound
processes with an asterisk or plus sign. The information used by ps
is available from the pr_xbias field now in the /proc filesystem. And
finally, a mask identifying which processors are exclusive-use at the
moment may be fetched with the MPA_CPU_EXCLUSIVE command of
mpadvise(3c).
Of the interfaces discussed above, only the processor_bind,
processor_exbind, pbind, and pexbind interfaces conform to what was
available in the Maxion/OS.
8.1.12 Kma_Giveback_Daemon_Tunable
The concept of `Shielded Processor' requires that the user have
complete control as to what processes and what interrupts run on the
shielded processor. In pursuit of this goal, a new configuration
tunable, KMA_GBACK_DISABLE, has been added to PowerMAX OS. This is a
bit mask specifying which processors are allowed to maintain a private
pool of global memory, and which are not. The purpose of these
private pools is to improve the average allocation and deallocation
speed of storage buffers needed by the kernel, at the expense of
requiring a daemon for each processor to periodically release excess
buffers back to the global pool. This daemon is called the kernel
- 35 -
Power Hawk PowerMAX OS 4.1m Release Notes
memory allocator (kma) giveback daemon.
This daemon should not be run on a shielded processor.
In the default configuration this tunable is set up to allow every
processor to have a private memory pool.
8.1.13 Network_Information_System_(NIS)
NIS support is provided with this release of PowerMAX OS. NIS is a
distributed name service that replaces copies of commonly replicated
configuration files with a centralized management facility. Instead
of having to manage each host's files, it is only necessary to
maintain one version of the file on the central server. Hosts that
are using NIS retrieve information as needed from a server system.
NIS is best suited for files that have no host-specific information in
them and hence are generally the same on all hosts in a network.
For more information on NIS, refer to the Network Administration
manual (Pubs No. 0890432).
8.1.14 Sendmail
PowerMAX OS now provides an alternative mailer program - sendmail.
Sendmail may be used to send or receive remote mail from hosts
connected via a network.
Sendmail was designed as a centralized mail facility used to route
mail by interpreting addresses according to a set of well-defined (and
configurable) rules. Message headers can also be rewritten to conform
to a number of standards or specialized targets.
Sendmail does not interface directly with users nor does actual mail
delivery. Rather, it collects mail messages generated by such mail
interface programs as mail(1) or mailx(1), edits the message as
directed and then calls the appropriate mailer to do the mail
delivery.
There is also a sendmail daemon that can be invoked as an SMTP server
for incoming remote mail.
For more information, refer to the Network Administration manual (Pubs
No. 0890432).
- 36 -
Release Notes 4.1m Power Hawk PowerMAX OS
8.1.15 STREAMS_Enhancements
STREAMS has been enhanced to include additional interfaces which allow
applications running in user space to share data with kernel drivers.
A user of these interfaces is able to avoid the the data copying
overhead associated with STREAMS output requests. This gives improved
performance when large data unit output requests are made. The details
of the interface are described in streamio(7). The associated system
configurables are described in the Streams category of system
configurables (see config(1M)).
- 37 -
Power Hawk PowerMAX OS 4.1m Release Notes
The new system configurables are:
STR_MAX_NBUFF
STR_NBUFF_COPYSIZE
STR_NPAGES_FPMAX
STR_NPAGES_TMAX
8.1.16 Virtual_Interrupt_System_(VIS)
The Concurrent Virtual Interrupt System permits cooperating processes
to establish channels to which they can connect to send and receive
signals. These signals can be used to notify processes of specific
events, and do not require the standard permissions that standard
signal interfaces demand. The manual pages on the VIS functions
provide greater detail. These are:
vi_create(2)
vi_ctl(2)
vi_delete(2)
vi_map(2)
vi_mapsource(2)
vi_nonsense(2)
vi_sense(2)
vi_unmap(2)
8.1.17 BSD_4.3_libs
A large portion of the functionality from the BSD 4.3 dialect of UNIX
is provided by standard system services and library routines. An
additional set of BSD-compatible routines are provided in the
libraries: libucbc, libmp and libdbm.
The libucbc library contains various services including packed decimal
routines, getwd, alternate dbm routines, random number routines,
alternate setjmp and longjmp, alternate signal routines and many
others. The libmp library provides multiple precision math routines.
The libdbm library provides a set of data base subroutines.
For more information on these libraries, refer to the intro(3B) manual
page.
8.1.18 Multiplexer_VMEbus_Controller_(mvc)_Driver
Processes requiring the use of the mvc driver should be biased to the
same CPU board that the driver is bound to. The mvc driver is bound
by default to CPU 0 but can be changed to another CPU if available.
See manual page Master(4) for details on how to bind the driver to a
specific CPU.
In addition, hvme/vme interrupt level 4 should likewise be bound to
the same CPU the mvc driver is bound to (see manual page config(1M)
- 38 -
Release Notes 4.1m Power Hawk PowerMAX OS
for instructions).
8.1.19 Dispatcher_Tables
The config(1M) utility has a new option for modifying the Dispatcher
Parameter Tables (DPT). Each process scheduling class (e.g. FP, TS,
FC) has a DPT associated with it which describes the range of class-
specific priority numbers. config(1M) now has a more user-friendly
interface for modifying these tables.
8.1.20 setrun command
The new setrun(1) command allows the user to specify the scheduling
environment for a process through the use of only one command. Process
characteristics which otherwise would have been specified with one or
more of mlockall(3c), priocntl(1), priocntl(2), processor_bind(3c),
and processor_exbind(3c) can now be specified with just one command.
8.1.21 mload command
The new mload(1) command allows the preloading and prelocking of
objects, e.g. files or shared memory segments, into memory.
8.1.22 mview command
The new mview(1) command is a system memory viewing program which
allows a user to determine on which memory pool the pages associated
with a process, file, or shared memory segment reside.
8.1.23 metreg
The new metreg(1) command collects various performance metrics from
the kernel and logs the information in /var/adm/metreg.data. This data
file may be analyzed using the metdump(1) command. metreg(1) and
metdump(1) can be used to find information and statistics about
filesystems, VM, IPC, scheduling and other important kernel
subsystems.
8.2 Compilation Systems
8.2.1 Commands_and_Utilities
The C compiler provided with PowerMAX OS 4.1m predefines the macro
_PowerMAXOS, indicating the compiler runs under PowerMAX OS. This
release of the compiler continues to predefine the macro _PowerUX, but
that predefinition will not be provided in the next release of the
compiler.
- 39 -
Power Hawk PowerMAX OS 4.1m Release Notes
The link editor is enhanced to permit automatically the inclusion of
position independent code (compiled with the -Zpic option) in non-
shared object portions of programs. This capability was formerly
available only when the the -Qgotp_to_got option of ld(1) was used.
The link editor will warn of the use of pic code in non-shared
objects, because of the resulting performance degradation. The
warning message can be disabled with use of the new -Qno_warn_gotp
option.
The gmake utility has been updated to version 3.75. The gmake command
should be backwards compatible with the older make command, but is
more current, more stable, and has additional features.
8.2.2 C_Library
8.2.3 Thread_Library
8.2.3.1 POSIX Thread Support
In the 4.1m release of PowerMAX OS, the thread library (-lthread) has
been modified to provide most of the POSIX thread functions, as
specified in the ISO/IEC 9945-1: 1996 specification. (Also known as
ANSI/IEEE Std 1003.1, 1996 Edition.) The POSIX thread support
provides a set of library functions which allow customers to create
POSIX compliant multi-threaded applications. While most of the POSIX
thread library functions are provided in the 4.1m release of PowerMAX
OS, the following function calls will not be provided until the next
subsequent release of PowerMAX OS:
o pthread_atfork() - register fork handlers,
o pthread_detach() - dynamically place a thread into the detached
state,
o All of the thread cancellation support functions listed below:
pthread_cancel()
pthread_setcancelstate()
pthread_setcanceltype()
pthread_testcancel()
pthread_cleanup_pop()
pthread_cleanup_push()
o The mutex scheduling attributes functions listed below:
pthread_mutexattr_getprioceiling()
pthread_mutexattr_setprioceiling()
pthread_mutexattr_getprotocol()
pthread_mutexattr_setprotocol()
pthread_mutex_getprioceiling()
pthread_mutex_setprioceiling()
- 40 -
Release Notes 4.1m Power Hawk PowerMAX OS
See the pthread(3pthread) man pages for details on the new POSIX
thread function calls.
9. Compatibility Between Night Hawk, Power Hawk and PowerMAXION
Systems
PowerMAX OS for the Power Hawk Model 610/620 systems in general
provides source and binary compatibility with PowerMAX OS on the Night
Hawk HN6200/HN6800. Code written, compiled and/or linked on one of
these platforms will operate on the other with the following
exceptions:
1. Applications written for the Night Hawk and PowerMAXION systems
that use the real-time clocks (RTCs) may require minor
modifications to function properly on a Power Hawk system. Five
RTCs are available on the Power Hawk Model 610, two 32-bit timers
with a 1 microsecond resolution (tick timers) and three 16-bit
timers (Z8536 timers) with a 400 nanosecond resolution. (Note
that RTCs are not available on the Power Stack system - see item
#7 below for further details on this subject).
Seven RTCs are available on the Power Hawk Model 620, four 32-bit
timers with a 1 microsecond resolution (tick timers) and three
16-bit timers (Z8536 timers) with a 400 nanosecond resolution.
On the Night Hawk and PowerMAXION, the RTCs have device names
/dev/rrtc/0cx where x is between 0 and 4. On the Power Hawk, the
tick timers have similar names (/dev/rrtc/0c0-3) while the Z8536
timers use /dev/rrtc/1c0-2.
When utilizing one of the tick timers in "default mode" no code
changes are required, only a re-compilation of the application.
If one of the Z8536 timers are to be used, the application will
need to be modified to handle the 400 nanosecond resolution of
the timers.
If the RTC application uses "direct mode" the modifications could
be extensive. Review the rtc(7) man page for a description of the
"direct mode" functionality on each of the systems.
2. PowerMAX OS on the Night Hawk and PowerMAXION systems provides
the ability to generate an address translation to the Interval
Timer hardware and read it directly from the user process. This
is done using the /dev/interval_timer device. Such a POSIX-
format timer does not exist on the Power Hawk hardware therefore,
programs that depend upon this operation will not operate. There
are two alternatives that provide compatible operation.
- 41 -
Power Hawk PowerMAX OS 4.1m Release Notes
a. Use the C library routines, such as clock_gettime(). This
routine exists in the shared C library and generates
instructions appropriate to the hardware platform. On the
Night Hawk and PowerMAXION, this routine uses the hardware
Interval Timer while on the Power Hawk it uses the 64-bit
Time Base Register. Note that conversion of the Time Base
register to POSIX format takes notably longer than merely
reading the Interval Timer register.
b. Use the Time Base Register exclusively for timing. This is
a 64-bit register that increments at 1/4 the clock speed of
the processor bus. For example, on a Power Hawk system that
has a processor bus speed of 66.66MHz, it increments at the
rate of 16.65MHz. This is a processor register on the
PPC604 and is directly accessible from user code. However,
conversion to seconds and nanoseconds may be time consuming
depending upon the processor bus speed.
3. Night Hawk and PowerMAXION PowerMAX OS provides a set of routines
to read and/or write the hardware ipl register. This register
determines the interrupt level that the processor is currently
running at. The ability to read/write the ipl value is
especially useful for user-level device drivers.
The spl_map() package includes routines to generate virtual
mappings to the hardware ipl register, along with a library to
write the register (spl_request) and a macro to do the same
(spl_request_macro). Mappings are done by using the /dev/spl
device node.
Power Hawk systems do not have a hardware ipl register. Instead
a series of hardware registers implement the ipl functionality
through a series of bit masks. Therefore, routines that map
directly to the hardware ipl register will not operate on these
systems. /dev/spl does not exist on Power Hawk systems.
Compatible operation between Power Hawk and the Night Hawk and
PowerMAXION systems can be accomplished using the following
techniques.
a. Do not use mmap(3) to map directly to the hardware
register(s).
b. Use the spl_map(), spl_unmap() and spl_manage() library
routines for all ipl register reads/writes. In this case,
binary compatibility is possible between Night Hawk and
Power Hawk platforms.
- 42 -
Release Notes 4.1m Power Hawk PowerMAX OS
c. The spl_xxx routines are contained in libud. If the shared
version of libc is used in the executables, then the shared
version of libud must also be used.
d. If the spl_request() function or the spl_request_macro() is
used, the program will need to be recomplied and relinked on
the target machine, as the macro implementation will be
different. On the Power Hawk it will be the same as the C
library routine.
e. Do not depend upon hard-coded spl values, as the values used
may vary between platforms. However, in all cases, an spl
value of 0 allows all interrupts, and higher values prevent
more and more interrupts. spl values are always less than
255.
4. Programs that depend upon the arrangement and size of kernel data
structures may not work properly due to differing sizes of
certain items. These would be programs that utilize /dev/mem or
/dev/kmem to read and/or examine kernel structures. These
programs should be recompiled on the target system to ensure
functionality.
5. Power Hawk platforms are only single processor systems. Programs
that require multiple processors, or make system calls that
reference multiple processors, may not operate properly.
6. Edge Triggered Interrupts are available on the Night Hawk and
PowerMAXION platforms but not on the Power Hawk platform.
Therefore, there is no software support on Power Hawk systems for
Edge Triggered Interrupts.
7. The Power Stack does not contain real-time clocks. Therefore,
some standard OS interfaces are not supported on the Power Stack.
The interfaces not supported are:
Posix interface timer_settime(3C)
Posix interface nanosleep(3C)
frequency-based scheduling using real-time clocks
NightSim's use of real-time clocks
The following interfaces are available but only at a low-
resolution (16 millisecond granularity):
timeout on server_block(2)
timeout on client-block(2)
For more information, see the section "Using High-Resolution
Timeout Facilities" in Chapter 3 of the PowerMAX OS Real-Time
Guide (Pubs No 0890466).
Note that the lack of real-time clocks does not affect high-
resolution time of day services such as the Posix interface
clock_gettime(3C).
- 43 -
Power Hawk PowerMAX OS 4.1m Release Notes
10. Manual Pages
Manual pages can be found online. The easiest way to access these is
by typing man followed by a manual page name or a command name.
Typing man manual, for example, will show online the manual page that
contains a categorized listing of all the current manual names,
publication numbers and latest revision numbers.
On-line manual pages also exist for most software and hardware manuals
in this document. These manual pages provide a description of each
manual and also list all related publications, where applicable. To
access, type apropos pubs number that will display the manual page
name. Typing man manual page name will then show on the screen the
manual page you are interested in.
Printed copies of selected man pages that may need to be referenced
during installation are provided in Appendix A to these notes. These
man pages are:
format(1M)
pkgadd(1M)
11. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 44 -
Contents
1. Introduction................................................. 1
2. Documentation................................................ 2
2.1 PowerMAX OS Software Documentation..................... 2
3. Software Prerequisites....................................... 2
4. Hardware Prerequisites....................................... 3
4.1 CPU.................................................... 3
4.2 SCSI Interface Controller.............................. 3
4.3 Disk/Tape Drives....................................... 3
4.4 Ethernet Controllers................................... 3
4.4.1 Internal DEC Ethernet Controller............... 3
4.4.2 PCI/PMC DEC Ethernet Controller:............... 4
4.4.3 Interphase 4207 Eagle.......................... 4
4.4.4 Interphase 4221 Condor......................... 4
4.5 FDDI Controllers....................................... 4
4.5.1 Interphase Peregrine 4211...................... 4
4.5.2 Interphase Peregrine 5211...................... 4
4.6 HPS.................................................... 4
4.7 HSDE................................................... 4
4.8 1553................................................... 5
4.9 DR11-W................................................. 5
4.10 Parallel Printer Port.................................. 5
4.11 VDT Terminal........................................... 5
5. System Installation.......................................... 5
5.1 Software Packages...................................... 5
5.2 System Disk Configuration.............................. 18
5.3 Installation Modes..................................... 20
5.3.1 Custom Mode of Installation.................... 20
5.3.2 Semi-Automatic Mode of Installation............ 20
5.4 Installation Procedure................................. 23
5.5 Standalone Utilities................................... 25
5.6 Installing Additional Packages......................... 25
6. Rebooting The System......................................... 26
6.1 Note Pertaining to XFS................................. 27
7. Features Ported From MAXION/OS............................... 28
8. Changes From Previous Release................................ 29
8.1 Operating System....................................... 29
8.1.1 Architecture Unification....................... 29
8.1.2 VIA Configuration.............................. 29
8.1.3 Resilient File System (xfs).................... 30
- i -
8.1.4 Loosely-Coupled Systems........................ 30
8.1.5 New spl_manage() Function...................... 31
8.1.6 Notification of VME I/O Bus Errors............. 32
8.1.7 FBS Soft Overruns.............................. 32
8.1.8 Network File System (NFS)...................... 33
8.1.9 Privileges..................................... 33
8.1.10 Asynchronous I/O Compatibility................. 34
8.1.11 Exclusive Binding.............................. 35
8.1.12 Kma Giveback Daemon Tunable.................... 35
8.1.13 Network Information System (NIS)............... 36
8.1.14 Sendmail....................................... 36
8.1.15 STREAMS Enhancements........................... 37
8.1.16 Virtual Interrupt System (VIS)................. 38
8.1.17 BSD 4.3 libs................................... 38
8.1.18 Multiplexer VMEbus Controller (mvc) Driver..... 38
8.1.19 Dispatcher Tables.............................. 39
8.1.20 setrun command................................. 39
8.1.21 mload command.................................. 39
8.1.22 mview command.................................. 39
8.1.23 metreg......................................... 39
8.2 Compilation Systems.................................... 39
8.2.1 Commands and Utilities......................... 39
8.2.2 C Library...................................... 40
8.2.3 Thread Library................................. 40
8.2.3.1 POSIX Thread Support.................. 40
9. Compatibility Between Night Hawk, Power Hawk and PowerMAXION
Systems...................................................... 41
10. Manual Pages................................................. 44
11. Direct Software Support...................................... 44
- ii -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
Power Hawk PowerMAX OS
Version 4.1m
Release Notes
0891058-4.1m
June 1997
_________________________________________________________________
Trademark Acknowledgments
Ada is a trademark Rational Software Corporation.
AXI is a trademark of Sente Corporation.
CX/RT is a trademark of Concurrent Computer
Corporation.
CX/UX is a trademark of Concurrent Computer
Corporation.
Elan License Manager is a trademark of Elan Computer Group, Inc.
Ethernet is a registered trademark of Xerox
Corporation.
gdb is a trademark of Free Software Foundation.
HAPSE is a trademark of Concurrent Computer
Corporation.
HSDE is a trademark of Concurrent Computer
Corporation.
MAXION/OS is a trademark of Concurrent Computer
Corporation.
NFS is a trademark of Sun Microsystems,
Incorporated.
NightProbe is a trademark of Concurrent Computer
Corporation.
NightSim is a trademark of Concurrent Computer
Corporation.
NightStar is a trademark of Concurrent Computer
Corporation.
NightTrace is a trademark of Concurrent Computer
Corporation.
NightTune is a trademark of Concurrent Computer
Corporation.
NightView is a trademark of Concurrent Computer
Corporation.
Night Hawk is a registered trademark of Concurrent
Computer Corporation.
OSF/Motif is a trademark of Open Software Foundation,
Inc.
PowerPC is a trademark of IBM Corporation.
PowerMAX OS is a trademark of Concurrent Computer
Corporation.
PowerSX is a trademark of Concurrent Computer
Corporation.
POSIX is a registered trademark of the Institute of
Electrical and Electronics Engineers, Inc.
Power Hawk is a trademark of Concurrent Computer
Corporation.
PowerMAXION is a trademark of Concurrent Computer
Corporation.
UNIX is a registered trademark licensed exclusively
by the X/Open Company Ltd.
VERITAS is a registered trademark of VERITAS Software
Corporation.
VxVM is a registered trademark of VERITAS Software
Corporation.
X Window System is a trademark of The Open Group.
.
Appendix A
Manual Pages
return to index
================================================================================