Digital PDFs

AA-MF05B-TE

June 1990

238 pages

Original

8.3MB

view download

OCR Version

7.5MB

view download

Document:	ULTRIX Reference Pages for Unsupported Software
Order Number:	AA-MF05B-TE
Revision:	0
Pages:	238
Original Filename:

OCR Text

ULTRIX

Reference Pages for Unsupported Software

Order Number: AA-MFQO5B-TE
June 1990

Product Version:

ULTRIX Version 4.0 or higher

This manual describes the unsupported commands, library routines, special files, file formats,
games, and macro packages for RISC and VAX platforms.

digital equipment corporation
maynard, massachusetts

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013.

Portions of the information herein are derived from copyrighted material as permitted under license agreements with
AT&T and the Regents of the University of California. © AT&T 1979, 1984. All Rights Reserved.

Portions of the information herein are derived from copyrighted material as permitted under a license agreement with
Sun MicroSystems, Inc. © Sun MicroSystems, Inc, 1985. All Rights Reserved.
Portions of this document © Massachusetts Institute of Technology, Cambridge, Massachusetts, 1984, 1985, 1986,
1988.

The information in this document is subject to change without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may
appear in this document.

The software described in this document is furnished under a license and may be used or copied only in accordance
with the terms of such license.

No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its
affiliated companies.

The following are trademarks of Digital Equipment Corporation:

mngnan
CDA
DDIF
DDIS

DECUS
DECwindows
DTIF
MASSBUS
MicroVAX

ULTRIX Worksystem Software
UNIBUS
VAX
VAXstation
VMS

DEC
DECnet

Q-bus
ULTRIX

VMS/ULTRIX Connection
vT

DECstation

ULTRIX Mail Connection

XUI

Triumvirate is a trademark of Compugraphic Corporation.
Modula-2 is a trademark of Interface Technologies Corporation.
System V is a registered trademark of AT&T.
Tektronix is a trademark of Tektronix, Inc.

Teletype is a registered trademark of AT&T in the USA and other countries.
UNIX is a registered trademark of AT&T in the USA and other countries.

Acknowledgments

In accordance with the licenses granted to Digital Equipment Corporation by AT&T and the University of California
at Berkeley pertaining to the software described herein, the following should be understood: Any related
documentation provided to third parties, whether pursuant to an agreement with Digital Equipment Corporation
permitting sublicensing of the software described herein or otherwise, must contain the provisions as set forth below.
Information herein is derived from copyrighted material as permitted under a license agreement with AT&T and The
Regents of the University of California.

UNIX is a trademark of AT&T. The UNIX trademark may not be used as or in the name of any licensee’s product.
Any use of the trademark in advertising, publicity, packaging, labeling or otherwise must state that UNIX is a
trademark of AT&T.

The software described in this documentation is based in part on the Fourth Berkeley Software Distribution under
license from The Regents of the University of California. The following individuals and institutions are acknowledged
for their role in its development:

The Electrical Engineering and Computer Science Department at the Berkeley Campus of the University of
California, Eric Allman, Ken Arnold, Ozalp Babaoglu, Scott B. Baden, Jerry Berkman, John Breedlove, Earl T.
Cohen, Robert P. Corbett, Mike Curry, Steve Feldman, Tom Ferrin, John Foderaro, Susan L. Graham, Charles Haley,
Robert R. Henry, Andy Hertzfeld, Mark Horton, S.C. Johnson, William Joy, Howard Katseff, Peter Kessler, Jim
Kleckner, J.E. Kulp, James Larus, Kevin Layer, Mike Lesk, Steve Levine, Jeff Levinsky, Louise Madrid, M. Kirk
McKusick, Colin L. McMaster, Mikey Olson, Geoffrey Peck, Ed Pelegri-Llopart, Rob Pike, Dave Presotto, John F.
Reiser, Asa Romberger, Bill Rowan, Jeff Schreibman, Eric P. Scott, Greg Shenaut, Eric Shienbrood, Kurt Shoens,
Keith Sklower, Helge Skrivervik, Al Stanberger, Ken Thompson, Michael C. Toy, Richard Tuck, Bill Tuthill, Mike
Urban, Edward Wang, David Wasley, Joseph Weizenbaum, Jon L. White, Glenn Wichman, Niklaus Wirth.

The Fourth Berkeley Software Distribution is provided by The Regents of the University of California and the Other
Contributors on an *‘as is’’ basis. Neither The Regents of the University of California nor the Other Contributors
warrant that the functions contained in the Fourth Berkeley Software Distribution will meet the licensee’s
requirements or will operate in the combinations which may be selected for use by the licensee, or that the operation
of the Fourth Berkeley Software Distribution will be uninterrupted or error free.

