.\" Copyright (c) 1986 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)intro.4 6.4 (Berkeley) 6/23/90
.TH INTRO 4 "June 23, 1990"
intro \- introduction to special files and hardware support
This section describes the special files, related driver functions,
In this part of the manual, the SYNOPSIS section of
each configurable device gives a sample specification
for use in constructing a system description for the
The DIAGNOSTICS section lists messages which may appear on the console
and in the system error log
due to errors in device operation.
A hardware device is identified to the system at configuration time
and the appropriate device or network interface driver is then compiled
into the system. When the resultant system is booted, the
autoconfiguration facilities in the system probe for the device
on the VERSAbus and, if found, enable the software
support for it. If a VERSAbus device does not respond at autoconfiguration
time it is not accessible at any time afterwards. To
enable a VERSAbus device which did not autoconfigure, the system will have to
The autoconfiguration system is described in
autoconf(4), netintro(4), config(8)
The devices listed below are supported in this incarnation of
the system. Devices are indicated by their functional interface.
If second vendor products provide functionally identical interfaces
they should be usable with the supplied software.
(\fBBeware however that we promise the software works
ONLY with the hardware indicated on the appropriate manual page.\fP)
ace ACC 10 Mb/s Ethernet controller
cons Tahoe console interface
cy Cypher tape drive interface
dr Ikon DR-11W controller
enp 3Com 10 Mb/s Ethernet controller
ik Evans and Sutherland PS300 interface through an Ikon DR-11W controller
vd CCI vd mass storage disk controller
vx CCI vioc terminal multiplexor
projects / unix-history / blob