BFS(4spp) RISC/os Reference Manual BFS(4spp)
NAME
bfs - ethernet boot file server device
SYNOPSIS
{
"bfs", cmcinit, cmcopen,
cmcstrategy, cmcclose, cmcioctl,
DTTYPECHAR,
DTFSBFS, "boot server/CMC/egl ethernet"
}
DESCRIPTION
Bfs is a block server protocol that sits on top of a UDP/IP
speaking ethernet device. Bfs communicates via a stateless
protocol with the UMIPS-BSD program bfsd(8spp), which ser-
vices its requests for file blocks. By convention, bfsd
services requests that arrive on UDP port 2201. Before the
bfs device may be used, the prom monitor environment vari-
able, $netaddr, must be correctly assigned an internet
address for this host.
REGISTERS
bfs supports two Ethernet controllers with control registers
in A24 supervisor address space. Controller 0 has its con-
trol registers based at 0xde0000, controller 1 has its con-
trol registers based at 0xf00000. The user may access cmc
Ethernet controllers with control registers based dif-
ferently that these by specifying the controller number as
the negative of the control register base.
DIAGNOSTICS
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
Printed 1/6/92 Page 1
BFS(4spp) RISC/os Reference Manual BFS(4spp)
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
SEE ALSO
udp(4spp), bfsd(8spp), bfs(5spp)
Page 2 Printed 1/6/92