Neither The Regents of the University of California nor the Other Contributors make any warranties, either express or
implied, as to any matter whatsoever, including without limitation, the condition of the Fourth Berkeley Software
Distribution, its merchantability or its fitness for any particular purpose.

The licensee understands and agrees that The Regents of the University of California and the Other Contributors are
under no obligation to provide either maintenance services, update services, notices of latent defects, or correction of
defects for the Fourth Berkeley Software Distribution.

About Unsupported Reference Pages

The Reference Pages for Unsupported Software describe commands, routines, file
formats, special files and games for RISC and VAX platforms that are part of the
optionally installed, unsupported software subset. The unsupported software is not all
documented and there are differences between the documentation levels on the RISC
and VAX platforms. QARs are not accepted on the unsupported reference pages.

The unsupported reference pages are each labeled ‘‘Unsupported’” under the title.

Sections
The reference pages for the unsupported software are in one binder that is divided
into seven sections according to topic. Within each section, the reference pages are
organized alphabetically by title, except Section 3, which is divided into subsections.
Some reference pages carry a one- to three-letter suffix after the section number, for
example, abort(3f). The suffix indicates a ‘‘family’’ of reference pages for that
utility or feature.

Following are the sections that make up the Reference Pages for Unsupported
Software.

Section 1: Commands
This section describes unsupported commands that are available to all ULTRIX users.

Section 3: Library Routines
This section describes the unsupported routines available in ULTRIX libraries.
Routines are sometimes referred to as subroutines or functions.

Section 4: Special Files
This section describes unsupported special files, related device driver functions,
databases, and network support.

Section 5: File Formats
This section describes the format of unsupported system files and how the files are
used.

Section 6: Games
The reference pages in this section describe the games that are available in the
unsupported software subset.

Section 7: Macro Packages and Conventions
This section contains miscellaneous information, including ASCII character codes,
mail addressing formats, text formatting macros, and a description of the root file
system.

Section 8: Maintenance
This section describes unsupported commands for system operation and maintenance.

Platform Labels
The Reference Pages for Unsupported Software contain entries for both RISC and
VAX platforms. Pages that have no platform label beside the title apply to both
platforms. Reference pages that apply only to RISC platforms have a ‘*‘RISC”’ label
beside the title and the VAX-only reference pages that apply only to VAX platforms
are likewise labeled with ‘‘“VAX.”’ If each platform has the same command, system
call, routine, file format, or special file, but functions differently on the different
platforms, both reference pages are included, with the RISC page first.

Reference Page Format
Each reference page follows the same general format. Common to all reference pages
is a title consisting of the name of a command or a descriptive title, followed by a
section number; for example, date(1l). This title is used throughout the
documentation set.
The headings in each reference page provide specific information. The standard
headings are:

Name

Syntax

Provides the name of the entry and gives a short description.

Describes the command syntax or the routine definition. Section 5
reference pages do not use the Syntax heading.

Description

Provides a detailed description of the entry’s features, usage, and
syntax variations.

Options
Restrictions

Describes the command-line options.
Describes limitations or restrictions on the use of a command or
routine.

Examples

Provides examples of how a command or routine is used.

Return Values

Describes the values returned by a system call or routine. Used in
Sections 2 and 3 only.

Diagnostics

Describes diagnostic and error messages that can appear.

Files

Lists related files that are either a part of the command or used
during execution.

Environment

Describes the operation of the system call or routine, with the
POSIX and SYSTEM V environments. If the environment has no
effect on the operation, this heading is not used. Used in Sections
2 and 3 only.

vi About Unsupported Reference Pages

See Also
intro(4n), inet(4f)

4-12 Special Files

hy(4)
Unsupported

Name
hy — Network Systems Hyperchannel interface

Syntax
device hy0 at uba0 csr 0172410 vector hyint

Description
The hy interface provides access to a Network Systems Corporation Hyperchannel
Adapter.

The network to which the interface is attached is specified at boot time with an
SIOCSIFADDR ioctl. The host’s address is discovered by reading the adapter status
register. The interface will not transmit or receive packets until the network number
is known.

Restrictions
If the adapter does not respond to the status command issued during autoconfigure,
the adapter is assumed down. A reboot is required to recognize it.

Diagnostics
hy%d: unit number 0x%x port %d type %x microcode level 0x %x.

Identifies the device during autoconfiguration.
hy%d: can’t handle af%d.

The interface was handed a message with addresses formatted in an unsuitable
address family; the packet was dropped.
hy%d: can’t initialize.

