1 .\" $NetBSD: ndbootd.8,v 1.3 2002/01/19 11:45:07 wiz Exp $
2 .\" <<Id: ndbootd.8,v 1.2 2001/05/15 14:42:25 fredette Exp >>
4 .\" Copyright (c) 2001 Matthew Fredette. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. All advertising materials mentioning features or use of this software
15 .\" must display the following acknowledgement:
16 .\" This product includes software developed by Matthew Fredette.
17 .\" 4. The name of Matthew Fredette may not be used to endorse or promote
18 .\" products derived from this software without specific prior written
21 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
22 .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
23 .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
32 Network Disk (ND) Protocol server
37 .Op Fl w Ar windowsize
42 is a server which supports the
43 Sun Network Disk (ND) Protocol.
44 This protocol was designed by Sun before they designed
47 makes the raw blocks of a disk available to network clients. Contrast
48 this with the true namespace and file abstractions that
52 The only reason you're likely to encounter ND nowadays is if you have
53 an old Sun 2 machine, like the 2/120 or 2/50. The Sun 2 PROMs can
54 only use ND to boot over the network. (Later, the Sun 3 PROMs would
59 to boot over the network.)
62 is a very simple ND server that only supports client reads for
63 booting. It exports a disk that the clients consider to be
65 (ND public unit zero). The disk is available only to clients that are
68 and have valid hostnames.
69 (Sun 2 PROMs don't do RARP, but they do learn their IP
70 address from the first ND response they receive from the server.)
73 is a file containing the mandatory first-stage network boot
75 .Pa /usr/mdec/bootyy .
76 The layout of the exported disk is:
77 .Bl -bullet -offset indent
79 block 0: normally a Sun disklabel (but ignored by the PROM)
81 blocks 1-15: the first-stage network boot program
88 will also make a second-stage network
89 boot program available to clients, typically
90 .Pa /usr/mdec/netboot .
93 is a filename, that file is the single second-stage network boot program
94 to be served to all clients.
98 is a directory name, typically
102 client's second-stage network boot program by turning its IP address
103 into a filename in that directory, in the same manner later Sun 3
104 PROMs do when TFTPing (i.e., if a client has IP address 192.168.1.10,
107 .Pa /tftpboot/C0A8010A.SUN2
110 When used in this last manner with an ND-aware first-stage boot program,
112 serves the same purpose in the Sun 2 netboot process as
114 serves in the Sun 3 netboot process.
116 Any second-stage network boot program always begins at block 16 of the
117 exported disk, regardless of the length of the first-stage network
120 All first- and second-stage network boot programs must have all
121 executable headers stripped off; they must be raw binary programs.
123 The remaining options are:
124 .Bl -tag -width "directory"
125 .It Fl i Ar interface
126 Only listen for ND clients on interface
130 listens for clients on the first non-loopback IP interface
131 that is up and running.
132 .It Fl w Ar windowsize
133 This adjusts the window size of the ND protocol. This is
134 the number of 1-kilobyte packets that can be transmitted before
135 waiting for an acknowledgement. Defaults to 6.
137 Run in debug mode. Debugging output goes to standard error
138 and the server will not fork.
141 .Bl -tag -width Pa -compact
149 Whether or not there is a second-stage network boot program, the
150 exported disk appears to all clients to have infinite length. The
151 content of all blocks not used by the first- or second-stage network
152 boot programs is undefined. All client reads of undefined blocks
153 are silently allowed by the server.