PowerMAX 4.1 Products are:
base_4.1
================================================================================
================================================================================
Power Hawk PowerMAX OS*
Version 4.1
Release Notes
Harris Computer Systems Corporation
1. Introduction
This document provides an overview of PowerMAX OS Release 4.1.
PowerMAX OS is supported on a variety of hardware platforms including
the following:
o Night Hawk Series 6000 systems (models HN6200 and HN6800)
o Power MAXION systems
o Power Hawk Model 610 systems
o Power Stack systems
(Note: Information applicable to Power Hawk is also applicable to
Power Stack unless otherwise noted.)
PowerMAX OS 4.1 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
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,
Power MAXION and Power Hawk platforms. The corresponding release notes
will be sent with the applicable platform.
__________
* These release notes cover the following products: PowerMAX OS
- 0 -
Release Notes 4.1 Power Hawk PowerMAX OS
________________________________________________________________
| Manual Name Pub. Number|
|_________________________________________________|_____________|
| PowerMAX OS Programming Guide | 0890423-050|
| Character User Interface Programming | 0890424-000|
| Device Driver Programming | 0890425-040|
| 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.1 Release Notes| 0891058-4.1|
| Compilation Systems Volume 1 (Tools) | 0890459-040|
| Compilation Systems Volume 2 (Concepts) | 0890460-040|
| PowerMAX OS Real-Time Guide | 0890466-040|
| PowerMAX OS Guide to Real-Time Services | 0890479-040|
| PowerMAX OS Documentation Overview | 0890470-040|
| Power Hawk 610 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-305-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.
2.2 Power Hawk Motorola Documentation
The following table lists the standard Motorola documentation that is
normally provided with each Power Hawk system (see table above for
documentation available with PowerMAX OS).
__________________________________________________________________
| Manual Name Pub. Number|
|___________________________________________________|_____________|
| PPCBug Firmware Package User's Manual, Part 1 of 2| PPCBUGA1/UM|
| PPCBug Firmware Package User's Manual, Part 2 of 2| PPCBUGA2/UM|
| PPC1Bug Diagnostic Manual | PPC1DIAA/UM|
|___________________________________________________|_____________|
- 1 -
Power Hawk PowerMAX OS 4.1 Release Notes
3. Software Prerequisites
None.
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 (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 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.
- 2 -
Release Notes 4.1 Power Hawk PowerMAX OS
4.4 Ethernet Controllers
4.4.1 Internal_DEC_Ethernet_Controller
Ethernet may be provided with the on-board DEC 21040 Ethernet chip.
4.4.2 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.3 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.
- 3 -
Power Hawk PowerMAX OS 4.1 Release Notes
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
- 4 -
Release Notes 4.1 Power Hawk PowerMAX OS
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.
- 5 -
Power Hawk PowerMAX OS 4.1 Release Notes
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 | |
| 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 | n | 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/HSA SCSI Adapter Driver | y | y | y | via | |
| Parallel Port Driver | n | n | y | lpt | lp |
|___________________________________________|_______|______|_____|_________|____________|
- 6 -
Release Notes 4.1 Power Hawk PowerMAX OS
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 | netcmd| 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, df|
| Distributed File System Utilities | y | y | y | dfs | inet |
|________________________________________|_______|______|_____|_______|___________________|
| Security: | | | | | |
| Auditing | y | y | y | audit | |
| Access Control List Utilities | y | y | y | acl | |
| Enhanced Security Utilities | y | y | y | es | acl, audit |
|________________________________________|_______|______|_____|_______|___________________|
| 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_rt| |
|________________________________________|_______|______|_____|_______|___________________|
| 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 |
| NightView | y | y | y | nview | elanlm, x11 |
|________________________________________|_______|______|_____|_______|___________________|
| Miscellaneous: | | | | | |
| Virtual Partition | y | y | y | vp | |
| VERITAS Volume Manager | y | y | y | vxvm | nsu |
|________________________________________|_______|______|_____|_______|___________________|
|________________________________________|_______|______|_____|_______|___________________|
- 7 -
Power Hawk PowerMAX OS 4.1 Release Notes
| | | | | | |
|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.
- 8 -
Release Notes 4.1 Power Hawk PowerMAX OS
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.
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
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.
- 9 -
Power Hawk PowerMAX OS 4.1 Release Notes
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.
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.
- 10 -
Release Notes 4.1 Power Hawk PowerMAX OS
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/HSA SCSI Adapter Driver (via)
This driver package supports the following:
1. 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.
2. 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 53C825 SCSI Driver (ncr)
This driver package supports the internal SCSI
controller chip on the Power MAXION and Motorola
MVME1604 processor cards. Up to seven disks and/or
tape drives may be connected to this internal SCSI bus.
Internal DEC 21040 Ethernet Driver (dec)
This driver package supports the internal Ethernet
controller chip on the Power MAXION and Motorola
MVME1604 processor cards. Both 10baseT and AUI
connections are supported. Also supported is the DE435
PCI controller card which is based on this Ethernet
chip.
- 11 -
Power Hawk PowerMAX OS 4.1 Release Notes
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
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.
- 12 -
Release Notes 4.1 Power Hawk PowerMAX OS
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.
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 Packages:
To achieve B2-Level of security, add the packages audit, acl, and es.
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.
Access Control List Utilities (acl)
The Access Control List Utilities package provides
Enhanced Discretionary Access Control (DAC), that
allows a file owner to grant different access
permissions for specific individuals or groups.
- 13 -
Power Hawk PowerMAX OS 4.1 Release Notes
Enhanced Security Utilities (es)
The Enhanced Security Utilities package provides the
Mandatory Access Control (MAC), Least Privilege
Mechanism (LPM), and Trusted Path (TP) features:
MAC is a mechanism to restrict access to
files and other system objects on a
need-to-know basis.
LPM is a file-based privilege mechanism.
TP is a mechanism to ensure that the user
logging in is talking to the trusted
login process. (The Trusted Path
feature is only available on serial
ports.)
The term "C2 utilities" refers to the security features
provided by the Auditing Set. The term "B1 utilities"
refers to the software that provides the MAC feature;
the term "B2 utilities" refers to the software that
provides the MAC, LPM, and TP features. B2 utilities
include the C2 and B1 utilities; B1 utilities include
the C2 utilities.
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:
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.
- 14 -
Release Notes 4.1 Power Hawk PowerMAX OS
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
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.
NightView (nview)
This package provides a general-purpose, source-level
debugger for C, Fortran and Ada with support for
multiple processes. (The Ada support is preliminary.)
- 15 -
Power Hawk PowerMAX OS 4.1 Release Notes
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.
- 16 -
Release Notes 4.1 Power Hawk PowerMAX OS
5.2 System Disk Configuration
The following system disk configuration is suggested for installing
the system:
_________|______|______________
| | minimum size
partition| file| (formatted)
_________|______|______________
0 | root| 75 MB
1 | swap| 96 MB
2 | usr | 350 MB1
3 | var | 200 MB
4 | --- | <remainder>
62 | boot| 1024 KB
_________|______|______________
1 - Suggested minimum partition size was increased in this release by 150MB.
2 - Partition is applicable to Power Hawk boot disks only.
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. 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).
- 17 -
Power Hawk PowerMAX OS 4.1 Release Notes
Use the format(1M) "?" command for help with format commands. Refer
to the format(1M) manual page in Appendix A 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.
2. Partition 6 must be configured with a size of 512K bytes (1024
sectors).
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.
(Note that prior to Release 4.1, custom mode was the only mode
available.)
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.
- 18 -
Release Notes 4.1 Power Hawk PowerMAX OS
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.
- 19 -
Power Hawk PowerMAX OS 4.1 Release Notes
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 16
________________________________________________________________________________________________
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
- 20 -
Release Notes 4.1 Power Hawk PowerMAX OS
________________________________________________________________________________________________
nfs Install OAM forms and menus ? yes
________________________________________________________________________________________________
es Install B2 utilities ? yes
User assigned to role of SSO root
________________________________________________________________________________________________
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)
- 21 -
Power Hawk PowerMAX OS 4.1 Release Notes
Table 2. Assigned Installation Values Under Semi-Automatic Mode
(Cont)
_________________________________________________________________________________
Package Name Configurable Item Automatic Installation Value
_________________________________________________________________________________
nprobe Install directory for Nprobe standard location relative
to root directory
_________________________________________________________________________________
nsim Install directory for Nsim standard location relative
to root directory
_________________________________________________________________________________
ntrace Install directory for Ntrace standard location relative
to root directory
_________________________________________________________________________________
nview Install directory for Nview 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
may be continued.
To begin system installation on a halted system, insert the Base
Installation Tape and execute the following console commands: (where
- 22 -
Release Notes 4.1 Power Hawk PowerMAX OS
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)
o System disk configuration (see Section 5.2)
Following are applicable to custom mode installation only:
- 23 -
Power Hawk PowerMAX OS 4.1 Release Notes
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.
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.
- 24 -
Release Notes 4.1 Power Hawk PowerMAX OS
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
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
- 25 -
Power Hawk PowerMAX OS 4.1 Release Notes
= 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".
7. Enhanced Security Notes
It is advisable that the person configuring the B2 system (usually a
trusted systems programmer (TSP)), be familiar with chapters 9 and 10
of the System Administration Volume 1, (Pubs No. 0890429). Chapter 9,
"Introduction to Security" , introduces the concept of levels,
classifications, privileges, secure devices, etc. Chapter 10,
- 26 -
Release Notes 4.1 Power Hawk PowerMAX OS
"Installing Software on an Enhanced Security System", explains what to
do before booting an ES (Enhanced Security/B2) kernel.
The only trusted shell available at this point is /sbin/sh.
Therefore, all system administrative activities should be performed in
/sbin/sh. A list of important commands are shown in Appendix B to
these release notes.
The notion of privilege is important, because most commands used in
booting and maintaining the system are privileged. To be effective,
the system administrator should login at SYS_PRIVATE level and invoke
all commands with /sbin/tfadmin prepended to them. Also, there is no
"all-powerful" root. The system administrator designated to maintain
the machine must belong to the Site Security Officer (SSO) role. All
commands assigned to the SSO role are listed in Appendix C to these
release notes.
To administer the system after booting it using a secure kernel in the
B2 security state, do the following:
1. Login at the SYS_PRIVATE level as root, if root was assigned SSO
role, or as the other user_login who was assigned SSO (by
entering -h SYS_PRIVATE user_login at the login prompt).
2. After entering the password and receiving the shell prompt,
invoke all privilege commands using the /sbin/tfadmin command.
For example, to use the df command, enter: /sbin/tfadmin df.
3. Run fsck on usr filesystem by entering:
/sbin/tfadmin fsck -F sfs /dev/rdsk/0s2
4. Mount usr by entering:
/sbin/tfadmin mount -F sfs /dev/dsk/0s2 /usr
5. Mount additional disks/partitions/NFS partitions.
a. Determine the level at which each disk/partition will be
mounted.
b. Make entries in /etc/vfstab to specify the ceiling level of
the filesystem to be mounted.
c. Update the secure device database by using putdev(1M) as
- 27 -
Power Hawk PowerMAX OS 4.1 Release Notes
follows:
putdev -a home range="SYS_RANGE_MAX-SYS_RANGE_MIN" \
state="public" mode="static" cdevice="/dev/rdsk/4s4" \
bdevice="/dev/dsk/4s4" mountpt="/home" \
desc="Disk containing the /home"
Specify the mount-point when mounting over NFS
6. All additional packages (including patches) should be added in
nonsecure single-user mode.
7. You may add users with the following commands:
/sbin/tfadmin useradd
/sbin/tfadmin usermod
/sbin/tfadmin userdel
7.1 Important Notes
Please observe the following:
1. Make sure that /stand/unix is at SYS_PUBLIC level for
/usr/bin/savecore(1) to work properly.
2. If you are having a problem with privileges, make sure all the
privileges are intact. This can be done by running the command
/etc/security/tools/setpriv. This command generates a script that
may be executed from a shell prompt. You must execute this
operation in nonsecure single-user mode.
# /etc/security/tools/setpriv > /tmp/restore_privs
# chmod 555 /tmp/restore_privs
# /tmp/restore_privs > /dev/null 2>&1
3. To make it easier to work in the B2 environment, the following
commands have been added to the SSO role:
/usr/bin/adminrole
/usr/bin/adminuser
/sbin/filepriv
/usr/bin/netsetup
/usr/bin/hwstat
/usr/bin/devcfg
/usr/sbin/route
4. It is recommended that you configure a user other than root into
the SSO role database. Then you should use the usermod -h
-systerm:private root command to prevent root from logging in at
SYS_PRIVATE.
- 28 -
Release Notes 4.1 Power Hawk PowerMAX OS
7.2 Re-linking a Secure Kernel
A brief summary on how to re-link a secure kernel is shown below:
(This procedure should only be done on a nonsecure kernel.)
1. cd /etc/conf/sdevice.d.
2. Edit the file audit. Change the configuration field from "N" to
"Y" to enable auditing.
3. Edit the file dac. Change the configuration field from "N" to
"Y" to enable Discretionary Access Controls (DAC).
4. Edit the file mac. Change the configuration field from "N" to
"Y" to enable Mandatory Access Controls (MAC).
5. Edit the files lpm and sum. Change the configuration field from
"N" to "Y" in lpm and "Y" to "N" in sum to enable Least Privilege
Mechanism (LPM), otherwise Super User Mechanism (SUM) is used.
6. Rebuild the kernel by executing /etc/conf/bin/idbuild.
7. The kernel binary will be put into /etc/conf/cf.d.
8. Copy the kernel binary to /stand and relink it to unix.
9. Make sure that /stand/unix is at SYS_PUBLIC level for
/usr/bin/savecore(1) to work properly.
7.3 Installation Cautions
On the initial boot of the B2 kernel, several error messages will be
displayed which are not serious, or can be readily worked around once
the login prompt is attained.
The errors and steps necessary to resolve them are detailed below:
1. The following message appears when attempting to initialize the
virtual partitions:
UX:sh: (/sbin/sh): ERROR: /etc/vptab: Cannot execute
The above message only appears if the vp (virtual partition)
package is installed during the system generation. This error
message will only appear on the initial boot of the new B2 kernel
and since virtual partitioning is not yet configured at this
point, the message may be ignored.
- 29 -
Power Hawk PowerMAX OS 4.1 Release Notes
2. The following message appears while trying to fsck the root file
system for the first time:
UX:fsck: ERROR: cannot execute /usr/lib/fs/sfs/fsck -
permission denied
The above message only appears on the very first boot of the new
B2 kernel and may be ignored.
3. The following sequence of messages will occur on every boot of
any kernel until the ix25 package is fully configured. This
message will only occur if the ix25 package is installed during
the initial sysgen.
Downloading VCOM adapters... File /etc/XNET not found.
8. Changes From Previous Release
8.1 Operating System
8.1.1 Architecture_Unification
Because 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.1
this includes Night Hawk 6200/6800 and PowerMAXION systems. Future
releases will support additional architectures.
On these systems, a new configurable module, the Board Support
Package, or 'bsp' has been introduced. In Release 4.1, Board Support
Packages are provided as bsp6400 for the PowerMAXION and bsp6800 for
the Night Hawk 6200/6800. A bspall package is also available which is
used primarily for system installation.
The system installation scripts will automatically turn on the
appropriate module (bsp6400 or bsp6800) based upon the type of
hardware on which the system is being installed. It is also possible
to manually select one and only one bspxxx module and relink a kernel
which is appropriate for that particular hardware type. The bspall
module should not normally be used, but if configured on instead of
one of the others, a kernel which is larger and slower than the others
will be produced, but that kernel will operate on both architecture
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 either architecture type.
- 30 -
Release Notes 4.1 Power Hawk PowerMAX OS
Power Hawk and Power Stack systems are not affected by this change.
8.1.2 Processor_Identification
The /system/processor/n file can be opened and read to obtain
information about the the current system. The format of the
information read is defined in <sys/prosrfs.h>. The values for two
fields have changed in Release 4.1. The cpu_type field has changed to
indicate which PowerPC processor is in use. The values for this field
are defined by the CPU_xxx values in <sys/cpu.h>. The cpu_model field
was previously zero, but now contains platform identification. Values
for this field are defined by the MODEL_xxx values in <sys/cpu.h>.
Programs compiled under previous PowerMAX OS releases which use this
file will not operate properly due to the change in value of these
fields. These programs will need to have the code which references
this file changed to use the new definitions in <sys/prosrfs.h> and
then recompiled.
8.1.3 Interrupt_Configuration_Tunables
As a part of the architecture unification process discussed earlier,
the tunables used to specify which processor is to handle a particular
hardware interrupt have been renamed. All tunables of the form PIN_nn
have now been renamed to a more symbolic name such as
PICPU_EMBEDDED_UART. The table below provides a translation from the
old PIN_xxx values to the new tunables implemented in Release 4.1:
- 31 -
Power Hawk PowerMAX OS 4.1 Release Notes
________________________________________________
| Night Hawk| PowerMAXION| 4.1 |
| Tunable | Tunable | Tunable |
|___________|_____________|_____________________|
| PIN_15 | none | PICPU_EDGE0_0 |
|___________|_____________|_____________________|
| PIN_18 | none | PICPU_EDGE0_1 |
|___________|_____________|_____________________|
| PIN_35 | none | PICPU_EDGE0_2 |
|___________|_____________|_____________________|
| PIN_37 | none | PICPU_EDGE0_3 |
|___________|_____________|_____________________|
| PIN_14 | none | PICPU_EDGE1_0 |
|___________|_____________|_____________________|
| PIN_19 | none | PICPU_EDGE1_1 |
|___________|_____________|_____________________|
| PIN_38 | none | PICPU_EDGE1_2 |
|___________|_____________|_____________________|
| PIN_41 | none | PICPU_EDGE1_3 |
|___________|_____________|_____________________|
| PIN_17 | none | PICPU_EDGE2_0 |
|___________|_____________|_____________________|
| PIN_20 | none | PICPU_EDGE2_1 |
|___________|_____________|_____________________|
| PIN_39 | none | PICPU_EDGE2_2 |
|___________|_____________|_____________________|
| PIN_42 | none | PICPU_EDGE2_3 |
|___________|_____________|_____________________|
| PIN_16 | none | PICPU_EDGE3_0 |
|___________|_____________|_____________________|
| PIN_21 | none | PICPU_EDGE3_1 |
|___________|_____________|_____________________|
| PIN_40 | none | PICPU_EDGE3_2 |
|___________|_____________|_____________________|
| PIN_43 | none | PICPU_EDGE3_3 |
|___________|_____________|_____________________|
| PIN_23 | none | PICPU_RTC_0C0 |
|___________|_____________|_____________________|
| PIN_25 | none | PICPU_RTC_0C1 |
|___________|_____________|_____________________|
| PIN_24 | none | PICPU_RTC_0C2 |
|___________|_____________|_____________________|
| PIN_26 | none | PICPU_RTC_0C3 |
|___________|_____________|_____________________|
| PIN_27 | none | PICPU_RTC_0C4 |
|___________|_____________|_____________________|
| PIN_22 | none | PICPU_RTC_1C0 |
|___________|_____________|_____________________|
- 32 -
Release Notes 4.1 Power Hawk PowerMAX OS
|___________|_____________|_____________________|
| PIN_29 | none | PICPU_RTC_1C1 |
|___________|_____________|_____________________|
| PIN_28 | none | PICPU_RTC_1C2 |
|___________|_____________|_____________________|
| PIN_30 | none | PICPU_RTC_2C0 |
|___________|_____________|_____________________|
| PIN_32 | none | PICPU_RTC_2C1 |
|___________|_____________|_____________________|
| PIN_31 | none | PICPU_RTC_2C2 |
|___________|_____________|_____________________|
| PIN_33 | none | PICPU_RTC_3C0 |
|___________|_____________|_____________________|
| PIN_34 | none | PICPU_RTC_3C1 |
|___________|_____________|_____________________|
| PIN_36 | none | PICPU_RTC_3C2 |
|___________|_____________|_____________________|
| PIN_52 | none | PICPU_PRIM_HVME_7 |
|___________|_____________|_____________________|
| PIN_53 | PIN_39 | PICPU_PRIM_VME_7 |
|___________|_____________|_____________________|
| none | PIN_38 | PICPU_EXP_VME_7 |
|___________|_____________|_____________________|
| PIN_54 | none | PICPU_PRIM_HVME_6 |
|___________|_____________|_____________________|
| PIN_55 | PIN_35 | PICPU_PRIM_VME_6 |
|___________|_____________|_____________________|
| none | PIN_34 | PICPU_EXP_VME_6 |
|___________|_____________|_____________________|
| PIN_60 | none | PICPU_PRIM_HVME_5 |
|___________|_____________|_____________________|
| PIN_61 | PIN_29 | PICPU_PRIM_VME_5 |
|___________|_____________|_____________________|
| none | PIN_28 | PICPU_EXP_VME_5 |
|___________|_____________|_____________________|
| PIN_78 | none | PICPU_PRIM_HVME_4 |
|___________|_____________|_____________________|
| PIN_79 | PIN_20 | PICPU_PRIM_VME_4 |
|___________|_____________|_____________________|
| none | PIN_19 | PICPU_EXP_VME_4 |
|___________|_____________|_____________________|
| PIN_80 | none | PICPU_PRIM_HVME_3 |
|___________|_____________|_____________________|
| PIN_81 | PIN_16 | PICPU_PRIM_VME_3 |
|___________|_____________|_____________________|
| none | PIN_15 | PICPU_EXP_VME_3 |
|___________|_____________|_____________________|
|___________|_____________|_____________________|
- 33 -
Power Hawk PowerMAX OS 4.1 Release Notes
| PIN_82 | none | PICPU_PRIM_HVME_2 |
|___________|_____________|_____________________|
| PIN_83 | PIN_12 | PICPU_PRIM_VME_2 |
|___________|_____________|_____________________|
| none | PIN_11 | PICPU_EXP_VME_2 |
|___________|_____________|_____________________|
| PIN_84 | none | PICPU_PRIM_HVME_1 |
|___________|_____________|_____________________|
| PIN_85 | PIN_8 | PICPU_PRIM_VME_1 |
|___________|_____________|_____________________|
| none | PIN_7 | PICPU_EXP_VME_1 |
|___________|_____________|_____________________|
| none | PIN_32 | PICPU_EMBEDDED_SCSI|
|___________|_____________|_____________________|
| PIN_56 | none | PICPU_EXT_PORT_0A6 |
|___________|_____________|_____________________|
| PIN_57 | none | PICPU_EXT_PORT_1A6 |
|___________|_____________|_____________________|
| PIN_58 | none | PICPU_EXT_PORT_2A6 |
|___________|_____________|_____________________|
| PIN_59 | none | PICPU_EXT_PORT_3A6 |
|___________|_____________|_____________________|
| none | PIN_26 | PICPU_EMBEDDED_ENET|
|___________|_____________|_____________________|
| PIN_70 | none | PICPU_EXT_PORT_0C5 |
|___________|_____________|_____________________|
| PIN_71 | none | PICPU_EXT_PORT_1C5 |
|___________|_____________|_____________________|
| PIN_72 | none | PICPU_EXT_PORT_2C5 |
|___________|_____________|_____________________|
| PIN_73 | none | PICPU_EXT_PORT_3C5 |
|___________|_____________|_____________________|
| none | PIN_23 | PICPU_EMBEDDED_UART|
|___________|_____________|_____________________|
| PIN_62 | none | PICPU_UART_0 |
|___________|_____________|_____________________|
| PIN_63 | none | PICPU_UART_1 |
|___________|_____________|_____________________|
| PIN_64 | none | PICPU_UART_2 |
|___________|_____________|_____________________|
| PIN_65 | none | PICPU_UART_3 |
|___________|_____________|_____________________|
| PIN_87 | PIN_4 | PICPU_SOFTCLOCK |
|___________|_____________|_____________________|
- 34 -
Release Notes 4.1 Power Hawk PowerMAX OS
8.1.4 VIA/HSA_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.1, 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
the system.
8.1.5 File_System_Performance_Improvement
The default parameters for creating a new file system have been
modified to provide higher performance in the default case. The most
noticeable change is that the default block size is now 8K instead of
4K. Other changes to file system algorithms provide improvements in
throughput, especially in the case of large sequential transfers.
To take full advantage of file system performance improvements,
existing files on the disk must be backed up, a newfs(1M) must be
performed on the disk, and the files then restored.
8.1.6 Static_Network_Library
The dynamic versions of the Network Libraries (libsocket.so,
libnsl.so, libresolv.so, tcpip.so, resolv.so and straddr.so) are
combined and built into a static library, named "libnsl.a".
libsocket.a and libresolv.a are softlinks to libnsl.a, created to
minimize the changes in the makefiles to build static network
commands. The changes in the makefile, would be to add -lthread and
-Zlink=static options to the link command. Thus the link options:
"-lsocket -lnsl -lgen... -Zlink=dynamic"
for building network commands with shared libraries will change to:
"-lnsl -lgen -lthread... -Zlink=static"
for building static network commands.
Note: The size of an executable may increase many fold from dynamic to
static mode, but the static commands run faster.
8.1.7 Methods_Available_for_Decreasing_Boot_Time
An administrator now has the ability to decrease boot time by setting
the values of three new tunables and by "customizing" system
initialization scripts.
- 35 -
Power Hawk PowerMAX OS 4.1 Release Notes
8.1.7.1 Tunables Affecting Boot Time
Boot time can be decreased by bypassing certain functions during
system initialization. The tunables and the functions they control are
listed below. Refer to Chapter 3 of the System Administration manual
(Volume 1) for additional information on these tunables.
Tunable Function
______________________________________________________________________________________
CONSMSGDIS console message output during system initialization
______________________________________________________________________________________
file system consistency checks performed by system initialization scripts
FASTFS creation of security index and master files
remounting of root file system
______________________________________________________________________________________
SCSISCAN SCSI device lookup
______________________________________________________________________________________
8.1.7.2 Customizing a System State
There are several system configuration changes an administrator can
make to further improve boot time. These are:
1. Create "custom" system state which bypasses some of the functions
performed during system boot to multi-user state.
2. Make inittab file smaller by eliminating entries which are not
required to run for your state or can be run after the system has
been booted.
3. Delay starting some utilities (networking for example) until
after the system has booted.
Refer to Chapter 3 of the System Administration manual (Volume 1) for
specific information on how to customize your system to achieve
reductions in boot time.
8.1.8 Shutting_Down_the_System_Quickly
Shut down time is affected by: how may processes are running, how much
of the file buffers need to be flushed to disk and the number of
facilities and daemons that are running which need to be stopped in a
clean and orderly fashion.
In a given environment, the method of choice for bringing the system
down may be to invoke the uadmin(1M) command directly. Bypassing init
and shutdown speeds up the process by a significant amount of time.
- 36 -
Release Notes 4.1 Power Hawk PowerMAX OS
Refer to Chapter 3 of the System Administration manual (Volume 1)
8.1.9 XPG4_Base_93
This release contains modifications to allow the operating system to
be branded XPG4 Base compliant. Another common term for this standard
is XPG4 Base 93. (No attempt has been made to complete the branding
process at this time.)
8.1.10 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.1. 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.
8.1.11 General_Performance
Performance improvements were made to several key areas within the
kernel:
o Synchronization routines
o System service entry and exit
o Byte copy routines
o File system services
o Pipe services
The result is a reduction in the kernel overhead associated with most
applications. The total run-time of standard operating system
benchmarks has been reduced 10-20 percent.
- 37 -
Power Hawk PowerMAX OS 4.1 Release Notes
8.1.12 Uniprocessor_Determinism
Provides support for interrupt daemons. This feature is required to
get improved determinism on a uniprocessor. Interrupt daemons are
kernel threads which perform the majority of the work which would
otherwise be performed at interrupt level. Each device can be
configured to run with interrupt daemons or standard interrupt
routines. Determinism is gained for the highest priority processes in
the system by scheduling these processes at a higher priority than the
interrupt daemon.
Interrupt daemons cause degradation in I/O throughput for the devices
for which they are configured. The amount of degradation depends on
the amount of application processing performed at a higher priority
than the interrupt daemon.
8.1.13 Configurable_VME_Space_(Power_Hawk_Only)
On Power Hawk platforms, accesses to VME space that are issued by the
processor are accomplished through a special range of processor
physical addresses. The hardware on Power Hawk platforms translates
this range of processor physical addresses into PCI bus addresses that
fall into the PCI Memory Space range on the PCI Bus. Additional
hardware on Power Hawk platforms is set up to translate these PCI
Memory Space addresses into VME addresses, which the hardware will
place upon the VME Bus.
The PowerMAX OS operating system on Power Hawk platforms sets up a
default VME space configuration that is designed to maximize
compatibility with Night Hawk platforms while also providing a variety
of A16, A24 and A32 VME spaces. For most customers, this default
configuration should be sufficient for their needs, and will not
require any modification.
However, in an effort to provide additional flexibility, in this
PowerMAX OS release, the system administrator may now modify certain
system defaults pertaining to the VME to PCI configuration, and the
placement of VME windows for A32 and A24 devices. This configuration
of VME space on Power Hawk platforms may be accomplished by modifying
certain tunables by using the config(1M) utility. It should be
mentioned that the default values of these VME configuration tunables
provide the exact same VME space configuration of previous PowerMAX OS
releases.
Some of the reasons why a system administrator may want to modify the
default VME space configuration on Power Hawk platforms are listed
below:
- 38 -
Release Notes 4.1 Power Hawk PowerMAX OS
1. There are one or more VME devices configured in the system that
have a large amount of on-board memory and/or require that their
VME space be configured on certain address boundaries.
2. There are only A32 VME devices configured on the system, and it
would be desirable to expand the amount of A32 VME space, and
remove the A24 VME space, or vice versa.
3. Although PCI devices can be configured to respond to PCI I/O
Space addresses, PCI devices can also be configured to respond to
PCI Memory Space addresses. Therefore, it is possible that there
may be a mix of PCI and VME devices in the system that both want
to share PCI Memory Space. In this situation, it may be
desirable to reduce the amount of VME space within the PCI Memory
Space in order to allow more of the PCI Memory Space to be used
for PCI devices.
8.1.14 SVGA_Display/Mouse/Keyboard_Support_(Power_Hawk_Only)
The 4.1 release of PowerMAX OS provides support that enables the use
of a 101 key keyboard (IBM compatible) and VGA/SVGA monitor as the
primary system console for systems equipped with built-in SVGA, or a
plug-in VGA/SVGA display adapter.
Features included are:
1. Console/monitor program support that allow the keyboard and
display to be used as the system boot/diagnostic interface.
2. Standalone library support that allows the keyboard/display to be
used during system boot and installation.
3. PowerMAX OS kernel drivers and STREAMS modules supporting an IBM
compatible keyboard and controller, VGA/SVGA display, and a PS/2
compatible or serial mouse, including support for hotkey
switching between multiple "virtual" consoles.
4. Utilities for managing virtual terminals, changing display modes,
and managing pointing devices, etc.
5. Underlying OS support for a X11R6 server package.
The aforementioned X server is based on MetroX, the enhanced X11R6
server from Metrolink, Inc., and initially supports the built-in SVGA
(Cirrus GD5434) found on certain models in the Power Hawk line. The X
server product depends upon the facilities found in PowerMAX OS 4.1.
- 39 -
Power Hawk PowerMAX OS 4.1 Release Notes
8.1.15 Notification_of_VME_I/O_Bus_Errors
The 4.1 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, addition 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.16 FBS_Soft_Overruns
The 4.1 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:
o Guide to Real-Time Services manual
o man pages
o fbswait(2)
o fbswait(3F77rt)
o rtcp(1)
o sched_pgm_set_soft_overrun_limit(3F77rt)
- 40 -
Release Notes 4.1 Power Hawk PowerMAX OS
o sched_pgm_set_soft_overrun_limit(3rt)
o sched_pgm_soft_overrun_query(3F77rt)
o sched_pgm_soft_overrun_query(3rt)
8.1.17 Network_File_System_(NFS)
The NFS software was changed in PowerMAX OS 4.1 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.18 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
- 41 -
Power Hawk PowerMAX OS 4.1 Release Notes
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.1 release of the PowerMAX OS this validity checking can be
disabled by resetting flags contained in the file
/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 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.1 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. The TFM tools are available with the Standard Package. See
the System Administration Volume 1 and the PowerMAX Programming Guide
manuals for further information.
8.2 Compilation Systems
8.2.1 Commands_and_Utilities
The C compiler provided with PowerMAX OS 4.1 predefines the macro
_PowerMAXOS, indicating the compiler runs under PowerMAX OS. This
release of the compiler continues to predefine the macro _PowerMAX OS,
but that predefinition will not be provided in the next release of the
compiler.
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
- 42 -
Release Notes 4.1 Power Hawk PowerMAX OS
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 which are worth
looking into.
8.2.2 C_Library
8.2.3 Thread_Library
8.2.3.1 POSIX Thread Support
In the 4.1 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.1 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:
pthread_cancel(), pthread_setcancelstate(),
pthread_setcanceltype(), pthread_testcancel(),
pthread_cleanup_pop() and pthread_cleanup_push(),
o The mutex scheduling attributes functions:
pthread_mutexattr_getprioceiling(),
pthread_mutexattr_setprioceiling(),
pthread_mutexattr_getprotocol(), pthread_mutexattr_setprotocol(),
pthread_mutex_getprioceiling() and
pthread_mutex_setprioceiling().
See the pthread(3pthread) man pages for details on the new POSIX
thread function calls.
8.2.4 Math_Library
- 43 -
Power Hawk PowerMAX OS 4.1 Release Notes
9. Compatibility Between Night Hawk, Power Hawk and Power MAXION
Systems
PowerMAX OS for the Power Hawk Model 610 system in general provides
source and binary compatibility with PowerMAX OS on the Night Hawk
HN6200. 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 Power MAXION 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, 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.)
On the Night Hawk and Power MAXION, the RTCs have device names
/dev/rrtc/0cx where x is between 0 and 4. On the Power Hawk, the
two tick timers have similar names (/dev/rrtc/0c0-1) 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 Power MAXION 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 so
programs that depend upon this operation will not operate. There
are two alternatives that provide compatible operation.
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 Power MAXION, 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.
- 44 -
Release Notes 4.1 Power Hawk PowerMAX OS
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 100MHz Power Hawk
system that has a processor bus speed of 50MHz, it
increments at the rate of 12.5MHZ. 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 Power MAXION 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
Power MAXION 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 compatability is possible between Night Hawk and
Power Hawk platforms. See Section 8 above.
c. 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.
d. 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
- 45 -
Power Hawk PowerMAX OS 4.1 Release Notes
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
Power MAXION platforms but not on the Power Hawk platform.
Therefore, there is no software support on Power Hawk systems for
Edge Triggered Interrupts.
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)
putdev(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
- 46 -
Release Notes 4.1 Power Hawk PowerMAX OS
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.
- 47 -
Contents
1. Introduction................................................. 0
2. Documentation................................................ 0
2.1 PowerMAX OS Software Documentation..................... 0
2.2 Power Hawk Motorola Documentation...................... 1
3. Software Prerequisites....................................... 2
4. Hardware Prerequisites....................................... 2
4.1 CPU.................................................... 2
4.2 SCSI Interface Controller.............................. 2
4.3 Disk/Tape Drives....................................... 2
4.4 Ethernet Controllers................................... 3
4.4.1 Internal DEC Ethernet Controller............... 3
4.4.2 Interphase 4207 Eagle.......................... 3
4.4.3 Interphase 4221 Condor......................... 3
4.5 FDDI Controllers....................................... 3
4.5.1 Interphase Peregrine 4211...................... 3
4.5.2 Interphase Peregrine 5211...................... 3
4.6 HPS.................................................... 3
4.7 HSDE................................................... 3
4.8 1553................................................... 4
4.9 DR11-W................................................. 4
4.10 Parallel Printer Port.................................. 4
4.11 VDT Terminal........................................... 4
5. System Installation.......................................... 4
5.1 Software Packages...................................... 4
5.2 System Disk Configuration.............................. 17
5.3 Installation Modes..................................... 18
5.3.1 Custom Mode of Installation.................... 18
5.3.2 Semi-Automatic Mode of Installation............ 19
5.4 Installation Procedure................................. 22
5.5 Standalone Utilities................................... 24
5.6 Installing Additional Packages......................... 24
6. Rebooting The System......................................... 25
6.1 Note Pertaining to XFS................................. 26
7. Enhanced Security Notes...................................... 26
7.1 Important Notes........................................ 28
7.2 Re-linking a Secure Kernel............................. 29
7.3 Installation Cautions.................................. 29
8. Changes From Previous Release................................ 30
8.1 Operating System....................................... 30
- i -
8.1.1 Architecture Unification....................... 30
8.1.2 Processor Identification....................... 31
8.1.3 Interrupt Configuration Tunables............... 31
8.1.4 VIA/HSA Configuration.......................... 35
8.1.5 File System Performance Improvement............ 35
8.1.6 Static Network Library......................... 35
8.1.7 Methods Available for Decreasing Boot Time..... 35
8.1.7.1 Tunables Affecting Boot Time.......... 36
8.1.7.2 Customizing a System State............ 36
8.1.8 Shutting Down the System Quickly............... 36
8.1.9 XPG4 Base 93................................... 37
8.1.10 New spl_manage() Function...................... 37
8.1.11 General Performance............................ 37
8.1.12 Uniprocessor Determinism....................... 38
8.1.13 Configurable VME Space (Power Hawk Only)....... 38
8.1.14 SVGA Display/Mouse/Keyboard Support (Power
Hawk Only)..................................... 39
8.1.15 Notification of VME I/O Bus Errors............. 40
8.1.16 FBS Soft Overruns.............................. 40
8.1.17 Network File System (NFS)...................... 41
8.1.18 Privileges..................................... 41
8.2 Compilation Systems.................................... 42
8.2.1 Commands and Utilities......................... 42
8.2.2 C Library...................................... 43
8.2.3 Thread Library................................. 43
8.2.3.1 POSIX Thread Support.................. 43
8.2.4 Math Library................................... 43
9. Compatibility Between Night Hawk, Power Hawk and Power
MAXION Systems............................................... 44
10. Manual Pages................................................. 46
11. Direct Software Support...................................... 46
- ii -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
Power Hawk PowerMAX OS
Version 4.1
Release Notes
0891058-4.1
February, 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.
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.
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 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.
Power MAXION is a trademark of Concurrent Computer
Corporation.
Real-Time/PowerMAX 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 X Consortium, Inc.
.
Appendix A
Manual Pages
return to index
================================================================================