The interface was unable to allocate UNIBUS resources. This is usually due to
having too many network devices on an 11/750 where there are only 3 buffered data
paths.

hy%d: NEX - Non Existent Memory.
Non existent memory error returned from hardware.
hy%d: BAR overflow.

Bus address register overflow error returned from hardware.

hy%d: Power Off bit set, trying to reset.

Adapter has lost power, driver will reset the bit and see if power is still out in the
adapter.

hy%d: Power Off Error, network shutdown.

Power was really off in the adapter, network connections are dropped. Software does

not shut down the network unless power has been off for a while.
ny%d: RECYD MP > MPSIZE (% d).

A message proper was received that is too big. Probable a driver bug. Shouldn’t

happen.

Special Files 4-13

VAX

hy(4)
Unsupported
hy%d: xmit error — len > hyolen [%d > %d].
Probable driver error. Shouldn’t happen.

hy%d: DRIVER BUG - INVALID STATE %d.
The driver state machine reached a non-existent state. Definite driver bug.

hy%d: watchdog timer expired.
A command in the adapter has taken too long to complete. Driver will abort and
retry the command.
hy%d: adapter power restored.

Software was able to reset the power off bit, indicating that the power has been
restored.

See Also
intro(4n), inet(4f)

4-14 Special Files

ik(4)
Unsupported

Name
ik — Ikonas frame buffer, graphics device interface

Syntax
device ik0Q at uba? csr 0172460 vector ikintr

Description

The ik program provides an interface to an Ikonas frame buffer graphics device.
Each minor device is a different frame buffer interface board. When the device is
opened, its interface registers are mapped, by virtual memory, into the user processes
address space. This allows the user process very high bandwidth to the frame buffer
with no system call overhead.

Bytes written or read from the device are DMA’d from or to the interface. The frame

buffer XY address, its addressing mode, etc. must be set up by the user process
before calling write or read.

Other communication with the driver is by ioctls. The IK_GETADDR ioctl returns
the virtual address where the user process can find the interface registers. The
IK_WAITINT ioctl suspends the user process until the ikonas device has interrupted
(for whatever reason — the user process has to set the interrupt enables).

Restrictions
An invalid access (for example, longword) to a mapped interface register can cause

the system to crash with a machine check.

Files
/dev/ik

Special Files 4-15

VAX

i1(4)
Unsupported

Name
il — Interlan 10 Mb/s Ethernet interface

Syntax
device il0 at uba0 csr 0161000 vector ilrint ilcint

Description
The i1 interface provides access to a 10 Mb/s Ethernet network through an Interlan
controller.

The host’s Internet address is specified at boot time with an SIOCSIFADDR ioctl.
The i1 interface employs the address resolution protocol described in arp(4p) to

dynamically map between Internet and Ethernet addresses on the local network.

The interface normally tries to use a “‘trailer’’ encapsulation to minimize copying

data on input and output. This may be disabled, on a per-interface basis, by setting
the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl.

Diagnostics
il%d: input error.
The hardware indicated an error in reading a packet off the cable or an illegally sized

packet.

il%d: can’t handle af%d.

The interface was handed a message with addresses formatted in an unsuitable
address family; the packet was dropped.

See Also
intro(4n), inet(4f)

4-22 Special Files

ps(4)
Unsupported

Name
ps — Evans and Sutherland Picture System 2 graphics device interface

Syntax
device ps0 at uba? csr 0172460 vector psintr

Description
The ps driver provides access to an Evans and Sutherland Picture System 2 graphics
device. Each minor device is a new PS2. When the device is opened, its interface
registers are mapped, via virtual memory, into a user process’s address space. This
allows the user process very high bandwidth to the device with no system call
overhead.

DMA to and from the PS2 is not supported. All read and write system calls will fail.
All data is moved to and from the PS2 via programmed I/O using the device’s
interface registers.

Commands are fed to and from the driver using the following ioctls:
PSIOGETADDR

Returns the virtual address through which the user process can access the
device’s interface registers.

PSIOAUTOREFRESH

Start auto refreshing the screen. The argument is an address in user space
where the following data resides. The first longword is a count of the number

of static refresh buffers. The next count longwords are the addresses in refresh
memory where the refresh buffers lie. The driver will cycle thru these refresh
buffers displaying them one by one on the screen.

PSIOAUTOMAP

Start automatically passing the display file thru the matrix processor and into
the refresh buffer. The argument is an address in user memory where the
following data resides. The first longword is a count of the number of display
files to operate on. The next count longwords are the address of these display
files. The final longword is the address in refresh buffer memory where
transformed coordinates are to be placed if the driver is not in double buffer
mode (see below).

PSIODOUBLEBUFFER

