Digital Equipment RapidPrint 500, Reference Manual

Page: 179 / 192

B -1
Glossary
B
B - Glossary of Terms
AppleTalk AppleTalk was developed by Apple Computer to allow networking
between Macintoshes. All Macintosh computers have a LocalTalk
port running AppleTalk over a 230kbit serial line. AppleTalk also runs
over Ethernet (via EtherTalk) and Token Ring network media (via
TokenTalk). Due to dynamic addressing and powerful name direc-
tory services, installing an AppleTalk device is generally as simple as
attaching it and turning it on.
AUI Attachment Unit Interface. A 15-pin shielded, twisted pair Ethernet
cable used (optionally) to connect the RapidPrint 500 and a
MAU .
backbone Any communications network has a main “cable,” and devices can be
thought of as attaching to this main conductor. (“Cable” is mislead-
ing, because networks can be over microwave or fiber optic carriers,
as well.) For example, in a university setting, the backbone might be
the cable that runs to all the buildings that need network access. Local
sub-networks and devices are attached off the main backbone.
BOOTP BOOTP is a TCP/IP network protocol that lets “dumb” network
nodes request configuration information from a BOOTP server node.
At boot time, the dumb node sends a broadcast message requesting
information and waits for a reply. The BOOTP host, if configured,
provides the dumb node with an IP address, the IP address of a load
host (usually itself), and the name of the download file. The dumb
node needs only know its own hardware address, as this is what the
BOOTP server uses to decide whether it can help the node and what
information to provide.
BOOTP implementations usually have a configuration file (such as
/usr/etc/bootptab
) that lists the hardware and IP addresses of BOOTP
clients, as well as the download file they should use. Most TCP/IP
hosts can act as servers if BOOTP replies have been enabled. See your
local documentation (man pages, etc) for specific information.
download The transfer of a file or information from one network node to
another. Generally it refers to transferring a file from a “big” node,
such as a computer, to a “small” node, such as a terminal server or
printer. Because the server code is downloaded (as opposed to being
stored permanently in the device’s ROM), the code can be upgraded
easily.