Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ () — UMIPS/BSD System Programmer's Package 2.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

 

bfs − ethernet boot file server device

{
"bfs",_cmcinit,_cmcopen,
_cmcstrategy,_cmcclose,_cmcioctl,
DTTYPE_CHAR,
DTFS_BFS,"boot server/CMC ethernet"
}

is a block server protocol that sits on top of a UDP/IP speaking ethernet device.  In the current implementation, the UDP/IP communication is provided by the device driver.  communicates via a stateless protocol with the UMIPS-BSD program which services its requests for file blocks.  By convention, bfsd services requests that arrive on UDP port 2201.  Before the device may be used, the prom monitor environment variable, $netaddr, must be correctly assigned and internet address for this host.  The controller, unit, and partition fields are passed on, uninterpreted to the underlying ethernet device, see path too long for bfs File pathname was longer than 254 characters bind failed Bfs port already in use or out of standalone socket buffers $netaddr incorrect: %s Environment variable $netaddr not defined, or not in Internet standard "." notation.  No server for %s No bfsd server replied that it could service the request for the file lost connection Bfs established communication with server and then lost it.  Also occurs with incorrectly setup sub-nets bfs read failed Bfsd server could not supply requested block unsolicited bfs reply from host %s The indicated host transmitted a bfs packet without request %s:%s bad packet received Garbled bfs reply packet received udp(4spp), bfsd(8spp), bfs(5spp)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026