Cause the driver to double buffer the output from the map that is going to the

refresh buffer. The argument is again a user space address where the real
arguments are stored. The first argument is the starting address of refresh
memory where the two double buffers are located. The second argument is the
length of each double buffer. The refresh mechanism displays the current
double buffer, in addition to its static refresh lists, when in double buffer mode.
PSIOSINGLEREFRESH

Single step the refresh process. That is, the driver does not continually refresh

the screen.

PSIOSINGLEMAP

Single step the matrix process. The driver does not automatically feed display

files thru the matrix unit.
Special Files 4-23

VAX

ps(4)
Unsupported

PSIOSINGLEBUFFER

Turn off double buffering.
PSIOTIMEREFRESH
The argument is a count of the number of refresh interrupts to take before
turning off the screen. This is used to do time exposures.
PSIOWAITREFRESH
Suspend the user process until a refresh interrupt has occurred. If in
TIMEREFRESH mode, suspend until count refreshes have occurred.
PSIOSTOPREFRESH

Wait for the next refresh, stop all refreshes, and then return to user process.
PSIOWAITMAP

Wait until a map done interrupt has occurred.
PSIOSTOPMAP
Wait for a map done interrupt, do not restart the map, and then return to the
user.

Restrictions
An invalid access (for example, longword) to a mapped interface register can cause

the system to crash with a machine check.

Diagnostics
ps device intr.
ps dma intr.
An interrupt was received from the device. This shouldn’t happen, check your device

configuration for overlapping interrupt vectors.

Files
/dev/ps

4-24 Special Files

pup (4f)
Unsupported

Name
pup — Xerox PUP-I protocol family

Syntax
#include <sys/types.h>
#include <netpup/pup.h>

Description
The PUP-I protocol family is a collection of protocols layered atop the PUP Level-0
packet format, and utilizing the PUP Internet address format. The PUP family is
currently supported only by a raw interface.

Addressing
PUP addresses are composed of network, host, and port portions. The include file
<netpup/pup.h> defines this address as,
struct

pupport

{

u_char

pup_net;

u_char

pup_ host;

u_char

pup_socket[4];

}s
Sockets bound to the PUP protocol family utilize the following addressing structure,
struct

sockaddr pup

{

short

spup_family;

short

spup_zerol;

u_char

spup net;

u_char

spup_host;

u_char

spup sock{4];

char

spup_zero2[4];

Headers
The current PUP support provides only raw access to the 3Mb/s Ethernet. Packets

sent through this interface must have space for the following packet header present at
the front of the message,
struct

pup_header

{

u_short

pup_length;

u_char

pup_ tcontrol; /*

transport

u_char

pup_type;

protocol

u_long

pup_ id;

used by protocols

u_char

pup_dnet;

destination

u_char

pup_dhost;

u_char

pup_dsock([4];

u_char

pup_snet;

source

u_char

pup_shost;

u_char

pup ssock([4];

control
type

}s
Special Files 4-25

VAX

pup (4f)
Unsupported

The sender should fill in the pup_tcontrol, pup type, and pup
id fields. The
remaining fields are filled in by the system. The system checks the message to insure
its size is valid and, calulates a checksum for the message. If no checksum should be
calculated, the checksum field (the last 16-bit word in the message) should be set to
PUP_NOCKSUM.

The pup_tcontrol field is restricted to be O or PUP_TRACE; PUP_TRACE indicates
packet tracing should be performed. The pup type field may not be 0.

On input, the entire packet, including header, is provided the user. No checksum
validation is performed.

See Also
intro(4n), inet(4f)

Special Files 4-31

VAX

up(4)

Unsupported

Name
up — unibus storage module controller/drives

Syntax
controller sc0 at uba? csr 0176700 vector upintr
disk up0 at sc0 drive 0

Description
This is a generic UNIBUS storage module disk driver. It is specifically designed to
work with the Emulex SC-21 controller. It can be easily adapted to other controllers

(although bootstrapping will not necessarily be directly possible.)
Files with minor device numbers O through 7 refer to various portions of drive 0;

minor devices 8 through 15 refer to drive 1, etc. The standard device names begin
with ‘‘up’’ followed by the drive number and then a letter a-h for partitions 0-7
respectively. The character ? stands here for a drive number in the range 0-7.
The block files access the disk via the system’s normal buffering mechanism and may
be read and written without regard to physical disk records. There is also a ‘raw’
interface which provides for direct transmission between the disk and the user’s read
or write buffer. A single read or write call results in exactly one I/O operation and
therefore raw 1/O is considerably more efficient when many words are transmitted.
The names of the raw files conventionally begin with an extra ‘r.’
In raw I/O counts should be a multiple of 512 bytes (a disk sector). Likewise seek
calls should specify a multiple of 512 bytes.

Disk Support
The driver interrogates the controller’s holding register to determine the type of drive
attached. The driver recognizes four different drives: AMPEX 9300, CDC 9766,
AMPEX Capricorn, and FUJITSU 160. The origin and size of the pseudo-disks on
each drive are as follows:

CDC 9766 300M drive partitions:
disk
start
length
up?a
0
15884

4-32 Special Files

cyl

up?b

16416

33440

up?c
up?d
up?e
up?f
up?g

0
341696
358112
414048
341696

500384
15884
55936
861760
158528

0-26
27-81
0-822
562-588
589-680
681-822
562-822

up?h

49856

291346

82-561

up(4)

Unsupported
AMPEX 9300 300M drive partitions:
cyl
length
start
disk
0-26
15884
0
up?a
27-81
33440
16416
up?b
0-814
495520
0
up?c
562-588
15884
341696
up?d
589-680
55936
358112
up?e
681-814
81312
414048
up?f
562-814
153664
341696
up?g
up?h
49856
291346
82-561

AMPEX Capricorn 330M drive partitions:
cyl
length
start
disk
hp?a
hp?b
hp?c
hp?d
hp?e
hp?f

hp?g
hp?h

0
16384
0o
342016
358400
414720

342016
50176

15884
33440
524288
15884
55936
109408
182112
291346

FUJITSU 160M drive partitions:

0-31
32-97
0-1023
668-699
700-809

810-1023
668-1023
98-667

disk
up?a
up?b

start
0
16000

length
15884
33440

cyl
0-49
50-154

up?d
up?e
up?f
up?g

49600
65600
121600
49600

15884
55936
141600
213600

155-204
205-379
380-822
155-822

up?c

263360

0-822

It is unwise for all of these files to be present in one installation, since there is
overlap in addresses and protection becomes a sticky matter. The up?a partition is
normally used for the root file system, the up?b partition as a paging area, and the
up?c partition for pack-pack copying (it maps the entire disk). On 160M drives the
up?g partition maps the rest of the pack. On other drives both up?g and up?h are
used to map the remaining cylinders.

Restrictions

In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries,
and write scribbles on the tail of incomplete blocks. Thus, in programs that are
likely to access raw devices, read, write and 1seek(2) should always deal in
512-byte multiples.

Diagnostics
up%d%c: hard error sn%d cs2=%b erl=%b er2=%b.
An unrecoverable error occurred during transfer of the specified sector in the

specified disk partition. The contents of the cs2, erl and er2 registers are printed in
octal and symbolically with bits decoded. The error was either unrecoverable, or a
large number of retry attempts (including offset positioning and drive recalibration)

Special Files 4-33

VAX

up (4)

Unsupported
could not recover the error.

up%d: write locked.
The write protect switch was set on the drive when a write was attempted. The write
operation is not recoverable.

up%d: not ready.
The drive was spun down or off line when it was accessed. The i/o operation is not
recoverable.

up%d: not ready (flakey).
The drive was not ready, but after printing the message about being not ready (which

takes a fraction of a second) was ready. The operation is recovered if no further
eITors OCCUr.

up%d%c: soft ecc sn%d.
A recoverable ECC error occurred on the specified sector of the specified disk

partition. This happens normally a few times a week. If it happens more frequently
than this the sectors where the errors are occurring should be checked to see if certain
cylinders on the pack, spots on the carriage of the drive or heads are indicated.

sc%d: lost interrupt.
A timer watching the controller detecting no interrupt for an extended period while
an operation was outstanding. This indicates a hardware or software failure. There is
currently a hardware/software problem with spinning down drives while they are

being accessed which causes this error to occur. The error causes a UNIBUS reset,
and retry of the pending operations. If the controller continues to lose interrupts, this
error will recur a few seconds later.

Files
/dev/up[0-7][a-h]

block files

/dev/rup[0-7][a-h]

raw files

See Also
intro(4n), inet(4f)

Special Files 4-47

VAX

bootparams(5)
Unsupported

Name
bootparams — boot parameter data base

Syntax
[etc/bootparams

Description
The bootparams file contains the list of client entries that Sun diskless clients use
for booting. For each diskless client the entry should contain: first, the name of the
diskless client; and, second, a list of keys, names of servers, and pathnames.
Items are separated by TAB characters.

Examples
The following is an example of the /etc/bootparams taken from a SunOS
system.

myclient

root=myserver:/nfsroot/myclient \
swap=myserver:/nfsswap/myclient \

dump=myserver:/nfsdump/myclient